From: Lars Ingebrigtsen <larsi@gnus.org>
To: Gilles <gilles.usenet@gmail.com>
Cc: 47439@debbugs.gnu.org
Subject: bug#47439: 27.2; In daemon mode, if after-init-hook errors out, the server does not start
Date: Sun, 28 Mar 2021 15:56:01 +0200 [thread overview]
Message-ID: <87czvjs7pq.fsf@gnus.org> (raw)
In-Reply-To: <CAHf9+CvzPeg24rXeeN2c64CQGbhjyEPc0Kb0rF3bCtScSUGNhQ@mail.gmail.com> (Gilles's message of "Sun, 28 Mar 2021 03:00:40 +0200")
Gilles <gilles.usenet@gmail.com> writes:
> 1. Make an init file with the following line: (add-hook 'after-init-hook 'barf)
> 2. Start Emacs in daemon mode: HOME=$PWD emacs --no-site-file --daemon=foo
>
> Expected behavior: Emacs starts normally (including starting the
> server), with the error logged in *Messages* (and optionally on Emacs's
> stderr), as happens for errors in the init file or in
> emacs-startup-hook.
>
> Actual behavior: the server does not start, so there is no way to
> open a frame other than the initial daemon frame.
The doc string for this variable is pretty explicit about errors:
---
There is no `condition-case' around the running of this hook;
therefore, if `debug-on-error' is non-nil, an error in one of
these functions will invoke the debugger.
---
So I think this is expected behaviour? Anybody got an opinion?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2021-03-28 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 1:00 bug#47439: 27.2; In daemon mode, if after-init-hook errors out, the server does not start Gilles
2021-03-28 13:56 ` Lars Ingebrigtsen [this message]
2021-03-28 14:05 ` Eli Zaretskii
2021-03-28 14:43 ` Lars Ingebrigtsen
2021-03-28 14:55 ` Eli Zaretskii
2021-03-28 14:56 ` Lars Ingebrigtsen
2021-03-28 17:04 ` Gilles
2021-03-28 17:23 ` Eli Zaretskii
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=87czvjs7pq.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=47439@debbugs.gnu.org \
--cc=gilles.usenet@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.