From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: phst@google.com, 35328@debbugs.gnu.org
Subject: bug#35328: [PATCH] Improve documentation around standard error pipes (Bug#35328).
Date: Mon, 22 Apr 2019 12:25:52 +0300 [thread overview]
Message-ID: <834l6q8k7z.fsf@gnu.org> (raw)
In-Reply-To: <20190421161147.29403-1-phst@google.com> (message from Philipp Stephani on Sun, 21 Apr 2019 18:11:47 +0200)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Cc: 35328@debbugs.gnu.org,
> Philipp Stephani <phst@google.com>
> Date: Sun, 21 Apr 2019 18:11:47 +0200
>
> +If @var{stderr} is a buffer, Emacs will create a pipe process, the
> +@dfn{standard error process}. This process will have the default
As a general rule, any use of @dfn should have a corresponding @cindex
entry leading to the text. So please add one here.
> +If you have passed a non-@code{nil} @var{stderr} to
> +@code{make-process}, it will have a standard error process.
> +@xref{Asynchronous Processes}. In that case, waiting for process
> +output from the main process doesn't wait for output from the standard
> +error process. To make sure that you have received both standard
> +output and error from a process, use the following code:
Suggest a minor rewording of the last sentence:
To make sure you have received both all of standard output and all of
standard error from a process ...
Otherwise, LGTM, thanks.
next prev parent reply other threads:[~2019-04-22 9:25 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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=834l6q8k7z.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=35328@debbugs.gnu.org \
--cc=p.stephani2@gmail.com \
--cc=phst@google.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.