From: Michael Albinus <michael.albinus@gmx.de>
To: Eli Zaretskii <eliz@gnu.org>
Cc: phst@google.com, emacs-devel@gnu.org
Subject: Re: master 3b4e312: Improve documentation around standard error pipes (Bug#35328).
Date: Tue, 23 Apr 2019 14:05:38 +0200 [thread overview]
Message-ID: <87d0ld7wq5.fsf@gmx.de> (raw)
In-Reply-To: <8336m9583y.fsf@gnu.org> (Eli Zaretskii's message of "Tue, 23 Apr 2019 13:28:01 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
> Maybe. But what do you mean by "different implementation" here:
>
>> ! process object. The @code{:stderr} argument cannot be a pipe; if it
>> ! is a buffer a different implementation will be used to show the buffer
>> ! contents. ^^^^^^^^^^^^^^^^^^^^^^^^
>
> This sounds vague and begs questions. Can we be more clear?
I don't believe implementation details belong into that manual. What about
The @code{:stderr} argument cannot be a pipe process, file name handlers
do not support pipe processes for this. A buffer as @code{:stderr}
argument is accepted, its contents is shown without the use of pipe processes.
Best regards, Michael.
next prev parent reply other threads:[~2019-04-23 12:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190422140753.20611.97812@vcs0.savannah.gnu.org>
[not found] ` <20190422140756.5C1042088F@vcs0.savannah.gnu.org>
2019-04-22 20:59 ` master 3b4e312: Improve documentation around standard error pipes (Bug#35328) Michael Albinus
2019-04-23 5:45 ` Eli Zaretskii
2019-04-23 7:11 ` Michael Albinus
2019-04-23 10:28 ` Eli Zaretskii
2019-04-23 12:05 ` Michael Albinus [this message]
2019-04-23 12:16 ` Eli Zaretskii
2019-04-23 14:09 ` Michael Albinus
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=87d0ld7wq5.fsf@gmx.de \
--to=michael.albinus@gmx.de \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--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 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).