From: "Paul A. Steckler" <steck@stecksoft.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 24287@debbugs.gnu.org
Subject: bug#24287: Process filters received stderr output, not documented
Date: Mon, 22 Aug 2016 15:08:47 -0400 [thread overview]
Message-ID: <CAMSKV5edL8wd_4yp3jH+EsJxXuEwCWABE15hcdUdnWNhF3GNWQ@mail.gmail.com> (raw)
In-Reply-To: <83y43ofysz.fsf@gnu.org>
That's true, but the documentation for filter functions is misleading.
It specifically mentions the standard output of the associated
process, but neglects to mention the standard error.
Also, one might not see that earlier section when looking at the
documentation for filter functions. I did not see that section, in
fact, when using the manual to help me write my code.
-- Paul
On Mon, Aug 22, 2016 at 2:23 PM, Eli Zaretskii <eliz@gnu.org> wrote:
>> From: "Paul A. Steckler" <steck@stecksoft.com>
>> Date: Mon, 22 Aug 2016 13:35:25 -0400
>>
>> The documentation for Process Filter Functions mentions that process
>> filters receive the standard output from their associated processes. It
>> does not mention that the filters also receive standard error output.
>
> That is described in the parent section:
>
> It is impossible to separate the standard output and standard error
> streams of the subprocess, because Emacs normally spawns the subprocess
> inside a pseudo-TTY, and a pseudo-TTY has only one output channel. If
> you want to keep the output to those streams separate, you should
> redirect one of them to a file—for example, by using an appropriate
> shell command.
next prev parent reply other threads:[~2016-08-22 19:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-22 17:35 bug#24287: Process filters received stderr output, not documented Paul A. Steckler
2016-08-22 18:23 ` Eli Zaretskii
2016-08-22 18:38 ` Clément Pit--Claudel
2016-08-22 19:15 ` Eli Zaretskii
2016-08-22 19:08 ` Paul A. Steckler [this message]
2016-08-23 21:47 ` Clément Pit--Claudel
2016-08-24 14:44 ` Eli Zaretskii
2016-08-24 15:18 ` Clément Pit--Claudel
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=CAMSKV5edL8wd_4yp3jH+EsJxXuEwCWABE15hcdUdnWNhF3GNWQ@mail.gmail.com \
--to=steck@stecksoft.com \
--cc=24287@debbugs.gnu.org \
--cc=eliz@gnu.org \
/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.