Re: emacsclient startup messages

[Pedro Andres Aranda Gutierrez]

Redirecting to stderr is a nice work-around ;-)

/PA

Enviado desde mi iPad

El 26 oct 2021, a las 14:18, Eli Zaretskii <eliz@gnu.org> escribió:

>> From: Pedro Andres Aranda Gutierrez <paaguti@gmail.com>
>> Date: Tue, 26 Oct 2021 07:26:35 +0200
>> 
>> I was used to the 
>> emacsclient: can't find socket; have you started the server?
>> emacsclient: To start the server in Emacs, type "M-x server-start".
>> messages and, despite finding them somehow annoying, well I could live with 
>> them :-)
>> 
>> Lately, this has grown to
>> emacsclient: Should XDG_RUNTIME_DIR='/run/user/1000' be in the environment?
>> emacsclient: (Be careful: XDG_RUNTIME_DIR is security-related.)
>> emacsclient: can't find socket; have you started the server?
>> emacsclient: To start the server in Emacs, type "M-x server-start".
>> in my Linux system and, well, it starts being too much...
>> 
>> even with a emacsclient -q there is no way to silence
>> emacsclient: Should XDG_RUNTIME_DIR='/run/user/1000' be in the environment?
>> emacsclient: (Be careful: XDG_RUNTIME_DIR is security-related.)
>> 
>> If I say quiet, I mean quiet and that should include this message... more so 
>> if they ask me maybe do
>> something that maybe I shouldn't because it is security related... 
> 
> That's not what -q is meant to do.  From the --help display:
> 
>  -q, --quiet        Don't display messages on success
> 
> IOW, it isn't supposed to suppress warning, only verbose messages
> about _successful_ actions.
> 
>> Isn't there any other way of saying this in a more positive way so that I 
>> either decide to take action or not?
>> Could'nt we also silence this warning in -q?
> 
> How about redirecting stderr to /dev/null?