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
To start a server in an existing Emacs session, run M-x server-start. A server started in this manner will close when the last visible Emacs frame closes. If you want Emacs to automatically run a server on startup, add the following to your configuration file.
Emacs 23 and higher provide the --daemon command-line argument, which will cause Emacs to immediately start a server and fork into the background. A server started in this manner is fully daemonized and will remain running even with no visible Emacs frames and after its parent terminal has closed (for example, after an SSH session has disconnected).
Note that, if using --daemon, your configuration file will be run while Emacs is still in a terminal. This may affect your theming if you usually use graphical Emacs.
Note: This option is not supported on Windows.
Once the server is started you may use the
emacsclient command outside of Emacs to send a file to Emacs for editing, e.g.
emacsclient ~/.emacs.d/init.el to modify your init file. On a GNU/Linux system it might be a good idea to set your EDITOR environment variable to emacsclient or emacsclient -t. Using emacsclient without any arguments will cause the calling process to simply pause and wait for the Emacs server to report that it's done editing. Using emacsclient -t will cause the calling process to put up a text-mode frame in the same terminal.
If the server was started using --daemon, you should run emacsclient -t or emacsclient -nc to create a visible frame to interact with.
Once you have finished with a buffer that was opened via emacsclient you should use the [C-x #] (or M-x server-edit) to properly close the loop. Killing the buffer normally will not send the signal to emacsclient that Emacs has finished with the file.
If you're in an Emacs session that was started using --daemon,will only close the frame that it was invoked in. It will also signal to the client that owns the frame that its editing job is done, so emacsclient -c or emacsclient -t as EDITOR will behave much like a full emacs or emacs -nw.
To entirely close a server started with --daemon, run M-x save-buffers-kill-emacs in a frame.
Adding To OS Startup
Configuration through the init daemon
systemd 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
emacsd.service in your systemd user configuration folder, modifying the binary . On Debian-based distributions, this file should be named
[Unit] 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 --eval "(progn (setq kill-emacs-hook nil) (kill-emacs))" Restart=on-failure Environment=DISPLAY=:%i TimeoutStartSec=0 [Install] WantedBy=default.target
Enable the new module with
systemctl --user enable emacsd; useful commands besides
restart. After running enable, the service will be enabled permanently. You can use
disable 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:
Type tells systemd it should expect
emacs --systemd to fork a server process, and
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
systemctl --user kill, systemd will restart Emacs. Alternative values you may want to use are
always. 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
(progn) 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
/usr/bin/emacs --daemon 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
cron process to start.
launchd is the OS X analog of
systemd and can be configured just as easily. If someone is familiar with launchd configuration please fill this in.
Open the startup folder by running the command
shell:startup 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
runemacs --daemon 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.