home-manager/tests/modules/services/emacs/emacs-socket-and-startWithUserSession.nix

{ lib, pkgs, ... }:

{
  services.emacs = {
    enable = true;
    socketActivation.enable = true;
    startWithUserSession = true;
  };

  nixpkgs.overlays = [
    (self: super: rec {
      emacs = pkgs.writeShellScriptBin "dummy-emacs-28.0.5" "" // {
        outPath = "@emacs@";
      };
      emacsPackagesFor = _:
        lib.makeScope super.newScope (_: { emacsWithPackages = _: emacs; });
    })
  ];

  nmt.script = ''
    assertFileContains \
      home-files/.config/systemd/user/emacs.service \
      "WantedBy=default.target"
  '';
}
emacs: optionally start service with the session Add services.emacs.startWithUserSession boolean to indicate that Emacs must be started with the systemd user session. This is true by default unless socket activation is also true. In the past, the user had to choose between socket activation (to get the Emacs service started when the user uses emacsclient) and immediate start with the user session. When choosing immediate start over socket activation and if the Emacs service is stopped at some point, using emacsclient would start a new Emacs daemon but the service would still be turned off. This situation would prevent `home-manager switch` from completing successfully because it wouldn't be able to start the Emacs service as Emacs is already running. This new setting makes it possible to have both socket activation and immediate start at the same time. In this scenario, Emacs is started with the user session and, after the Emacs service is stopped, using emacsclient starts the service again. This new settings also makes it possible to have neither socket activation nor immediate start. 2022-05-06 07:13:20 +02:00			`{ lib, pkgs, ... }:`

			`{`
			`services.emacs = {`
			`enable = true;`
			`socketActivation.enable = true;`
			`startWithUserSession = true;`
			`};`

			`nixpkgs.overlays = [`
			`(self: super: rec {`
			`emacs = pkgs.writeShellScriptBin "dummy-emacs-28.0.5" "" // {`
			`outPath = "@emacs@";`
			`};`
			`emacsPackagesFor = _:`
tests: various minor cleanups 2023-05-13 00:08:12 +02:00			`lib.makeScope super.newScope (_: { emacsWithPackages = _: emacs; });`
emacs: optionally start service with the session Add services.emacs.startWithUserSession boolean to indicate that Emacs must be started with the systemd user session. This is true by default unless socket activation is also true. In the past, the user had to choose between socket activation (to get the Emacs service started when the user uses emacsclient) and immediate start with the user session. When choosing immediate start over socket activation and if the Emacs service is stopped at some point, using emacsclient would start a new Emacs daemon but the service would still be turned off. This situation would prevent `home-manager switch` from completing successfully because it wouldn't be able to start the Emacs service as Emacs is already running. This new setting makes it possible to have both socket activation and immediate start at the same time. In this scenario, Emacs is started with the user session and, after the Emacs service is stopped, using emacsclient starts the service again. This new settings also makes it possible to have neither socket activation nor immediate start. 2022-05-06 07:13:20 +02:00			`})`
			`];`

			`nmt.script = ''`
			`assertFileContains \`
			`home-files/.config/systemd/user/emacs.service \`
			`"WantedBy=default.target"`
			`'';`
			`}`