In the systemd service, I believe that Carlos was setting $0 to emacsd for the following effect: $ xprop -name emacsd@$HOST | grep WM_CLASS WM_CLASS(STRING) = "emacsd", "Emacsd" This is because deskt
Thanks. I'm not very familiar with how systemd works, but from my limited knowledge of it, I think this makes sense? So I've applied your patch to Emacs 28. -- (domestic pets only, the antidote for o
This was four weeks ago, so I've now pushed this partial reversion to the trunk. -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no
Yeah, me neither. Perhaps Carlos has some insight here... -- (domestic pets only, the antidote for overdose, milk.) bloggy blog: http://lars.ingebrigtsen.no
Yes, that fixes my issue, however as I'm not quite sure why it was introduced in the first place, I don't know how it interacts with the rest of the patch. Would reverting this bit of the patch fix t
Would reverting this bit of the patch fix the problem? [Service] Type=notify -ExecStart=emacs --fg-daemon +ExecStart=@emacs emacsd --fg-daemon ExecStop=emacsclient --eval "(kill-emacs)" -- (domestic
This appears to break packages that rely on `invocation-name' to be executable. When started as a systemd service, the `invocation-name' of the server process is `emacsd', which is not indicative of
I've renamed it to emacsd since it's launched by systemd. Now it's a bit confusing that StartupWMClass = Emacsd, but I think it's preferable to the alternative. Attachment: 0001-Improve-client-daemo
I've changed the name of the emacsclient launcher from "Emacs" to "Emacs (Client)". Also added the bug number to the commit message. One last remark: the name emacsclient to run `emacs --daemon` is a
The attached patch adds an emacsclient.desktop launcher with StartWMClass=Emacsclient and also makes systemd start the daemon with name emacsclient. This is intended to fix a number of shortcomings i