Re: bug in server-start

[Dan Nicolaescu]

Stefan Monnier <address@hidden> writes:

  > > What benefit does that bring?  Presumably, previously the first Emacs
  > > instance was the current server, which was fine with me.
  > 
  > No, as mentioned the second was "the current server", overriding
  > the first.  And when the second exits, it doesn't magically re-enable
  > the first.
  > So when starting the second (in Emacs-22), the first server is neutered,
  > but without even knowing it.  In Emacs-22 it was a problem, but a fairly
  > minor one.  With "emacs --daemon" this is now a much more serious
  > problem since if the daemon is thus neutered it will keep running
  > without the user having any way to access it: it can only look for it in
  > `ps' and kill it.

We could install something by default to restart the server when
receiving an USR1 or USR2 signal.

Also currently the daemon is broken:

emacs -Q -f server-start&

emacs --daemon 
Server "server" is already running

and the daemon is not started...