| blob | 33800a98682deaea3b211c636c0e445952868c1c |
1 ;;; server.el --- Lisp code for GNU Emacs running as server process -*- lexical-binding: t -*-
3 ;; Copyright (C) 1986-1987, 1992, 1994-2017 Free Software Foundation,
4 ;; Inc.
6 ;; Author: William Sommerfeld <wesommer@athena.mit.edu>
7 ;; Maintainer: emacs-devel@gnu.org
8 ;; Keywords: processes
10 ;; Changes by peck@sun.com and by rms.
11 ;; Overhaul by Karoly Lorentey <lorentey@elte.hu> for multi-tty support.
13 ;; This file is part of GNU Emacs.
15 ;; GNU Emacs is free software: you can redistribute it and/or modify
16 ;; it under the terms of the GNU General Public License as published by
17 ;; the Free Software Foundation, either version 3 of the License, or
18 ;; (at your option) any later version.
20 ;; GNU Emacs is distributed in the hope that it will be useful,
21 ;; but WITHOUT ANY WARRANTY; without even the implied warranty of
22 ;; MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
23 ;; GNU General Public License for more details.
25 ;; You should have received a copy of the GNU General Public License
26 ;; along with GNU Emacs. If not, see <https://www.gnu.org/licenses/>.
28 ;;; Commentary:
30 ;; This Lisp code is run in Emacs when it is to operate as
31 ;; a server for other processes.
33 ;; Load this library and do M-x server-edit to enable Emacs as a server.
34 ;; Emacs opens up a socket for communication with clients. If there are no
35 ;; client buffers to edit, server-edit acts like (switch-to-buffer
36 ;; (other-buffer))
38 ;; When some other program runs "the editor" to edit a file,
39 ;; "the editor" can be the Emacs client program ../lib-src/emacsclient.
40 ;; This program transmits the file names to Emacs through
41 ;; the server subprocess, and Emacs visits them and lets you edit them.
43 ;; Note that any number of clients may dispatch files to Emacs to be edited.
45 ;; When you finish editing a Server buffer, again call server-edit
46 ;; to mark that buffer as done for the client and switch to the next
47 ;; Server buffer. When all the buffers for a client have been edited
48 ;; and exited with server-edit, the client "editor" will return
49 ;; to the program that invoked it.
51 ;; Your editing commands and Emacs's display output go to and from
52 ;; the terminal in the usual way. Thus, server operation is possible
53 ;; only when Emacs can talk to the terminal at the time you invoke
54 ;; the client. This is possible in four cases:
56 ;; 1. On a window system, where Emacs runs in one window and the
57 ;; program that wants to use "the editor" runs in another.
59 ;; 2. On a multi-terminal system, where Emacs runs on one terminal and the
60 ;; program that wants to use "the editor" runs on another.
62 ;; 3. When the program that wants to use "the editor" is running
63 ;; as a subprocess of Emacs.
65 ;; 4. On a system with job control, when Emacs is suspended, the program
66 ;; that wants to use "the editor" will stop and display
67 ;; "Waiting for Emacs...". It can then be suspended, and Emacs can be
68 ;; brought into the foreground for editing. When done editing, Emacs is
69 ;; suspended again, and the client program is brought into the foreground.
71 ;; The buffer local variable "server-buffer-clients" lists
72 ;; the clients who are waiting for this buffer to be edited.
73 ;; The global variable "server-clients" lists all the waiting clients,
74 ;; and which files are yet to be edited for each.
76 ;; Todo:
78 ;; - handle command-line-args-left.
79 ;; - move most of the args processing and decision making from emacsclient.c
80 ;; to here.
81 ;; - fix up handling of the client's environment (place it in the terminal?).
83 ;;; Code:
88 "Emacs running as a server process."
92 "If non-nil, use TCP sockets instead of local sockets."
104 "The name or IP address to use as host address of the server process.
105 If set, the server accepts remote connections; otherwise it is local.
107 DO NOT give this a non-nil value unless you know what you are doing!
108 On unsecured networks, accepting remote connections is very dangerous,
109 because server-client communication (including session authentication)
110 is not encrypted."
116 ;;;###autoload
120 "The port number that the server process should listen on.
121 This variable only takes effect when the Emacs server is using
122 TCP instead of local sockets. A nil value means to use a random
123 port number."
129 ;;;###autoload
133 "Directory for server authentication files.
134 We only use this if `server-use-tcp' is non-nil.
135 Otherwise we use `server-socket-dir'.
137 NOTE: On FAT32 filesystems, directories are not secure;
138 files can be read and modified by any user or process.
139 It is strongly suggested to set `server-auth-dir' to a
140 directory residing in a NTFS partition instead."
144 ;;;###autoload
148 "Server authentication key.
149 This is only used if `server-use-tcp' is non-nil.
151 Normally, the authentication key is randomly generated when the
152 server starts. It is recommended to leave it that way. Using a
153 long-lived shared key will decrease security (especially since
154 the key is transmitted as plain-text).
156 In some situations however, it can be difficult to share randomly
157 generated passwords with remote hosts (e.g., no shared directory),
158 so you can set the key with this variable and then copy the
159 server file to the remote host (with possible changes to IP
160 address and/or port if that applies).
162 Note that the usual security risks of using the server over
163 remote TCP, arising from the fact that client-server
164 communications are unencrypted, still apply.
166 The key must consist of 64 ASCII printable characters except for
167 space (this means characters from ! to ~; or from code 33 to
176 "If non-nil, raise frame when switching to a buffer."
182 "Hook run when visiting a file for the Emacs server."
187 "Hook run when switching to a buffer for the Emacs server."
192 "Hook run when done editing a buffer for the Emacs server."
200 "List of current server clients.
206 ;; Changing major modes should not erase this local.
210 "Specification of the window to use for selecting Emacs server buffers.
211 If nil, use the selected window.
212 If it is a function, it should take one argument (a buffer) and
213 display and select it. A common value is `pop-to-buffer'.
214 If it is a window, use that.
215 If it is a frame, use the frame's selected window.
217 It is not meaningful to set this to a specific frame or window with Custom.
218 Only programs can do so."
224 nil)
230 "Regexp matching names of temporary files.
231 These are deleted and reused after each edit by the programs that
232 invoke the Emacs server."
237 "Whether to kill buffers when done with them.
238 If non-nil, kill a buffer unless it already existed before editing
239 it with the Emacs server. If nil, kill only buffers as specified by
240 `server-temp-file-regexp'.
241 Please note that only buffers that still have a client are killed,
243 in this way."
249 "Non-nil means the buffer existed before the server was asked to visit it.
250 This means that the server should not kill the buffer when you say you
254 ;;;###autoload
256 "The name of the Emacs server, if this Emacs process creates one.
257 The command `server-start' makes use of this. It should not be
258 changed while a server is running."
263 ;; We do not use `temporary-file-directory' here, because emacsclient
264 ;; does not read the init file.
268 "The directory in which to place the server socket.
272 "Return a list of clients with PROPERTY set to VALUE."
277 result))
280 "Create a client for process PROC, if it doesn't already have one.
281 New clients have no properties."
285 "Evaluate BODY with environment variables VARS set to those in ENV.
286 The environment variables are then restored to their previous values.
288 VARS should be a list of strings.
289 ENV should be in the same format as `process-environment'."
299 process-environment)))
303 "Delete PROC, including its buffers, terminals and frames.
304 If NOFRAME is non-nil, let the frames live.
305 Updates `server-clients'."
307 ;; Force a new lookup of client (prevents infinite recursion).
311 ;; Kill the client's buffers.
315 ;; Kill the buffer if necessary.
328 ;; Restore clients if user pressed C-g in `kill-buffer'.
331 ;; Delete the client's frames.
336 ;; Prevent `server-handle-delete-frame' from calling us
337 ;; recursively.
343 ;; Delete the client's tty, except on Windows (both GUI and console),
344 ;; where there's only one terminal and does not make sense to delete it.
347 ;; Only delete the terminal if it is non-nil.
351 ;; Delete the client's process.
361 "Buffer used internally by Emacs's server.
362 One use is to log the I/O for debugging purposes (see option `server-log'),
363 the other is to provide a current buffer in which the process filter can
370 "If option `server-log' is non-nil, log STRING to `server-buffer'.
371 If CLIENT is non-nil, add a description of it to the logged message."
380 string)
384 "The process sentinel for Emacs server connections."
385 ;; If this is a new client process, set the query-on-exit flag to nil
386 ;; for this process (it isn't inherited from the server process).
390 ;; Delete the associated connection file, if applicable.
391 ;; Although there's no 100% guarantee that the file is owned by the
392 ;; running Emacs instance, server-start uses server-running-p to check
393 ;; for possible servers before doing anything, so it *should* be ours.
403 ;; Note: TTY frames still get a `display' parameter set to the value of
404 ;; $DISPLAY. This is useful when running from that tty frame
405 ;; sub-processes that want to connect to the X server, but that means we
406 ;; have to be careful here not to be tricked into thinking those frames
407 ;; are on `display'.
411 ;; If the current frame is on `display' we're all set.
412 ;; Similarly if we are unable to open frames on other displays, there's
413 ;; nothing more we can do.
416 ;; Otherwise, look for an existing frame there and select it.
420 ;; If there's no frame on that display yet, create and select one.
424 display
425 ;; Make it display (and remember) some dummy buffer, so
426 ;; we can detect later if the frame is in use or not.
428 ;; This frame may be deleted later (see
429 ;; server-unselect-display) so we want it to be as
430 ;; unobtrusive as possible.
434 frame))))
438 ;; If the temporary frame is in use (displays something real), make it
439 ;; visible. If not (which can happen if the user's customizations call
440 ;; pop-to-buffer etc.), delete it to avoid preserving the connection after
441 ;; the last real frame is deleted.
443 ;; Rewritten to avoid inadvertently killing the current buffer after
444 ;; `delete-frame' removed FRAME (Bug#10729).
448 ;; The temp frame still only shows one buffer, and that is the
449 ;; internal temp buffer.
457 "Delete the client connection when the emacsclient frame is deleted.
458 \(To be used from `delete-frame-functions'.)"
461 proc
462 ;; See if this is the last frame for this client.
467 frame-num)))
472 "Notify the client process that its tty device is suspended."
475 proc)
482 "Remove &-quotation from ARG.
483 See `server-quote-arg' and `server-process-filter'."
491 arg t t))
494 "In ARG, insert a & before each &, each space, each newline, and -.
495 Change spaces to underscores, too, so that the return value never
496 contains a space.
498 See `server-unquote-arg' and `server-process-filter'."
506 arg t t))
509 "A wrapper around `process-send-string' for logging."
514 "Make sure DIR is a directory with no race-condition issues.
515 Creates the directory if necessary and makes sure:
516 - there's no symlink involved
517 - it's owned by us
518 - it's not readable/writable by anybody else."
525 ;; Check that it's safe for use.
534 'server
536 Using `%s' to store Emacs-server authentication files.
537 Directories on FAT32 filesystems are NOT secure against tampering.
538 See variable `server-auth-dir' for details."
541 nil)
544 ;; Files created on Windows by Administrator
545 ;; (RID=500) have the Administrators (RID=544)
546 ;; group recorded as the owner.
559 "Generate and return a random authentication key.
560 The key is a 64-byte string of random chars in the range `!'..`~'.
561 If called interactively, also inserts it into current buffer."
569 auth-key))
572 "Return server's authentication key.
574 If `server-auth-key' is nil, just call `server-generate-key'.
575 Otherwise, if `server-auth-key' is a valid key, return it.
576 If the key is not valid, signal an error."
579 server-auth-key
583 ;;;###autoload
585 "Allow this Emacs process to be a server for client processes.
586 This starts a server communications subprocess through which client
588 To use the server, set up the program `emacsclient' in the Emacs
591 Optional argument LEAVE-DEAD (interactively, a prefix arg) means just
592 kill any existing server communications subprocess.
594 If a server is already running, restart it. If clients are
595 running, ask the user for confirmation first, unless optional
596 argument INHIBIT-PROMPT is non-nil.
602 ;; Ask the user before deleting existing clients---except
603 ;; when we can't get user input, which may happen when
604 ;; doing emacsclient --eval "(kill-emacs)" in daemon mode.
609 leave-dead)
616 ;; kill it dead!
618 ;; Delete the socket files made by previous server invocations.
620 ;; Remove any leftover socket or authentication file
626 'server
629 server-name)
631 "To start the server in this Emacs process, stop the existing
635 ;; If this Emacs already had a server, clear out associated status.
638 ;; Now any previous server is properly stopped.
643 ;; Make sure there is a safe directory in which to place the socket.
652 ;; We put server's kill-emacs-hook after the others, so that
653 ;; frames are not deleted too early, because doing that
654 ;; would severely degrade our abilities to communicate with
655 ;; the user, while some hooks may wish to ask the user
656 ;; questions (e.g., desktop-kill).
660 :name server-name
661 :server t
662 :noquery t
665 :use-external-socket t
666 ;; We must receive file names without being decoded.
667 ;; Those are decoded by server-process-filter according
668 ;; to file-name-coding-system. Also don't get
669 ;; confused by CRs since we don't quote them.
671 ;; The other args depend on the kind of socket used.
678 :service server-file
694 "Kill all connections to the current server.
695 This function is meant to be called from `kill-emacs-hook'."
698 ;;;###autoload
700 "Unconditionally delete connection file for server NAME.
701 If server is running, it is first stopped.
702 NAME defaults to `server-name'. With argument, ask for NAME."
709 server-auth-dir
710 server-socket-dir))))
719 "Test whether server NAME is running.
721 Return values:
722 nil the server is definitely not running.
723 t the server seems to be running.
724 something else we cannot determine whether it's running without using
725 commands which may have to wait for a long time."
735 t)
741 t)
744 ;;;###autoload
746 "Toggle Server mode.
747 With a prefix argument ARG, enable Server mode if ARG is
748 positive, and disable it otherwise. If called from Lisp, enable
749 Server mode if ARG is omitted or nil.
751 Server mode runs a process that accepts commands from the
752 `emacsclient' program. See Info node `Emacs server' and
753 `server-start' for details."
754 :global t
757 ;; Fixme: Should this check for an existing server socket and do
758 ;; nothing if there is one (for multiple Emacs sessions)?
760 \f
762 "Eval EXPR and send the result back to client PROC."
763 ;; While we're running asynchronously (from a process filter), it is likely
764 ;; that the emacsclient command was run in response to a user
765 ;; action, so the user probably knows that Emacs is processing this
766 ;; emacsclient request, so if we get a C-g it's likely that the user
767 ;; intended it to interrupt us rather than interrupt whatever Emacs
768 ;; was doing before it started handling the process filter.
769 ;; Hence `with-local-quit' (bug#6585).
783 "Send a `-print QTEXT' command to client PROC.
784 QTEXT must be already quoted.
785 This handles splitting the command if it would be bigger than
786 `server-msg-size'."
788 part)
790 ;; We have to split the string
792 ;; Don't split in the middle of a quote sequence
794 ;; There is an uneven number of & at the end
811 ;; For tgetent(3); list according to ncurses(3).
816 ;; rxvt wants these
821 ;; Ignore nowait here; we always need to
822 ;; clean up opened ttys when the client dies.
824 ;; This is a leftover from an earlier
825 ;; attempt at making it possible for process
826 ;; run in the server process to use the
827 ;; environment of the client process.
828 ;; It has no effect now and to make it work
829 ;; we'd need to decide how to make
830 ;; process-environment interact with client
831 ;; envvars, and then to change the
832 ;; C functions `child_setup' and
833 ;; `getenv_internal' accordingly.
836 ;; ttys don't use the `display' parameter, but callproc.c does to set
837 ;; the DISPLAY environment on subprocesses.
843 frame))
853 ;; Special case for ns. This is because DISPLAY may not be set at all
854 ;; which in the ns case isn't an error. The variable display then becomes
855 ;; the fully qualified hostname, which make-frame-on-display below
856 ;; does not understand and throws an error.
857 ;; It may also be a valid X display, but if Emacs is compiled for ns, it
858 ;; can not make X frames.
861 ;; FIXME! Not sure what this was for, and not sure how it should work
862 ;; in the cl-defmethod new world!
863 ;;(unless (assq w window-system-initialization-alist)
864 ;; (setq w nil))
865 )
868 ;; Flag frame as client-created, but use a dummy client.
869 ;; This will prevent the frame from being deleted when
870 ;; emacsclient quits while also preventing
871 ;; `server-save-buffers-kill-terminal' from unexpectedly
872 ;; killing emacs on that frame.
874 ;; This is a leftover, see above.
877 frame)
886 frame))
891 nil))))
895 ;; If we're running isearch, we must abort it to allow Emacs to
896 ;; display the buffer and switch to it.
901 ;; Signaled by isearch-cancel.
904 ;; We're inside a minibuffer already, so if the emacs-client is trying
905 ;; to open a frame on a new display, we might end up with an unusable
906 ;; frame because input from that display will be blocked (until exiting
907 ;; the minibuffer). Better exit this minibuffer right away.
908 ;; Similarly with recursive-edits such as the splash screen.
912 ;; We use various special properties on process objects:
913 ;; - `env' stores the info about the environment of the emacsclient process.
914 ;; - `continuation' is a no-arg function that we need to execute. It contains
915 ;; commands we wanted to execute in some earlier invocation of the process
916 ;; filter but that we somehow were unable to process at that time
917 ;; (e.g. because we first need to throw to the toplevel).
925 "Process a request from the server to edit some files.
926 PROC is the server process. STRING consists of a sequence of
927 commands prefixed by a dash. Some commands have arguments;
928 these are &-quoted and need to be decoded by `server-unquote-arg'.
929 The filter parses and executes these commands.
931 To illustrate the protocol, here is an example command that
932 emacsclient sends to create a new X frame (note that the whole
933 sequence is sent on a single line):
935 -env HOME=/home/lorentey
936 -env DISPLAY=:0.0
937 ... lots of other -env commands
938 -display :0.0
939 -window-system
941 The following commands are accepted by the server:
943 `-auth AUTH-STRING'
944 Authenticate the client using the secret authentication string
945 AUTH-STRING.
947 `-env NAME=VALUE'
948 An environment variable on the client side.
950 `-dir DIRNAME'
951 The current working directory of the client process.
953 `-current-frame'
954 Forbid the creation of new frames.
956 `-frame-parameters ALIST'
957 Set the parameters of the created frame.
959 `-nowait'
960 Request that the next frame created should not be
961 associated with this client.
963 `-display DISPLAY'
964 Set the display name to open X frames on.
966 `-position LINE[:COLUMN]'
967 Go to the given line and column number
968 in the next file opened.
970 `-file FILENAME'
971 Load the given file in the current frame.
973 `-eval EXPR'
974 Evaluate EXPR as a Lisp expression and return the
975 result in -print commands.
977 `-window-system'
978 Open a new X frame.
980 `-tty DEVICENAME TYPE'
981 Open a new tty frame at the client.
983 `-suspend'
984 Suspend this tty frame. The client sends this string in
985 response to SIGTSTP and SIGTTOU. The server must cease all I/O
986 on this tty until it gets a -resume command.
988 `-resume'
989 Resume this tty frame. The client sends this string when it
990 gets the SIGCONT signal and it is the foreground process on its
991 controlling tty.
993 `-ignore COMMENT'
994 Do nothing, but put the comment in the server log.
995 Useful for debugging.
998 The following commands are accepted by the client:
1000 `-emacs-pid PID'
1001 Describes the process id of the Emacs process;
1002 used to forward window change signals to it.
1004 `-window-system-unsupported'
1005 Signals that the server does not support creating X frames;
1006 the client must try again with a tty frame.
1008 `-print STRING'
1009 Print STRING on stdout. Used to send values
1010 returned by -eval.
1012 `-print-nonl STRING'
1013 Print STRING on stdout. Used to continue a
1014 preceding -print command that would be too big to send
1015 in a single message.
1017 `-error DESCRIPTION'
1018 Signal an error and delete process PROC.
1020 `-suspend'
1021 Suspend this terminal, i.e., stop the client process.
1022 Sent when the user presses C-z."
1024 ;; First things first: let's check the authentication
1035 ;; Before calling `delete-process', give emacsclient time to
1036 ;; receive the error string and shut down on its own.
1039 ;; We return immediately.
1048 ;; Send our pid
1052 ;; Save for later any partial line that remains.
1056 ;; In earlier versions of server.el (where we used an `emacsserver'
1057 ;; process), there could be multiple lines. Nowadays this is not
1058 ;; supported any more.
1063 default-file-name-coding-system)))
1064 nowait ; t if emacsclient does not want to wait for us.
1065 frame ; Frame opened for the client (if any).
1066 display ; Open frame on this display.
1067 parent-id ; Window ID for XEmbed
1068 dontkill ; t if client should not be killed.
1069 commands
1070 dir
1071 use-current-frame
1072 frame-parameters ;parameters for newly created frame
1073 tty-name ; nil, `window-system', or the tty name.
1074 tty-type ; string.
1075 files
1076 filepos
1077 args-left)
1078 ;; Remove this line from STRING.
1084 ;; -version CLIENT-VERSION: obsolete at birth.
1087 ;; -nowait: Emacsclient won't wait for a result.
1090 ;; -current-frame: Don't create frames.
1093 ;; -frame-parameters: Set frame parameters
1100 ;; -display DISPLAY:
1101 ;; Open X frames on the given display instead of the default.
1106 ;; -parent-id ID:
1107 ;; Open X frame within window ID, via XEmbed.
1112 ;; -window-system: Open a new X frame.
1118 ;; -resume: Resume a suspended tty frame.
1125 commands)))
1127 ;; -suspend: Suspend the client's frame. (In case we
1128 ;; get out of sync, and a C-z sends a SIGTSTP to
1129 ;; emacsclient.)
1136 commands)))
1138 ;; -ignore COMMENT: Noop; useful for debugging emacsclient.
1139 ;; (The given comment appears in the server log.)
1144 ;; -tty DEVICE-NAME TYPE: Open a new tty frame.
1145 ;; (But if we see -window-system later, use that.)
1151 ;; On Windows, emacsclient always asks for a tty
1152 ;; frame. If running a GUI server, force the frame
1153 ;; type to GUI. (Cygwin is perfectly happy with
1154 ;; multi-tty support, so don't override the user's
1155 ;; choice there.) In daemon mode on Windows, we can't
1156 ;; make tty frames, so force the frame type to GUI
1157 ;; there too.
1163 ;; -position LINE[:COLUMN]: Set point to the given
1164 ;; position in the next file.
1175 ;; -file FILENAME: Load the given file.
1180 ;; Allow Cygwin's emacsclient to be used as a file
1181 ;; handler on MS-Windows, in which case FILENAME
1182 ;; might start with a drive letter.
1190 proc))
1193 ;; -eval EXPR: Evaluate a Lisp expression.
1201 commands)
1204 ;; -env NAME=VALUE: An environment variable.
1207 ;; XXX Variables should be encoded as in getenv/setenv.
1211 ;; -dir DIRNAME: The cwd of the emacsclient process.
1219 ;; Unknown command.
1222 ;; If both -no-wait and -tty are given with file or sexp
1223 ;; arguments, use an existing frame.
1233 ;; We can't use the Emacs daemon's
1234 ;; terminal frame.
1238 terminal-frame)))))
1246 parent-id
1247 frame-parameters))
1248 ;; When resuming on a tty, tty-name is nil.
1253 proc 'continuation
1256 ;; Use the same cwd as the emacsclient, if possible, so
1257 ;; relative file names work correctly, even in `eval'.
1260 dir default-directory)))
1262 dontkill frame tty-name)))))
1268 ;; condition-case
1272 ;; This is run from timers and process-filters, i.e. "asynchronously".
1273 ;; But w.r.t the user, this is not really asynchronous since the timer
1274 ;; is run after 0s and the process-filter is run in response to the
1275 ;; user running `emacsclient'. So it is OK to override the
1276 ;; inhibit-quit flag, which is good since `commands' (as well as
1277 ;; find-file-noselect via the major-mode) can run arbitrary code,
1278 ;; including code that needs to wait.
1284 ;; If we were told only to open a new client, obey
1285 ;; `initial-buffer-choice' if it specifies a file
1286 ;; or a function.
1297 ;; Delete the client if necessary.
1300 ;; Client requested nowait; return immediately.
1304 ;; This client is empty; get rid of it immediately.
1309 nil)
1332 ;; Before calling `delete-process', give emacsclient time to
1333 ;; receive the error string and shut down on its own.
1338 "Move point to the position indicated in LINE-COL.
1339 LINE-COL should be a pair (LINE . COL)."
1348 "Find FILES and return a list of buffers created.
1349 FILES is an alist whose elements are (FILENAME . FILEPOS)
1350 where FILEPOS can be nil or a pair (LINENUMBER . COLUMNNUMBER).
1351 PROC is the client that requested this operation.
1352 NOWAIT non-nil means this client is not waiting for the results,
1353 so don't mark these buffers specially, just visit them normally."
1354 ;; Bind last-nonmenu-event to force use of keyboard, not mouse, for queries.
1356 ;; Restore the current buffer afterward, but not using save-excursion,
1357 ;; because we don't want to save point in this buffer
1358 ;; if it happens to be one of those specified by the server.
1361 ;; If there is an existing buffer modified or the file is
1362 ;; modified, revert it. If there is an existing buffer with
1363 ;; deleted file, offer to write it.
1365 minibuffer-auto-raise))
1374 ;; separately for each file, in sync with post-command hooks,
1375 ;; with the new buffer current:
1389 ;; hooks may be specific to current buffer:
1392 ;; When the buffer is killed, inform the clients.
1399 client-record))
1406 This buries the buffer, then returns a list of the form (NEXT-BUFFER KILLED).
1407 NEXT-BUFFER is another server buffer, as a suggestion for what to select next,
1408 or nil. KILLED is t if we killed BUFFER (typically, because it was visiting
1409 a temp file).
1410 FOR-KILLING if non-nil indicates that we are called from `kill-buffer'."
1419 ;; Delete all dead buffers from PROC.
1425 ;; If client now has no pending buffers,
1426 ;; tell it that it is done, and forget it entirely.
1430 ;; `server-delete-client' might delete the client's
1431 ;; frames, which might change the current buffer. We
1432 ;; don't want that (bug#640).
1437 ;; We may or may not kill this buffer;
1438 ;; if we do, do not call server-buffer-done recursively
1439 ;; from kill-buffer-hook.
1444 ;; Notice whether server-done-hook killed the buffer.
1447 ;; Don't bother killing or burying the buffer
1448 ;; when we are called from kill-buffer.
1451 server-kill-new-buffers
1456 ;; Prevent kill-buffer from prompting (Bug#3696).
1471 "Return non-nil if BUFFER contains a file considered temporary.
1472 These are files whose names suggest they are repeatedly
1473 reused to pass information to another program.
1475 The variable `server-temp-file-regexp' controls which filenames
1476 are considered temporary."
1482 This kills or buries the buffer, then returns a list
1483 of the form (NEXT-BUFFER KILLED). NEXT-BUFFER is another server buffer,
1484 as a suggestion for what to select next, or nil.
1485 KILLED is t if we killed BUFFER, which happens if it was created
1486 specifically for the clients and did not exist before their request for it."
1489 ;; For a temp file, save, and do make a non-numeric backup
1490 ;; (unless make-backup-files is nil).
1495 buffer-file-name
1501 "Ask before exiting Emacs if it has live clients."
1507 live-client))
1511 "Remove the current buffer from its clients' buffer list.
1512 Designed to be added to `kill-buffer-hook'."
1513 ;; Prevent infinite recursion if user has made server-done-hook
1514 ;; call kill-buffer.
1520 \f
1524 The buffer is also killed if it did not exist before the clients asked for it.
1527 Temporary files such as MH <draft> files are always saved and backed up,
1528 no questions asked. (The variable `make-backup-files', if nil, still
1529 inhibits a backup; you can set it locally in a particular buffer to
1530 prevent a backup for it.) The variable `server-temp-file-regexp' controls
1531 which filenames are considered temporary.
1533 If invoked with a prefix argument, or if there is no server process running,
1545 "Switch to another buffer, preferably one that has a client.
1546 Arg NEXT-BUFFER is a suggestion; if it is a live buffer, use it.
1548 KILLED-ONE is t in a recursive call if we have already killed one
1549 temp-file server buffer. This means we should avoid the final
1551 done that.
1553 FILEPOS specifies a new buffer position for NEXT-BUFFER, if we
1554 visit NEXT-BUFFER in an existing window. If non-nil, it should
1555 be a cons cell (LINENUMBER . COLUMNNUMBER)."
1561 ;; Only look at frameless clients, or those in the selected
1562 ;; frame.
1569 ;; (switch-to-buffer (other-buffer))
1572 ;; If NEXT-BUFFER is a dead buffer, remove the server records for it
1573 ;; and try the next surviving server buffer.
1575 ;; OK, we know next-buffer is live, let's display and select it.
1580 ;; The buffer is already displayed: just reuse the
1581 ;; window. If FILEPOS is non-nil, use it to replace the
1582 ;; window's own value of point.
1588 ;; Otherwise, let's find an appropriate window.
1597 ;; Move to a non-dedicated window, if we have one.
1608 ;; After all the above, we might still have ended up with
1609 ;; a minibuffer/dedicated-window (if there's no other).
1614 ;;;###autoload
1616 ;; Called from save-buffers-kill-terminal in files.el.
1617 "Offer to save each buffer, then kill the current client.
1618 With ARG non-nil, silently save all file-visiting buffers, then kill.
1620 If emacsclient was started with a list of filenames to edit, then
1621 only these files will be asked to be saved."
1624 ;; Nowait frames have no client buffer list.
1628 ;; If we're the last frame standing, kill Emacs.
1632 ;; If client is bufferless, emulate a normal Emacs exit
1633 ;; and offer to save all buffers. Otherwise, offer to
1634 ;; save only the buffers belonging to the client.
1638 t))
1645 "Unload the Server library."
1652 ;; continue standard unloading
1653 nil)
1656 "Contact the Emacs server named SERVER and evaluate FORM there.
1657 Returns the result of the evaluation, or signals an error if it
1658 cannot contact the specified server. For example:
1665 address port secret process)
1682 :host address
1696 ;; If the result is nil, there's nothing in the buffer. If the
1697 ;; result is non-nil, it's after "-print ".
1709 \f
1712 ;;; server.el ends here