From: Eli Zaretskii <eliz@gnu.org>
To: Philipp Stephani <p.stephani2@gmail.com>
Cc: phst@google.com, emacs-devel@gnu.org
Subject: Re: [PATCH 2/3] Don't print "process finished" into the stderr buffer.
Date: Sat, 20 Apr 2019 10:30:59 +0300 [thread overview]
Message-ID: <83imv9b0b0.fsf@gnu.org> (raw)
In-Reply-To: <CAArVCkQaBFyyKem-NXmjDsRsFJevpt=zpmDO0D9K3aCm4kUXzg@mail.gmail.com> (message from Philipp Stephani on Fri, 19 Apr 2019 21:28:32 +0200)
> From: Philipp Stephani <p.stephani2@gmail.com>
> Date: Fri, 19 Apr 2019 21:28:32 +0200
> Cc: Emacs developers <emacs-devel@gnu.org>, Philipp Stephani <phst@google.com>
>
> > But I'm guessing that the current behavior was unexpected for some
> > reason, and that's why you looked in the documentation. If the guess
> > is correct, could you describe why it was unexpected/unwanted?
>
> It's unexpected that Emacs writes something. This is an instance of
> the general case that by default you expect nothing to happen instead
> of something, unless you request the "something". For example, after
> $ echo foo > bar
> would you expect that the file "bar" contains content other than
> "foo\n" because the shell decides to write additional text before
> closing redirections? This is the same thing.
But Emacs does that for ages, so in Emacs this is veteran behavior of
the default sentinel function.
> The documentation for make-process doesn't state that if :stderr is a
> buffer, make-process creates a pipe process with the default sentinel;
Actually, it does, albeit in the parent section:
Alternatively, you could use the ‘:stderr’ parameter with a non-‘nil’
value in a call to ‘make-process’ (*note make-process: Asynchronous
Processes.) to make the destination of the error output separate from
the standard output; in that case, Emacs will use pipes for
communicating with the subprocess.
next prev parent reply other threads:[~2019-04-20 7:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 12:02 [PATCH 1/3] Document that 'make-process' mixes the output streams Philipp Stephani
2018-04-04 12:02 ` [PATCH 2/3] Don't print "process finished" into the stderr buffer Philipp Stephani
2018-04-04 13:14 ` Eli Zaretskii
2018-04-07 20:21 ` Philipp Stephani
2018-04-08 13:13 ` Eli Zaretskii
2018-04-10 4:14 ` Stephen Leake
2018-04-10 4:59 ` Eli Zaretskii
2019-04-19 19:28 ` Philipp Stephani
2019-04-20 7:30 ` Eli Zaretskii [this message]
2019-04-21 13:55 ` Philipp Stephani
2019-04-21 19:09 ` Eli Zaretskii
2019-04-21 20:57 ` Stefan Monnier
2019-04-22 9:37 ` Eli Zaretskii
2019-04-22 14:43 ` Stefan Monnier
2019-04-22 15:23 ` Eli Zaretskii
2019-04-22 15:45 ` Philipp Stephani
2019-04-22 15:52 ` Eli Zaretskii
2018-04-04 12:02 ` [PATCH 3/3] Inherit process output coding system to stderr process Philipp Stephani
2018-04-04 13:39 ` Eli Zaretskii
2018-04-07 21:12 ` Philipp Stephani
2018-04-08 13:18 ` Eli Zaretskii
2018-04-08 16:39 ` Eli Zaretskii
2018-04-04 13:12 ` [PATCH 1/3] Document that 'make-process' mixes the output streams Eli Zaretskii
2018-04-07 20:18 ` Philipp Stephani
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=83imv9b0b0.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=p.stephani2@gmail.com \
--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 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.