From: Bart Schaefer <schaefer@brasslantern.com>
To: "brian m. carlson" <sandals@crustytoothpaste.net>
Cc: "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [PATCH v2] exec: run final pipeline command in a subshell in sh mode
Date: Sun, 7 Jun 2020 09:55:54 -0700 [thread overview]
Message-ID: <CAH+w=7aq+U5Ap-aqcDXuLtctT3Pu3WFLzOQA6u7xmn7xyUU5Og@mail.gmail.com> (raw)
In-Reply-To: <20200605204144.GD6569@camp.crustytoothpaste.net>
On Fri, Jun 5, 2020 at 1:42 PM brian m. carlson
<sandals@crustytoothpaste.net> wrote:
>
> I will tell you that as a practical matter, nobody writing code for sh
> expects the last command not to be run in a subshell and consequently
> lots of code is practically broken in this case with zsh as /bin/sh.
I believe you, but would be curious to see an example.
For what it's worth, I'm not opposed to this patch. I think it's
pretty unlikely that anyone is invoking zsh as sh and still expecting
to be able to (for example) pipe into read to set variables in the
current shell.
next prev parent reply other threads:[~2020-06-07 16:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-05 1:53 [PATCH v2 0/1] Run pipeline command in " brian m. carlson
2020-06-05 1:53 ` [PATCH v2] exec: run final pipeline command in a " brian m. carlson
2020-06-05 10:21 ` Mikael Magnusson
2020-06-05 20:41 ` brian m. carlson
2020-06-06 4:33 ` [PATCH v2] exec: run final pipeline command in a subshell in sh modeZZ Daniel Shahaf
2020-06-06 16:28 ` brian m. carlson
2020-06-07 11:29 ` Daniel Shahaf
2020-06-07 16:55 ` Bart Schaefer [this message]
2020-06-07 17:24 ` [PATCH v2] exec: run final pipeline command in a subshell in sh mode Peter Stephenson
2020-06-09 7:57 ` Daniel Shahaf
2020-06-09 10:54 ` Mikael Magnusson
2020-06-17 18:26 ` Daniel Shahaf
2020-07-03 20:16 ` brian m. carlson
2020-06-11 0:24 ` brian m. carlson
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='CAH+w=7aq+U5Ap-aqcDXuLtctT3Pu3WFLzOQA6u7xmn7xyUU5Og@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=sandals@crustytoothpaste.net \
--cc=zsh-workers@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).