From: Philipp Stephani <p.stephani2@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: phst@google.com, emacs-devel@gnu.org
Subject: Re: [PATCH 1/3] Document that 'make-process' mixes the output streams
Date: Sat, 07 Apr 2018 20:18:19 +0000 [thread overview]
Message-ID: <CAArVCkTh6WcXhCqGDzwuwGwhCsgcprhjTo7hsEKC7HoROv7SXA@mail.gmail.com> (raw)
In-Reply-To: <8360573yke.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 1169 bytes --]
Eli Zaretskii <eliz@gnu.org> schrieb am Mi., 4. Apr. 2018 um 15:12 Uhr:
> > From: Philipp Stephani <p.stephani2@gmail.com>
> > Date: Wed, 4 Apr 2018 14:02:16 +0200
> > Cc: Philipp Stephani <phst@google.com>
> >
> > * doc/lispref/processes.texi (Asynchronous Processes):
> > * src/process.c (Fmake_process): Document that standard error is mixed
> > with standard output if STDERR is nil.
>
> Thanks.
>
> > +(ert-deftest make-process/mix-stderr ()
> > + "Check that ‘make-process’ mixes the output streams if STDERR is nil."
> > + (skip-unless (executable-find shell-file-name))
> > + (with-temp-buffer
> > + (let ((process (make-process
> > + :name "mix-stderr"
> > + :command (list shell-file-name shell-command-switch
> > + "echo stdout; echo stderr >&2")
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> This shell command is non-portable: on Windows you have to use "&"
> instead of ";" to chain commands. You could use "&&", which in this
> case will do the same on both Posix and Windows systems.
>
Done and pushed to master.
[-- Attachment #2: Type: text/html, Size: 1785 bytes --]
prev parent reply other threads:[~2018-04-07 20:18 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
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 [this message]
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=CAArVCkTh6WcXhCqGDzwuwGwhCsgcprhjTo7hsEKC7HoROv7SXA@mail.gmail.com \
--to=p.stephani2@gmail.com \
--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).