From: Oğuz <oguzismailuysal@gmail.com>
To: stephane.chazelas@gmail.com
Cc: zsh-users@zsh.org
Subject: Re: substituted command won't inherit stdin in pipeline
Date: Thu, 14 Nov 2019 11:43:49 +0300 [thread overview]
Message-ID: <CAH7i3Lo8UqebRn17sjmUh5M5AbmSTTFvV1a4EQOgRSbZxKyg3w@mail.gmail.com> (raw)
In-Reply-To: <20191114075727.kyilhlqwn5fyn4ur@chaz.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 984 bytes --]
On Thu, Nov 14, 2019 at 10:57 AM Stephane Chazelas <
stephane.chazelas@gmail.com> wrote:
[...]
> It's what zsh does.
>
Oh, okay then.
> IIRC, POSIX leaves it unspecified.
>
> It also leaves unspecified which pipeline component if any may
> be run in the current shell process.
>
The standard says
> Additionally, each command of a multi-command pipeline is in a subshell
> environment; as an extension, however, any or all commands in a pipeline
> may be executed in the current environment.
I thought this means each component of a pipeline should be executed in a
subshell, but as an *extension*, implementations may prefer executing some
of them in the current environment. Seems like I was wrong.
Btw, I installed a more recent version (5.7.1), and in the DESCRIPTION
section of manual it says
> It does not provide compatibility with POSIX or other shells in its
default
> operating mode...
Now this explains everything. Sorry if I wasted your time
> --
> Stephane
>
next prev parent reply other threads:[~2019-11-14 8:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAH7i3Lo57yAd==m7zF+8mtETqYDDSptmdzxF-2t_pu42fe9ztQ__41421.1000244663$1573638841$gmane$org@mail.gmail.com>
2019-11-13 13:00 ` Stephane Chazelas
2019-11-13 13:30 ` Oğuz
[not found] ` <CAH7i3LrwD4G0CJ3WvdWZsp5u-cSTQoGomSf6HHF1XG8NnA89Vw__34634.6754276723$1573691143$gmane$org@mail.gmail.com>
2019-11-14 7:57 ` Stephane Chazelas
2019-11-14 8:43 ` Oğuz [this message]
2019-11-14 9:35 ` Peter Stephenson
2019-11-14 9:38 ` Roman Perepelitsa
2019-11-13 9:52 Oğuz
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=CAH7i3Lo8UqebRn17sjmUh5M5AbmSTTFvV1a4EQOgRSbZxKyg3w@mail.gmail.com \
--to=oguzismailuysal@gmail.com \
--cc=stephane.chazelas@gmail.com \
--cc=zsh-users@zsh.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 public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).