Re: annoying behavior of emacs --daemon

[Miles Bader <miles@gnu.org>]

Dan Nicolaescu <dann@ics.uci.edu> writes:
>   > When using --daemon, you initially have no frames.  You can then make
>   > new frames with emacsclient -c or emacsclient -t, but if they're X
>   > frames, closing the last such created frame (with C-x # or C-x C-c)
>   > kills the emacs process!
>
> I can't reproduce this...
>
> Can you reproduce this with 
> emacs -Q --daemon
> ?

Sure:

   $ emacs --daemon -Q 
   ("emacs" "-Q")
   For information about GNU Emacs and the GNU system, type C-h C-a.
   $ pidof emacs
   9730 9424
   $ emacsclient -c ~/.bashrc 
   Waiting for Emacs...
   <... close emacs window with C-x C-c or C-x # ...>
   $ pidof emacs
   9424

[The 9424 process is my normal long-lived emacs process, but emacsclient
seems to connect to the last-started process.]

If I use emacsclient -t, on the other hand:

   $ emacs --daemon -Q 
   ("emacs" "-Q")
   For information about GNU Emacs and the GNU system, type C-h C-a.
   $ pidof emacs
   9744 9424
   $ emacsclient -t ~/.bashrc 
   <... close emacs window with C-x C-c or C-x # ...>
   $ pidof emacs
   9744 9424

The same thing happens whether I kill the window with C-x C-c (bound to
`save-buffers-kill-terminal'), or C-x # (bound to `server-edit').

Emacs is checked out from CVS this morning.

-Miles

-- 
Immortality, n.  A toy which people cry for, And on their knees apply for,
      Dispute, contend and lie for, And if allowed Would be right proud
      Eternally to die for.