GNU bug report logs -
#35328
27.0.50; Lisp reference, "Accepting Output": Should describe what happens to standard error
Previous Next
Reported by: Philipp <p.stephani2 <at> gmail.com>
Date: Fri, 19 Apr 2019 19:38:01 UTC
Severity: minor
Found in version 27.0.50
Done: Philipp Stephani <p.stephani2 <at> gmail.com>
Bug is archived. No further changes may be made.
Full log
Message #31 received at 35328-done <at> debbugs.gnu.org (full text, mbox):
Am Mo., 22. Apr. 2019 um 11:26 Uhr schrieb Eli Zaretskii <eliz <at> gnu.org>:
>
> > From: Philipp Stephani <p.stephani2 <at> gmail.com>
> > Cc: 35328 <at> debbugs.gnu.org,
> > Philipp Stephani <phst <at> 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.
Thanks, pushed as 3b4e312cfe.
This bug report was last modified 6 years and 73 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.