all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: peder@klingenberg.no (Peder O. Klingenberg)
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25708@debbugs.gnu.org, alexhutcheson@google.com
Subject: bug#25708: 25.1.91; Allow users to inhibit printing for 'emacsclient -c -t'
Date: Mon, 20 Feb 2017 19:28:28 +0100	[thread overview]
Message-ID: <m1zihgyawj.fsf@modesty> (raw)
In-Reply-To: <831suspxzf.fsf@gnu.org> (Eli Zaretskii's message of "Mon, 20 Feb 2017 19:34:44 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> Each comment should end with a period and 2 spaces.  Like this:

Sorry.  I'll fix it.

> Do we really need the "non-error" part here?  Errors don't manifest
> themselves via return values, I think.

I'm not intimately familiar with the protocol between emacs and
emacsclient, but emacsclient handles a number of different return
messages from emacs.  Two of which (-print and -print-nonl) I made -u
apply to.

Another possible return message seems to be -error, which also results
in stuff being printed by emacsclient (in this case to stderr).  -u does
not suppress that kind of printing.  I thought it worth specifying, but
if that path is in practice never used, I can take that wording out.
What do people think?

--
...Peder...





  reply	other threads:[~2017-02-20 18:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-13 19:46 bug#25708: 25.1.91; Allow users to inhibit printing for 'emacsclient -c -t' Alex Hutcheson
2017-02-19 20:54 ` Peder O. Klingenberg
2017-02-20  3:29   ` Eli Zaretskii
2017-02-20  8:58     ` Peder O. Klingenberg
2017-02-20 17:19       ` Peder O. Klingenberg
2017-02-20 17:34         ` Eli Zaretskii
2017-02-20 18:28           ` Peder O. Klingenberg [this message]
2017-02-20 18:04         ` Andreas Schwab
2017-02-20 18:13           ` Eli Zaretskii
2017-02-20 19:15             ` Andreas Schwab
2017-02-20 20:55               ` Peder O. Klingenberg
2017-02-25  8:33                 ` Eli Zaretskii
2017-02-20 18:17           ` Peder O. Klingenberg

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=m1zihgyawj.fsf@modesty \
    --to=peder@klingenberg.no \
    --cc=25708@debbugs.gnu.org \
    --cc=alexhutcheson@google.com \
    --cc=eliz@gnu.org \
    /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.