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
Eli Zaretskii <eliz <at> gnu.org> writes:
>> AFAIU, some people start emacs-server from, for example, systemd, and
>> only ever pop up an Emacs frame with emacsclient. They might never see
>> the warnings.
>>
>> If we expect people to manually check the *Warnings* buffer, this sounds
>> to me as the same as saying either
>> 1. warnings are not important to display, or
>> 2. warnings are not important to display to users that use
>> emacs-server+emacsclient
>>
>> If our reply is (2), which sounds more plausible, then I think that must
>> be justified somehow.
>
> If we want the first client connection to show the important messages
> from the startup phase of the daemon, then warnings is not the only
> thing, and not even the most important thing, that needs to be shown.
> We should also show any errors and important echo-area messages, since
> that's what the user will get when he/she starts Emacs normally with
> the same init files and command-line arguments. This requires some
> infrastructure we don't currently have, AFAIK. If you or someone else
> want to work on such an infrastructure, I won't object to then using
> it as part of the first client connection. But talking only about
> *Warnings* makes little sense to me, since displaying that upon the
> first connection already needs some minimal infrastructure we don't
> have, and if we are going to develop such infrastructure, let's do it
> right from the get-go.
Fully agreed on all of the above.
This sounds to me like: patches welcome to implement the above.
This bug report was last modified 103 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.