Emacs Daemon Architecture: Persistent Sessions and Fast Startup

The Problem with Slow Emacs Startup

When you launch Emacs normally, it reads your init files every time, which can take seconds on systems with heavy configurations. This delay isn't just annoying—it breaks workflows where you need to open files quickly from the command line, like fixing a git commit message or editing a config file.

The Daemon Solution

The emacs --daemon command starts a background server process that holds your session state. Once running, emacsclient connects to this server instantly without reloading init files. Think of it like keeping Emacs running in the background, ready to accept connections.

Basic Setup

Add this to your early-init.el to enable server functionality early:

(server-start)

Then configure your environment variables:

export EDITOR="emacsclient -t"
export VISUAL="emacsclient -c -a emacs"

The -a emacs flag is crucial: if no daemon exists, it starts one automatically instead of failing.

Practical Usage

Once the daemon is running, these commands work instantly:

# Open a new graphical frame
emacsclient -c

# Open a terminal frame
emacsclient -t

# Evaluate an expression
emacsclient -e "(+ 1 2)"

# Edit a file for git commits
git commit

Systemd Integration for Automatic Startup

Create ~/.config/systemd/user/emacs.service to auto-start Emacs at login:

[Unit]
Description=Emacs daemon

[Service]
Type=forking
ExecStart=/usr/bin/emacs --daemon
ExecStop=/usr/bin/emacsclient -e "(server-kill-terminate)"

[Install]
WantedBy=default.target

Enable it with:

systemctl --user enable emacs.service
systemctl --user start emacs.service

Important Limitations and Gotchas

Display Dependencies

Terminal frames may render incorrectly if the daemon started under a different display (e.g., SSH X11 forwarding vs local display). The daemon inherits the display environment at startup, so GUI-specific features like tool-bar-mode can fail in terminal clients.

Guard Against Display-Specific Code

In your init files, check the display type before enabling GUI features:

(when (display-graphic-p)
  (tool-bar-mode 1)
  (menu-bar-mode 1))

Multiple Daemon Instances

Using different EMACS_SERVER_FILE values creates separate daemons. To connect to a specific one:

emacsclient -s /path/to/server

Crash Recovery

If the daemon crashes, all unsaved buffers are lost. Enable these safeguards:

(desktop-save-mode 1)
(add-hook 'server-after-make-frame-hook
          'server-save-buffers-kill-terminal)

Verification Steps

Run these commands to confirm your setup works:

1. Start daemon: emacs --daemon
2. Test evaluation: emacsclient -c -e "(+ 1 2)" should return 3
3. Check processes: ps aux | grep emacs should show one daemon and no extra Emacs processes
4. Verify socket: ls -l ~/.emacs.d/server/server should show srwx------ permissions
5. Test fallback: EDITOR="emacsclient -t -a emacs" git commit should start daemon and open commit message

Common Mistakes to Avoid

• Forgetting -a emacs: Without it, emacsclient fails if no daemon exists
• Starting daemon too late: (server-start) should be in early-init.el, not after package initialization
• Not handling crashes: Always enable desktop saving and auto-save for persistence
• Mixing terminal and GUI frames: Remember that face settings are shared across all frames