Emacs server - Revision history

Thomas Ganter: /* OS X */ launch configuration

2019-10-26T20:27:34Z

OS X: launch configuration

24.135.18.144: Fixing a simple error

2016-04-05T03:12:42Z

Fixing a simple error

128.187.112.6: /* MS Windows */ Added note about needing Emacs 25 for daemon support. Changed code to use runemacs, since this won't popup a cmd box

2015-12-17T18:18:40Z

MS Windows: Added note about needing Emacs 25 for daemon support. Changed code to use runemacs, since this won't popup a cmd box

Miabraha: /* Linux */

2015-06-25T01:07:19Z

Linux

Miabraha: /* Linux */

2015-06-25T01:06:59Z

Linux

Miabraha: Expanded systemd instructions

2015-06-25T01:06:32Z

Expanded systemd instructions

Miabraha: /* Linux */

2015-06-23T03:21:38Z

Linux

Miabraha: /* Linux */

2015-06-23T00:21:33Z

Linux

Miabraha: /* Linux */

2015-06-23T00:21:21Z

Linux

Miabraha: Updated intro

2015-06-22T21:30:12Z

Updated intro

@@ Line 61: / Line 61: @@
 == OS X ==
-<code>launchd</code> is the OS X analog of <code>systemd</code> and can be configured just as easily. If someone is familiar with launchd configuration please fill this in.
+<code>launchd</code> is the OS X analog of <code>systemd</code> and can be configured just as easily. The following is a valid launchd file based on the <code>homebrew</code> installation of emacs, modified to work for <code>homebrew cask</code> and to have a proper <code>PATH</code> variable so emacs can actually call binaries:
 == MS Windows ==

← Older revision		Revision as of 03:12, 5 April 2016
Line 1:		Line 1:
−	Emacs includes an optional client-server architecture. The benefit of running emacs in server mode is that new client instances can be started up instantaneously. If you have 100+ packages and starting Emacs usually takes several ~~three~~ seconds, using server mode creates a much more streamlined workflow without sacrificing customization functionality.	+	Emacs includes an optional client-server architecture. The benefit of running emacs in server mode is that new client instances can be started up instantaneously. If you have 100+ packages and starting Emacs usually takes several seconds, using server mode creates a much more streamlined workflow without sacrificing customization functionality.

	== Starting the Server ==		== Starting the Server ==

@@ Line 64: / Line 64: @@
 == MS Windows ==
-Open the startup folder by running the command <code>shell:startup</code> in a run dialog or by typing it in the Windows Explorer path bar. Place a shortcut to Emacs in this folder to run Emacs at boot. Change the target to <code>emacs --daemon</code> to run start it in daemon mode. The best option for more advanced Emacs daemon-mode configuration on Windows is still not settled, there is some discussion on the Emacs Wiki which could potentially be sifted through.
+Open the startup folder by running the command <code>shell:startup</code> in a run dialog or by typing it in the Windows Explorer path bar. Place a shortcut to Emacs in this folder to run Emacs at boot. Change the target to <code>runemacs --daemon</code> to run start it in daemon mode. Please note, you need at least Emacs 25 in order to use daemon on Windows. The best option for more advanced Emacs daemon-mode configuration on Windows is still not settled, there is some discussion on the Emacs Wiki which could potentially be sifted through.
 [[Category: Server]]

@@ Line 48: / Line 48: @@
   Environment=DISPLAY=:%i
   TimeoutStartSec=0
-−
   [Install]
   WantedBy=default.target

@@ Line 54: / Line 54: @@
 Enable the new module with <code>systemctl --user enable emacsd</code>; useful commands besides <code>enable</code> include <code>stop</code>, <code>kill</code> and <code>restart</code>. After running enable, the service will be enabled permanently.  You can use <code>disable</code> if you no longer want systemd to run an Emacs daemon.
