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

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Artiom Balan <artiombalan331 <at> gmail.com>
Cc: 76772 <at> debbugs.gnu.org
Subject: bug#76772: 
Date: Thu, 06 Mar 2025 16:13:31 +0200

> From: Artiom Balan <artiombalan331 <at> gmail.com>
> Date: Thu, 6 Mar 2025 10:56:29 +0200
> 
> > The *Warnings* buffer is there, it's just that the client frame doesn't show it.
> Sorry, yes that's what I meant.
> 
> > Why should it?
> For the same reason that the warnings buffer is displayed in a regular emacs instance if there have been any
> warnings emitted during startup.

Emacs displays it because that's the first command it executes after
starting.  By contrast, in the daemon case, there's no relation
between the --eval argument when starting the daemon and the client
frame displayed because emacsclient connected, these events could be
many minutes apart.

> > how should it know you want that particular buffer displayed without any indication from you?
> I think the warnings buffer should be displayed in the first emacsclient created after startup (if there are any
> warnings). Then the following clients shouldn't display the warnings buffer, because the user has already
> seen it.

I don't think your expectations are correct, but let's hear what
others think.

Previous Next

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