2 ms·
In retrospect, the name `emacsclient` was a poor one because in 2026 most folks new to Emacs expect it to act like a REST client, where runtime state is synchro
by kickingvegas 3mo ago
In retrospect, the name `emacsclient` was a poor one because in 2026 most folks new to Emacs expect it to act like a REST client, where runtime state is synchronized between the client and server over a network. Emacs' usage of ‘client’ and ‘server’ here refer to the usage of a Unix local domain (i.e. file system) socket for simple control commands from the socket client. This was later extended to support a network socket, but the client still only sends simple control commands.
- jolmg 3mo ago> Emacs' usage of ‘client’ and ‘server’ here refer to [...] simple control commands Despite that, it still enables this: > where runtime state is synchronized between the client and server over a network On graphical X11 frames: https://news.ycombinator.com/item?id=48864196 https://news.ycombinator.com/item?id=48864196 but it also enables having multiple TUI `emacsclient -c -nw` frames over SSH.