From: Dan Nicolaescu <dann@ics.uci.edu>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: trentbuck@gmail.com, 1058@emacsbugs.donarmstrong.com,
Romain Francoise <romain@orebokech.com>
Subject: bug#1058: 23.0.60; emacs --daemon should not return until socket is ready
Date: Tue, 7 Oct 2008 08:31:47 -0700 (PDT) [thread overview]
Message-ID: <200810071531.m97FVlPt007507@mothra.ics.uci.edu> (raw)
In-Reply-To: <jwvej2s8oun.fsf-monnier+emacsbugreports@gnu.org> (Stefan Monnier's message of "Tue, 07 Oct 2008 10:26:46 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
> > Errors in ~/.emacs show up in the *Messages* buffer (as they do when
> > starting up normally).
There are multiple issues being discussed here.
1.
> But is the *Messages* buffer automatically displayed (as is done when
> starting up normally)?
Not yet, but it just takes one extra `if' to do it:
--- server.el.~1.168.~ 2008-09-24 17:34:59.000000000 -0700
+++ server.el 2008-10-07 08:09:16.000000000 -0700
@@ -606,7 +606,9 @@ Server mode runs a process that accepts
(process-put proc 'terminal (frame-terminal frame))
;; Display *scratch* by default.
- (switch-to-buffer (get-buffer-create "*scratch*") 'norecord)
+ (switch-to-buffer
+ (get-buffer-create
+ (if init-file-had-error "*Messages*" "*scratch*")) 'norecord)
;; Reply with our pid.
(server-send-string proc (concat "-emacs-pid "
2. During the normal interactive startup the splash screen nowadays
covers the *Messages* buffer too fast, so the user can miss the error.
I should file a bug about this...
> This is the main reason why I think that .emacs messages should go
> to stdout.
3. There's no code in emacs now that can do that for interactive
sessions, and when I looked at this it did not look that it can be a
small change acceptable during the feature freeze. The `noninteractive'
code has it's claws in too many places.
> Especially since the error might even be something that breaks the
> server, so you can't connect later on to take a look at the
> *Messages* buffer.
5. Making the output go to stdout does not avoid this problem at all, it
reduces the possibility somewhat, but it does not avoid it.
6. But my original code to start the server early minimizes the window
of opportunity for problems in starting the server, the more .emacs,
default.el, site-start.el code you run, the more potential for problems
in starting the server later. Yes, starting the server early was
entirely intentional.
7. This bug report is about something else:
emacs --daemon && emacsclient -c
not working. Romain's patch looks good, it does not add features, it's
just a bug fix, so I don't see any reason it cannot go in right now.
next prev parent reply other threads:[~2008-10-07 15:31 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-30 13:43 bug#1058: 23.0.60; emacs --daemon should not return until socket is ready SRS0+wOMF+22+gmail.com=trentbuck
2008-10-01 16:51 ` Dan Nicolaescu
2008-10-01 19:39 ` Romain Francoise
2008-10-01 20:19 ` Andreas Schwab
2008-10-02 6:05 ` Romain Francoise
2008-10-01 23:32 ` Dan Nicolaescu
2008-10-02 6:07 ` Romain Francoise
2008-10-02 8:14 ` Dan Nicolaescu
2008-10-02 12:38 ` Stefan Monnier
2008-10-02 17:26 ` Dan Nicolaescu
2008-10-02 21:32 ` Stefan Monnier
2008-10-02 22:34 ` Dan Nicolaescu
2008-10-02 22:46 ` Trent W. Buck
2008-10-03 1:12 ` Stefan Monnier
2008-10-03 4:52 ` Dan Nicolaescu
2008-10-03 13:00 ` Stefan Monnier
2008-10-03 17:44 ` Dan Nicolaescu
2008-10-13 2:03 ` Dan Nicolaescu
2008-10-13 15:16 ` Stefan Monnier
2008-10-13 17:01 ` Dan Nicolaescu
2008-10-13 19:07 ` Stefan Monnier
2008-10-14 7:26 ` Dan Nicolaescu
2008-10-27 7:04 ` Dan Nicolaescu
2008-10-02 22:42 ` Trent W. Buck
2008-10-02 17:54 ` Romain Francoise
2008-10-02 18:40 ` Dan Nicolaescu
2008-10-06 20:59 ` Dan Nicolaescu
2008-10-07 14:26 ` Stefan Monnier
2008-10-07 15:31 ` Dan Nicolaescu [this message]
2008-10-07 23:13 ` Trent W. Buck
2008-10-08 2:03 ` Stefan Monnier
2008-10-08 2:25 ` Stefan Monnier
2008-10-07 18:45 ` Romain Francoise
2008-10-07 19:01 ` Dan Nicolaescu
2008-10-26 19:24 ` Dan Nicolaescu
2008-10-02 0:50 ` Trent W. Buck
2008-10-02 0:43 ` Trent W. Buck
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200810071531.m97FVlPt007507@mothra.ics.uci.edu \
--to=dann@ics.uci.edu \
--cc=1058@emacsbugs.donarmstrong.com \
--cc=monnier@IRO.UMontreal.CA \
--cc=romain@orebokech.com \
--cc=trentbuck@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.