GNU bug report logs - #35328
27.0.50; Lisp reference, "Accepting Output": Should describe what happens to standard error

Previous Next

Package: emacs;

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 #17 received at 35328 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Philipp Stephani <p.stephani2 <at> gmail.com>
Cc: 35328 <at> debbugs.gnu.org
Subject: Re: bug#35328: 27.0.50; Lisp reference, "Accepting Output": Should
 describe what happens to standard error
Date: Sun, 21 Apr 2019 22:12:11 +0300
> From: Philipp Stephani <p.stephani2 <at> gmail.com>
> Date: Sun, 21 Apr 2019 15:58:11 +0200
> Cc: 35328 <at> debbugs.gnu.org
> 
> > > 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?
> 
> The node doesn't describe what happens with standard error, e.g.
> whether standard error is part of "output" and how it's handled.

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?  If it is, we only need to clarify that both standard
output and standard error are included.




This bug report was last modified 6 years and 29 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.