Re: 23.0.60; Emacs should survive a lost X connection

[Stefan Monnier <monnier@iro.umontreal.ca>]

>> >> No, the crashes are gone.  But the server does not seem to know that the
>> >> clients have gone, it gives a warning when trying to exit because it
>> >> thinks that clients are still connected.
>> >> 
>> >> I do not understand.  When you say "server" do you mean "X server"?
>> 
>> > No, I mean the emacs server, i.e. the one started by M-x server-start.
>> 
>> >> Do you mean that it doesn't notice that it has been disconnected
>> >> from Emacs?
>> 
>> > No, the emacs server keeps track of the number of emacsclients that are
>> > still connected, when that number is > 0 and you are doing C-x C-c it
>> > will warn that emacsclients are still connected 
>> > (see server-kill-emacs-query-function)
>> 
>> > In the case described here, there are no emacsclients that are still
>> > connected (they have died when X has died, or have been killed with
>> > xkill), but the server thinks otherwise.
>> 
>> Actually, server.el does not keep track of a count of client, it keeps
>> track of actual clients directly, so we should be able to check
>> the client's liveness and discard the dead ones.
>> 
>> I lost the beginning of this thread, could you give a recipe and
>> description for this problem?

> emacs -Q -nw -f server-start

> emacsclient -c -d $DISPLAY&

> xkill 
> the emacsclient X11 frame

> then C-x C-c in the emacs -nw frame will warn about clients still being
> connected.

Indeed I can reproduce the problem, but the emacsclient is indeed not
dead, so the warning isn't wrong.  But I guess the problem here is that
since the emacsclient asked "-c" and did not specify any file to visit,
it would make a lot of sense to terminate the emacsclient when the frame
gets deleted.


        Stefan