In reply to @gilganix:matrix.org

I tried to use the following, but it still launches with an empty config file as if it was unable to locate ~/.config/emacs:

    systemd.user.services.emacs = {
      unitConfig = {
        Description = "Emacs text editor.";
        Documentation = "man:emacs(1)";

        After = [ "graphical-session-pre.target" ];
        PartOf = [ "graphical-session.target" ];
      };

      wantedBy = [ "default.target" ];

      serviceConfig = {
        Type = "forking";
        ExecStart = "${emacsWithPackages}/bin/emacs --fg-daemon";
        ExecStop = "${emacsWithPackages}/bin/emacsclient --eval (kill-emacs)";
        Restart = "always";
      };
    };

In reply to @psionic-lights:matrix.org
Just symlink? If you also have an ~/.emacs.d then Emacs may try to load that first. I don't know the behavior in that case. ExecStart is the property you need to override to point at a specific config. The client would only need such configuration if the server was serving at a nonstandard location.

In reply to @gilganix:matrix.org
How would you do that through ExecStart?

In reply to @psionic-lights:matrix.org
The code you posted is the unit itself. You can just modify ExecStart in that snippet to point to where your configs are

In reply to @psionic-lights:matrix.org
The code you posted is the unit itself. You can just modify ExecStart in that snippet to point to where your configs are

I can not find anything else about this error (that would be recent enough to be relevant) therefore I have to assume its nix related, but when I try to start erlang-mode, then I get this message in the message buffer:

File mode specification error: (error Given parent class xref-file-location is not a class)

I use emacsGcc and all the erlang package as defined in commit ae1c1eeeb6168c9e1a13dd47c44781c0eb9ed8ed.