bug#47439: 27.2; In daemon mode, if after-init-hook errors out, the server does not start

[Gilles <gilles.usenet@gmail.com>]

Looking at the code in startup.el, I think it would be ok to let
errors go uncaught (it would avoid any complication to debug those
errors), but the daemon should start anyway. How about putting most of
command-line in an unwind-protect? Or moving the daemon start outside
the unwind-protect in normal-top-level?

-- Gilles

On Sun, 28 Mar 2021 at 16:56, Lars Ingebrigtsen <larsi@gnus.org> wrote:
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> > You mean, catching the error if we are starting the daemon? that's one
> > possibility, assuming that the error message will then be visible when
> > the first client connects.
> >
> > In non-daemon mode I think we should keep not catching errors.
>
> Yup, and yup.
>
> --
> (domestic pets only, the antidote for overdose, milk.)
>    bloggy blog: http://lars.ingebrigtsen.no