GNU bug report logs -
#57650
[29.0.50] Chatty Emacsclient: "Got response from server"
Previous Next
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 57650 in the body.
You can then email your comments to 57650 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57650
; Package
emacs
.
(Wed, 07 Sep 2022 17:23:02 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Jacob Faibussowitsch <jacob.fai <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Wed, 07 Sep 2022 17:23:02 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
To reproduce:
1. $ emacs -Q --daemon
2. $ emacsclient --tty --quiet
3. C-x C-c
4. Behold:
Got response from server
Note that if you do the above *without* --quiet, then no message is printed. It appears the message is printed from lib-src/emacsclient.c:2174.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57650
; Package
emacs
.
(Wed, 07 Sep 2022 18:26:02 GMT)
Full text and
rfc822 format available.
Message #8 received at 57650 <at> debbugs.gnu.org (full text, mbox):
> From: Jacob Faibussowitsch <jacob.fai <at> gmail.com>
> Date: Wed, 7 Sep 2022 13:22:20 -0400
>
> To reproduce:
>
> 1. $ emacs -Q --daemon
> 2. $ emacsclient --tty --quiet
> 3. C-x C-c
> 4. Behold:
>
> Got response from server
>
> Note that if you do the above *without* --quiet, then no message is printed. It appears the message is printed from lib-src/emacsclient.c:2174.
Then I don't understand the complaint: you _asked_ for more chatter by
specifying --quiet. Right?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57650
; Package
emacs
.
(Wed, 07 Sep 2022 18:32:01 GMT)
Full text and
rfc822 format available.
Message #11 received at 57650 <at> debbugs.gnu.org (full text, mbox):
> you _asked_ for more chatter by
> specifying --quiet. Right?
… I had to read that twice, but just so I understand the --quiet flag makes emacsclient display more to screen? Perhaps it should be renamed to --louder. Going from the help tooltip:
$ emacsclient --help
…
-q, --quiet Don't display messages on success
I was under the distinct impression this flag would make emacsclient well, quieter.
Best regards,
Jacob Faibussowitsch
(Jacob Fai - booss - oh - vitch)
> On Sep 7, 2022, at 14:25, Eli Zaretskii <eliz <at> gnu.org> wrote:
>
>> From: Jacob Faibussowitsch <jacob.fai <at> gmail.com>
>> Date: Wed, 7 Sep 2022 13:22:20 -0400
>>
>> To reproduce:
>>
>> 1. $ emacs -Q --daemon
>> 2. $ emacsclient --tty --quiet
>> 3. C-x C-c
>> 4. Behold:
>>
>> Got response from server
>>
>> Note that if you do the above *without* --quiet, then no message is printed. It appears the message is printed from lib-src/emacsclient.c:2174.
>
> Then I don't understand the complaint: you _asked_ for more chatter by
> specifying --quiet. Right?
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57650
; Package
emacs
.
(Wed, 07 Sep 2022 18:49:02 GMT)
Full text and
rfc822 format available.
Message #14 received at 57650 <at> debbugs.gnu.org (full text, mbox):
> From: Jacob Faibussowitsch <jacob.fai <at> gmail.com>
> Date: Wed, 7 Sep 2022 14:31:28 -0400
> Cc: 57650 <at> debbugs.gnu.org
>
> > you _asked_ for more chatter by
> > specifying --quiet. Right?
>
> … I had to read that twice, but just so I understand the --quiet flag makes emacsclient display more to screen? Perhaps it should be renamed to --louder.
Yes, I think --louder is a better name for the option, now that it
behaves like that.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57650
; Package
emacs
.
(Wed, 07 Sep 2022 19:27:02 GMT)
Full text and
rfc822 format available.
Message #17 received at 57650 <at> debbugs.gnu.org (full text, mbox):
On 9/7/2022 11:47 AM, Eli Zaretskii wrote:
>> From: Jacob Faibussowitsch <jacob.fai <at> gmail.com>
>> Date: Wed, 7 Sep 2022 14:31:28 -0400
>> Cc: 57650 <at> debbugs.gnu.org
>>
>>> you _asked_ for more chatter by
>>> specifying --quiet. Right?
>>
>> … I had to read that twice, but just so I understand the --quiet flag makes emacsclient display more to screen? Perhaps it should be renamed to --louder.
>
> Yes, I think --louder is a better name for the option, now that it
> behaves like that.
Looking at emacsclient.c, I think this is just a bug in the new timeout
handling. Everywhere else that --quiet is used, it means what
"emacsclient --help" says: "Don't display messages on success".
For example, 'set_local_socket' has this bit, which makes it pretty
explicit:
/* If there's an alternate editor and the user has requested
--quiet, don't output the warning. */
if (!quiet || !alternate_editor)
{
message (true,
("%s: can't find socket; have you started the server?\n"
"%s: To start the server in Emacs,"
" type \"M-x server-start\".\n"),
progname, progname);
}
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#57650
; Package
emacs
.
(Wed, 07 Sep 2022 21:51:01 GMT)
Full text and
rfc822 format available.
Message #20 received at 57650 <at> debbugs.gnu.org (full text, mbox):
close 57650 29.1
thanks
Jacob Faibussowitsch <jacob.fai <at> gmail.com> writes:
> 1. $ emacs -Q --daemon
> 2. $ emacsclient --tty --quiet
> 3. C-x C-c
> 4. Behold:
>
> Got response from server
Fixed on master (commit 901d3a2b5d). Thanks for the bug report.
bug marked as fixed in version 29.1, send any further explanations to
57650 <at> debbugs.gnu.org and Jacob Faibussowitsch <jacob.fai <at> gmail.com>
Request was from
Stefan Kangas <stefankangas <at> gmail.com>
to
control <at> debbugs.gnu.org
.
(Wed, 07 Sep 2022 21:51:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Thu, 06 Oct 2022 11:24:13 GMT)
Full text and
rfc822 format available.
This bug report was last modified 1 year and 194 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.