> Why is it a problem to look in *Messages* and *Warnings*, if you are
interested in any messages there?

The problem is that warnings can pop up unexpectedly, and if you're not
automatically notified of them you will simply miss them.




On Thu, Mar 6, 2025, 4:43 PM Eli Zaretskii <eliz@gnu.org> wrote:

> > From: Artiom Balan <artiombalan331@gmail.com>
> > Date: Thu, 6 Mar 2025 16:33:08 +0200
> > Cc: Stefan Kangas <stefankangas@gmail.com>, 76772@debbugs.gnu.org
> >
> > With the --eval I tried to simulate an error happening during the
> execution of the init.el, for example.
>
> Understood.
>
> > I don't understand why it shouldn't be the case (at least in principle)
> that the client automatically displays the
> > warnings that were emitted during the server startup. How else should
> you be notified of the warnings? Are
> > you supposed to remember to display it manually or hack your way around
> it?
>
> The client frames display messages and warnings triggered by showing
> what emacsclient told the server to execute and show.  Anything else
> needs to be explicitly requested to show on display, since the daemon
> has no idea that the client connection is related in any way to the
> message or warning or any other buffer Emacs pops due to what happened
> in the server itself, _before_ the client connected.
>
> Why is it a problem to look in *Messages* and *Warnings*, if you are
> interested in any messages there?
>