From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 10313 invoked from network); 9 Jun 2020 07:58:34 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 9 Jun 2020 07:58:34 -0000 Received: (qmail 27984 invoked by alias); 9 Jun 2020 07:58:19 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 46029 Received: (qmail 28651 invoked by uid 1010); 9 Jun 2020 07:58:19 -0000 X-Qmail-Scanner-Diagnostics: from wout3-smtp.messagingengine.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25835. spamassassin: 3.4.4. Clear:RC:0(64.147.123.19):SA:0(-2.6/5.0):. Processed in 9.183512 secs); 09 Jun 2020 07:58:19 -0000 X-Envelope-From: d.s@daniel.shahaf.name X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at daniel.shahaf.name does not designate permitted sender hosts) X-ME-Sender: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduhedrudehfedguddvkecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpeffhffvuffkjghfofggtgfgsehtjedttdertddvnecuhfhrohhmpeffrghn ihgvlhcuufhhrghhrghfuceougdrshesuggrnhhivghlrdhshhgrhhgrfhdrnhgrmhgvqe enucggtffrrghtthgvrhhnpeefudetgeevhedvhfetveetvdduleduieejueduueejjedt teeutdejhfdtgfeiteenucfkphepjeelrddujeeirdefledrieelnecuvehluhhsthgvrh fuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomhepugdrshesuggrnhhivghlrdhs hhgrhhgrfhdrnhgrmhgv X-ME-Proxy: Date: Tue, 9 Jun 2020 07:57:28 +0000 From: Daniel Shahaf To: Peter Stephenson Cc: zsh-workers@zsh.org Subject: Re: [PATCH v2] exec: run final pipeline command in a subshell in sh mode Message-ID: <20200609075728.3c3941d8@tarpaulin.shahaf.local2> In-Reply-To: References: <20200605015338.1347787-1-sandals@crustytoothpaste.net> <20200605015338.1347787-2-sandals@crustytoothpaste.net> <20200605204144.GD6569@camp.crustytoothpaste.net> X-Mailer: Claws Mail 3.17.3 (GTK+ 2.24.32; x86_64-pc-linux-gnu) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Peter Stephenson wrote on Sun, 07 Jun 2020 18:24 +0100: > On Sun, 2020-06-07 at 09:55 -0700, Bart Schaefer wrote: > > On Fri, Jun 5, 2020 at 1:42 PM brian m. carlson > > 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. > > Yes, since I'm still here, that's my position too. > > Our general position on consistency is that we'll try our best to > keep native mode compatible, while with sh compatibility we'll > try to be like other shells and not worry so much about what zsh > used to do. This being the case, I'm happy to defer to consensus. I won't object to an entry in the list of incompatibilities in README, though. I can't speak for Mikael, of course. > But it's a little bit of an odd case here for all the reasons I won't > rehash. Thanks for the additional context, Daniel