| blob | 71e2463c595663499416ba2153291c15b319b30a |
1 ;;; server.el --- Lisp code for GNU Emacs running as server process
3 ;; Copyright (C) 1986,87,92,94,95,96,97,98,99,2000,01,02,2003
4 ;; Free Software Foundation, Inc.
6 ;; Author: William Sommerfeld <wesommer@athena.mit.edu>
7 ;; Maintainer: FSF
8 ;; Keywords: processes
10 ;; Changes by peck@sun.com and by rms.
12 ;; This file is part of GNU Emacs.
14 ;; GNU Emacs is free software; you can redistribute it and/or modify
15 ;; it under the terms of the GNU General Public License as published by
16 ;; the Free Software Foundation; either version 2, or (at your option)
17 ;; any later version.
19 ;; GNU Emacs is distributed in the hope that it will be useful,
20 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
21 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
22 ;; GNU General Public License for more details.
24 ;; You should have received a copy of the GNU General Public License
25 ;; along with GNU Emacs; see the file COPYING. If not, write to the
26 ;; Free Software Foundation, Inc., 59 Temple Place - Suite 330,
27 ;; Boston, MA 02111-1307, USA.
29 ;;; Commentary:
31 ;; This Lisp code is run in Emacs when it is to operate as
32 ;; a server for other processes.
34 ;; Load this library and do M-x server-edit to enable Emacs as a server.
35 ;; Emacs opens up a socket for communication with clients. If there are no
36 ;; client buffers to edit, server-edit acts like (switch-to-buffer
37 ;; (other-buffer))
39 ;; When some other program runs "the editor" to edit a file,
40 ;; "the editor" can be the Emacs client program ../lib-src/emacsclient.
41 ;; This program transmits the file names to Emacs through
42 ;; the server subprocess, and Emacs visits them and lets you edit them.
44 ;; Note that any number of clients may dispatch files to emacs to be edited.
46 ;; When you finish editing a Server buffer, again call server-edit
47 ;; to mark that buffer as done for the client and switch to the next
48 ;; Server buffer. When all the buffers for a client have been edited
49 ;; and exited with server-edit, the client "editor" will return
50 ;; to the program that invoked it.
52 ;; Your editing commands and Emacs's display output go to and from
53 ;; the terminal in the usual way. Thus, server operation is possible
54 ;; only when Emacs can talk to the terminal at the time you invoke
55 ;; the client. This is possible in four cases:
57 ;; 1. On a window system, where Emacs runs in one window and the
58 ;; program that wants to use "the editor" runs in another.
60 ;; 2. On a multi-terminal system, where Emacs runs on one terminal and the
61 ;; program that wants to use "the editor" runs on another.
63 ;; 3. When the program that wants to use "the editor" is running
64 ;; as a subprocess of Emacs.
66 ;; 4. On a system with job control, when Emacs is suspended, the program
67 ;; that wants to use "the editor" will stop and display
68 ;; "Waiting for Emacs...". It can then be suspended, and Emacs can be
69 ;; brought into the foreground for editing. When done editing, Emacs is
70 ;; suspended again, and the client program is brought into the foreground.
72 ;; The buffer local variable "server-buffer-clients" lists
73 ;; the clients who are waiting for this buffer to be edited.
74 ;; The global variable "server-clients" lists all the waiting clients,
75 ;; and which files are yet to be edited for each.
77 ;;; Code:
82 "Emacs running as a server process."
86 "*Hook run when visiting a file for the Emacs server."
91 "*Hook run when switching to a buffer for the Emacs server."
96 "*Hook run when done editing a buffer for the Emacs server."
104 "List of current server clients.
105 Each element is (CLIENTID BUFFERS...) where CLIENTID is a string
106 that can be given to the server process to identify a client.
112 ;; Changing major modes should not erase this local.
116 "*Specification of the window to use for selecting Emacs server buffers.
117 If nil, use the selected window.
118 If it is a function, it should take one argument (a buffer) and
119 display and select it. A common value is `pop-to-buffer'.
120 If it is a window, use that.
121 If it is a frame, use the frame's selected window.
123 It is not meaningful to set this to a specific frame or window with Custom.
124 Only programs can do so."
130 nil)
135 "*Regexp matching names of temporary files.
136 These are deleted and reused after each edit by the programs that
137 invoke the Emacs server."
142 "*Whether to kill buffers when done with them.
143 If non-nil, kill a buffer unless it already existed before editing
144 it with Emacs server. If nil, kill only buffers as specified by
145 `server-temp-file-regexp'.
146 Please note that only buffers are killed that still have a client,
148 this way."
157 "Non-nil means the buffer existed before the server was asked to visit it.
158 This means that the server should not kill the buffer when you say you
167 "If a *server* buffer exists, write STRING to it for logging purposes."
173 string)
178 ;; Remove PROC from the list of clients.
183 ;; Remove PROC from the clients of each buffer.
185 ;; Kill the buffer if necessary.
194 ;; If the current frame is on `display' we're all set.
196 ;; Otherwise, look for an existing frame there and select it.
200 ;; If there's no frame on that display yet, create a dummy one
201 ;; and select it.
205 display
206 ;; This frame is only there in place of an actual "current display"
207 ;; setting, so we want it to be as unobtrusive as possible. That's
208 ;; what the invisibility is for. The minibuffer setting is so that
209 ;; we don't end up displaying a buffer in it (which noone would
210 ;; notice).
221 arg t t))
224 "Make sure DIR is a directory with no race-condition issues.
225 Creates the directory if necessary and makes sure:
226 - there's no symlink involved
227 - it's owned by us
228 - it's not readable/writable by anybody else."
234 ;; Check that it's safe for use.
239 ;;;###autoload
241 "Allow this Emacs process to be a server for client processes.
242 This starts a server communications subprocess through which
244 To use the server, set up the program `emacsclient' in the
247 Prefix arg means just kill any existing server communications subprocess."
249 ;; Make sure there is a safe directory in which to place the socket.
251 ;; kill it dead!
253 ;; Delete the socket files made by previous server invocations.
255 ;; If this Emacs already had a server, clear out associated status.
266 :service server-socket-name
268 ;; We must receive file names without being decoded.
269 ;; Those are decoded by server-process-filter according
270 ;; to file-name-coding-system.
273 ;;;###autoload
275 "Toggle Server mode.
276 With ARG, turn Server mode on if ARG is positive, off otherwise.
277 Server mode runs a process that accepts commands from the
278 `emacsclient' program. See `server-start' and Info node `Emacs server'."
279 :global t
282 ;; Fixme: Should this check for an existing server socket and do
283 ;; nothing if there is one (for multiple Emacs sessions)?
285 \f
287 "Process a request from the server to edit some files.
294 ;; If the input is multiple lines,
295 ;; process each line individually.
300 default-file-name-coding-system)))
301 client nowait eval
305 ;; Remove this line from STRING.
321 ;; ARG is a line number option.
324 ;; ARG is line number:column option.
329 ;; Undo the quoting that emacsclient does
330 ;; for certain special characters.
332 ;; Now decode the file name if necessary.
342 ;; ARG is a file name.
343 ;; Collapse multiple slashes to single slashes.
352 ;; CLIENT is now a list (CLIENTNUM BUFFERS...)
354 ;; This client is empty; get rid of it immediately.
358 ;; We visited some buffer for this client.
366 ;; Save for later any partial line that remains.
377 "Find FILES and return the list CLIENT with the buffers nconc'd.
378 FILES is an alist whose elements are (FILENAME LINENUMBER COLUMNNUMBER).
379 NOWAIT non-nil means this client is not waiting for the results,
380 so don't mark these buffers specially, just visit them normally."
381 ;; Bind last-nonmenu-event to force use of keyboard, not mouse, for queries.
383 ;; Restore the current buffer afterward, but not using save-excursion,
384 ;; because we don't want to save point in this buffer
385 ;; if it happens to be one of those specified by the server.
388 ;; If there is an existing buffer modified or the file is
389 ;; modified, revert it. If there is an existing buffer with
390 ;; deleted file, offer to write it.
402 filen
411 ;; When the buffer is killed, inform the clients.
416 \f
419 This buries the buffer, then returns a list of the form (NEXT-BUFFER KILLED).
420 NEXT-BUFFER is another server buffer, as a suggestion for what to select next,
421 or nil. KILLED is t if we killed BUFFER (typically, because it was visiting
422 a temp file).
423 FOR-KILLING if non-nil indicates that we are called from `kill-buffer'."
432 ;; Delete all dead buffers from CLIENT.
439 ;; If client now has no pending buffers,
440 ;; tell it that it is done, and forget it entirely.
447 ;; We may or may not kill this buffer;
448 ;; if we do, do not call server-buffer-done recursively
449 ;; from kill-buffer-hook.
454 ;; Notice whether server-done-hook killed the buffer.
457 ;; Don't bother killing or burying the buffer
458 ;; when we are called from kill-buffer.
461 server-kill-new-buffers
476 "Return non-nil if BUFFER contains a file considered temporary.
477 These are files whose names suggest they are repeatedly
478 reused to pass information to another program.
480 The variable `server-temp-file-regexp' controls which filenames
481 are considered temporary."
487 This kills or buries the buffer, then returns a list
488 of the form (NEXT-BUFFER KILLED). NEXT-BUFFER is another server buffer,
489 as a suggestion for what to select next, or nil.
490 KILLED is t if we killed BUFFER, which happens if it was created
491 specifically for the clients and did not exist before their request for it."
494 ;; For a temp file, save, and do make a non-numeric backup
495 ;; (unless make-backup-files is nil).
500 buffer-file-name
505 ;; Ask before killing a server buffer.
506 ;; It was suggested to release its client instead,
507 ;; but I think that is dangerous--the client would proceed
508 ;; using whatever is on disk in that file. -- rms.
520 ;; See if any clients have any buffers that are still alive.
534 ;; Prevent infinite recursion if user has made server-done-hook
535 ;; call kill-buffer.
541 \f
545 The buffer is also killed if it did not exist before the clients asked for it.
548 Temporary files such as MH <draft> files are always saved and backed up,
549 no questions asked. (The variable `make-backup-files', if nil, still
550 inhibits a backup; you can set it locally in a particular buffer to
551 prevent a backup for it.) The variable `server-temp-file-regexp' controls
552 which filenames are considered temporary.
554 If invoked with a prefix argument, or if there is no server process running,
564 "Switch to another buffer, preferably one that has a client.
565 Arg NEXT-BUFFER is a suggestion; if it is a live buffer, use it."
566 ;; KILLED-ONE is t in a recursive call
567 ;; if we have already killed one temp-file server buffer.
568 ;; This means we should avoid the final "switch to some other buffer"
569 ;; since we've already effectively done that.
577 ;; If NEXT-BUFFER is a dead buffer, remove the server records for it
578 ;; and try the next surviving server buffer.
580 ;; OK, we know next-buffer is live, let's display and select it.
585 ;; The buffer is already displayed: just reuse the window.
591 ;; Otherwise, let's find an appropriate window.
601 ;; Move to a non-dedicated window, if we have one.
612 ;; After all the above, we might still have ended up with
613 ;; a minibuffer/dedicated-window (if there's no other).
623 \f
626 ;;; server.el ends here