-A few parts of this script are not quite self-documenting.  Two are just technical: <code>Type</code> tells systemd it should expect <code>emacs --systemd</code> to fork a server process, and <code>Environment sets an environment variable to ensure Emacs works properly with multiple X displays.  The Restart command asks systemd to restart Emacs whenever there is a nonzero exit code.  For example, if Emacs hangs in the middle of a loop and you kill it in a task manager or run <code>systemctl --user kill</code>, systemd will restart Emacs.  Alternative values you may want to use are <code>no</code> and <code>always</code>.  TimeoutStartSec=0 tells systemd it shouldn't worry about how long it takes Emacs to start.  Specifying a timeout might be useful if you occasionally break your Emacs init file.
+A few parts of this script are not quite self-documenting.  Two are just technical: <code>Type</code> tells systemd it should expect <code>emacs --systemd</code> to fork a server process, and <code>Environment</code> sets an environment variable to ensure Emacs works properly with multiple X displays.  The Restart command asks systemd to restart Emacs whenever there is a nonzero exit code.  For example, if Emacs hangs in the middle of a loop and you kill it in a task manager or run <code>systemctl --user kill</code>, systemd will restart Emacs.  Alternative values you may want to use are <code>no</code> and <code>always</code>.  TimeoutStartSec=0 tells systemd it shouldn't worry about how long it takes Emacs to start.  Specifying a timeout might be useful if you occasionally break your Emacs init file.
 Systemd will not know what to do if Emacs tries to ask for input before closing, for example, if Desktop mode prompts for confirmation before overwriting a desktop file.  If the simple <code>(progn)</code> script executed on ExecStop</code> is not suitable,  You may need to define your own command for a clean exit and call that function instead.

@@ Line 34: / Line 34: @@
 Configuration through the init daemon <code>systemd</code> is the preferred method of starting Emacs at launch on most major distributions, including Debian, Ubuntu, Fedora, OpenSUSE, Arch, and derivatives.
-To tell systemd to start Emacs on init, place the following script <code>emacsd.service</code> in your systemd user configuration folder, replacing the location of the emacs executable if necessary.  On Debian-based distributions, this file should be named <code>/etc/systemd/user/emacsd.service</code>.
+To tell systemd to start Emacs on init, place the following script <code>emacsd.service</code> in your systemd user configuration folder, modifying the binary .  On Debian-based distributions, this file should be named <code>~/.config/systemd/user/emacsd.service</code>.
   [Unit]
-  Description=GNU Emacs daemon
+  Description=Emacs: the extensible, self-documenting text editor
   Documentation=man:emacs(1) info:Emacs
   [Service]
   Type=forking
   ExecStart=/usr/bin/emacs --daemon
-  ExecStop=/usr/bin/emacsclient --e "(kill-emacs)"
+  ExecStop=/usr/bin/emacsclient --eval "(progn (setq kill-emacs-hook nil) (kill-emacs))"
-  Restart=always
+  Restart=on-failure
+  Environment=DISPLAY=:%i
   [Install]
-  WantedBy=console.target
+  WantedBy=default.target
-Enable the new module with <code>systemctl --user enable emacsd</code>.
+Systemd will not know what to do if Emacs tries to ask for input before closing, for example, if Desktop mode prompts for confirmation before overwriting a desktop file.  If the simple <code>(progn)</code> script executed on ExecStop</code> is not suitable,  You may need to define your own command for a clean exit and call that function instead.
-If systemd is not available on your distribution, you can add <code>/usr/bin/emacs --daemon</code> to your crontab. However using systemd is preferable because the process will begin up at boot, i.e. without depending on the <code>cron</code> process to start first.
+If systemd is not available on your distribution, you can add <code>/usr/bin/emacs --daemon</code> to your crontab. However using systemd is preferable because of the ability to easily configure Emacs to restart, and because the process will begin at boot, i.e. without depending on the <code>cron</code> process to start.
 == OS X ==

← Older revision		Revision as of 21:30, 22 June 2015
Line 1:		Line 1:
−	Emacs includes an optional client-server architecture.	+	Emacs includes an optional client-server architecture. The benefit of running emacs in server mode is that new client instances can be started up instantaneously. If you have 100+ packages and starting Emacs usually takes several three seconds, using server mode creates a much more streamlined workflow without sacrificing customization functionality.

	== Starting the Server ==		== Starting the Server ==