[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: save-buffers-kill-terminal and emacsclient --no-wait
From: |
Thorsten Bonow |
Subject: |
Re: save-buffers-kill-terminal and emacsclient --no-wait |
Date: |
Wed, 31 Dec 2008 11:06:49 +0100 (CET) |
>>>>> "Ulrich" == Ulrich Mueller <address@hidden> writes:
Ulrich> Hi, is the following a bug, or the intended behaviour:
Ulrich> $ emacs --daemon $ emacsclient --create-frame --no-wait
Ulrich> Now save-buffers-kill-terminal (bound to C-x C-c) in this frame does
Ulrich> just nothing.
Ulrich> I would expect it to do the following:
Ulrich> - offer to save buffers
Ulrich> - call delete-frame
Not if you had read the manual ;-) It is the documented behaviour:
If you type `C-x C-c' (`save-buffers-kill-terminal') in an Emacs
frame created with `emacsclient', via the `-c' or `-t' options, Emacs
deletes the frame instead of killing the Emacs process itself. On a
text-only terminal frame created with the `-t' option, this returns
control to the terminal. Emacs also marks all the server buffers for
the client as finished, as though you had typed `C-x #' in all of them.
When Emacs is started as a daemon, all frames are considered client
frames, so `C-x C-c' will never kill Emacs. To kill the Emacs process,
type `M-x kill-emacs'.
(Quoted from "42.2 `emacsclient' Options")
Ulrich> Ulrich
Best wishes for the new year and all that ...
Toto
--
Contact information and PGP key at
http://www.withouthat.org/~toto/contact.html
...wir sind Deserteure! Kein Land auf das ich schw$(D+S(Bre.
Wolf Mahn und die Deserteure