GNU bug report logs - #76772
29.4; Emacsclient doesn't display warnings emitted during daemon startup

Previous Next

Full log

Message #28 received at 76772 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Artiom Balan <artiombalan331 <at> gmail.com>
Cc: 76772 <at> debbugs.gnu.org, stefankangas <at> gmail.com
Subject: Re: bug#76772: 29.4; Emacsclient doesn't display warnings emitted
 during daemon startup
Date: Thu, 06 Mar 2025 16:42:46 +0200

> From: Artiom Balan <artiombalan331 <at> gmail.com>
> Date: Thu, 6 Mar 2025 16:33:08 +0200
> Cc: Stefan Kangas <stefankangas <at> gmail.com>, 76772 <at> 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?

Previous Next

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