GNU bug report logs - #1058
23.0.60; emacs --daemon should not return until socket is ready

Previous Next

Full log

View this message in rfc822 format

From: Dan Nicolaescu <dann <at> ics.uci.edu>
To: Stefan Monnier <monnier <at> iro.umontreal.ca>
Cc: 1058 <at> debbugs.gnu.org, trentbuck <at> gmail.com,
        Romain Francoise <romain <at> orebokech.com>
Subject: bug#1058: 23.0.60; emacs --daemon should not return until socket is ready
Date: Fri, 3 Oct 2008 10:44:10 -0700 (PDT)

Stefan Monnier <monnier <at> iro.umontreal.ca> writes:

  > > Hmm, you mean that after "emacs -Q --daemon" if you look with ps there's
  > > no emacs process at all?  And "emacsclient -t" does not connect to it?
  > 
  > Exactly.  But I haven't investigated further yet.  Most likely it's
  > a simple error somewhere that causes Emacs to exit but the message is
  > throw away.  

If this is with an up to date pristine tree, then please debug it, it's
very bad.  I have not seen anything like this on any of the systems that
I use.

  > That's exactly for these kinds of reasons that it's important to
  > keep sending messages to stdout at least until after the server is
  > started: otherwise debugging is a pain.

Well, but that is not how things work when using emacs normally
(i.e. interactive session without --daemon).  
  - Errors in .emacs are shown in the *Messages* buffer.  That still happens
  with --daemon.
  - Interactive questions (like a y-or-n-p in .emacs) get asked in the
  first emacs frame that appears.  I think we agree that something like
  this is ill formed for --daemon.  It would be nice if it failed more
  graciously, but I am not sure it can be easily done within the current
  constraints.


BTW, the splash screen covers that *Messages* buffer quite fast, so
errors at startup are not displayed for too long ...

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.