all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jim Porter <jporterbugs@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>, Jacob Faibussowitsch <jacob.fai@gmail.com>
Cc: 57650@debbugs.gnu.org
Subject: bug#57650: [29.0.50] Chatty Emacsclient: "Got response from server"
Date: Wed, 7 Sep 2022 12:26:06 -0700	[thread overview]
Message-ID: <7abd27b0-8ae5-b046-341f-64988b5cb9ac@gmail.com> (raw)
In-Reply-To: <83czc7ggxf.fsf@gnu.org>

On 9/7/2022 11:47 AM, Eli Zaretskii wrote:
>> From: Jacob Faibussowitsch <jacob.fai@gmail.com>
>> Date: Wed, 7 Sep 2022 14:31:28 -0400
>> Cc: 57650@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);
	}





  reply	other threads:[~2022-09-07 19:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-07 17:22 bug#57650: [29.0.50] Chatty Emacsclient: "Got response from server" Jacob Faibussowitsch
2022-09-07 18:25 ` Eli Zaretskii
2022-09-07 18:31   ` Jacob Faibussowitsch
2022-09-07 18:47     ` Eli Zaretskii
2022-09-07 19:26       ` Jim Porter [this message]
2022-09-07 21:50 ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7abd27b0-8ae5-b046-341f-64988b5cb9ac@gmail.com \
    --to=jporterbugs@gmail.com \
    --cc=57650@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=jacob.fai@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.