unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Philipp <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: Sat, 20 Apr 2019 10:12:47 +0300	[thread overview]
Message-ID: <83k1fpb15c.fsf@gnu.org> (raw)
In-Reply-To: <m2imv9bxd9.fsf@gmail.com> (message from Philipp on Fri, 19 Apr 2019 21:36:50 +0200)

> From: Philipp <p.stephani2@gmail.com>
> Date: Fri, 19 Apr 2019 21:36:50 +0200
> 
> The Emacs Lisp manual section "Accepting Output" now documents how to
> read all output from a process (thanks!).  However, the section still
> lacks some discussion what happens to standard error.  Specifically, it
> should answer the following questions:
> 
> Does the code
> (while (accept-process-output PROC))
> also ensure that all of the standard error has been read and passed to
> the filter/inserted into the buffer?

I don't think I understand why you say that node doesn't already
answer this question.  Why did you think standard error is special in
this regard?





  reply	other threads:[~2019-04-20  7:12 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 [this message]
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

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=83k1fpb15c.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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).