From: Noam Postavsky <npostavs@users.sourceforge.net>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: Philipp Stephani <p.stephani2@gmail.com>, 30349@debbugs.gnu.org
Subject: bug#30349: 27.0.50; Cuonfusing documentation about pipe processes
Date: Tue, 6 Feb 2018 11:44:53 -0500 [thread overview]
Message-ID: <CAM-tV-91VQgaTEJQfLyQQT290nvT+6PSd4LH2ZjqKSQzwH7KHQ@mail.gmail.com> (raw)
In-Reply-To: <87fu6euljs.fsf@tcd.ie>
On Tue, Feb 6, 2018 at 11:31 AM, Basil L. Contovounesios
<contovob@tcd.ie> wrote:
>>>> > ":buffer BUFFER -- BUFFER is the buffer (or buffer-name) to associate
>>>> > with the process. Process output goes at the end of that buffer,
>>>> > unless you specify an output stream or filter function to handle the
>>>> > output."
>>>> >
>>>> > => How do you specify an output stream?
>>>>
>>>> I don't think there is such a thing. That phrase seems to have been
>>>> copied across all the make-*-process functions.
>>>
>>> And is wrong in all of them?
>>
>> I think so.
>>
>>> Could it be that the phrase originally meant shell-style redirection?
>>
>> Perhaps, but none of those functions support that, as far as I know.
>
> No relation to '(elisp) Output Streams'?
I don't see anything in the process code that would be able to take an
Elisp stream.
next prev parent reply other threads:[~2018-02-06 16:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-04 16:29 bug#30349: 27.0.50; Cuonfusing documentation about pipe processes Philipp
2018-02-04 17:46 ` Eli Zaretskii
2018-02-06 0:53 ` Noam Postavsky
2018-02-06 3:54 ` Eli Zaretskii
2018-02-06 12:10 ` Noam Postavsky
2018-02-06 16:31 ` Basil L. Contovounesios
2018-02-06 16:44 ` Noam Postavsky [this message]
2018-02-06 18:55 ` Eli Zaretskii
2018-02-07 0:05 ` Noam Postavsky
2018-02-07 3:40 ` Eli Zaretskii
2018-02-08 1:24 ` Noam Postavsky
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=CAM-tV-91VQgaTEJQfLyQQT290nvT+6PSd4LH2ZjqKSQzwH7KHQ@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=30349@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=p.stephani2@gmail.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).