* [multi-tty] server-process set to nil
@ 2007-05-21 11:50 Juanma Barranquero
0 siblings, 0 replies; only message in thread
From: Juanma Barranquero @ 2007-05-21 11:50 UTC (permalink / raw)
To: Emacs-Devel
The multi-tty's server.el has (among many others) this difference with
the HEAD one:
;; Now any previous server is properly stopped.
- (unless leave-dead
+ (if leave-dead
+ (progn
+ (server-log (message "Server stopped"))
+ (setq server-process nil))
(let* ((server-dir (if server-use-tcp server-auth-dir server-socket-dir))
(server-file (expand-file-name server-name server-dir)))
Is there any reason to set server-process to nil? I find very
convenient the HEAD behavior of having the dead process still in
server-process (until a new server is created, of course), because I
attach properties to it when it is created and I use them at
kill-emacs-hook time.
Juanma
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2007-05-21 11:50 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-05-21 11:50 [multi-tty] server-process set to nil Juanma Barranquero
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).