all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: 35328@debbugs.gnu.org
Subject: bug#35328: 27.0.50; Lisp reference, "Accepting Output": Should describe what happens to standard error
Date: Mon, 22 Apr 2019 12:26:34 +0300	[thread overview]
Message-ID: <8336ma8k6t.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkTXE5KGVXOjxCyVYSbSsc9J6WauTfyYMd=wA+3GkH_Urw@mail.gmail.com> (message from Philipp Stephani on Mon, 22 Apr 2019 11:14:19 +0200)

> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Mon, 22 Apr 2019 11:14:19 +0200
> Cc: 35328@debbugs.gnu.org
> 
> > Well, it says "output", not "standard output".  I take it to mean both
> > output streams.  If the text is interpreted to mean both streams, is
> > it accurate?
> 
> I don't think so. At least empirically one has to wait for the
> standard error process separately to ensure that all standard error is
> read. I've sent a patch to extend the documentation to say that, is
> that ok?

Yes, modulo my minor comments there.

Thanks.





      reply	other threads:[~2019-04-22  9:26 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19 19:36 bug#35328: 27.0.50; Lisp reference, "Accepting Output": Should describe what happens to standard error Philipp
2019-04-20  7:12 ` Eli Zaretskii
2019-04-21 13:58   ` Philipp Stephani
2019-04-21 16:11     ` bug#35328: [PATCH] Improve documentation around standard error pipes (Bug#35328) Philipp Stephani
2019-04-22  9:25       ` Eli Zaretskii
2019-04-22 14:08         ` Philipp Stephani
2019-04-21 19:12     ` bug#35328: 27.0.50; Lisp reference, "Accepting Output": Should describe what happens to standard error Eli Zaretskii
2019-04-22  9:14       ` Philipp Stephani
2019-04-22  9:26         ` Eli Zaretskii [this message]

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=8336ma8k6t.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35328@debbugs.gnu.org \
    --cc=p.stephani2@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.