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 1045 invoked from network); 7 Jun 2020 16:56:52 -0000 Received: from ns1.primenet.com.au (HELO primenet.com.au) (203.24.36.2) by inbox.vuxu.org with ESMTPUTF8; 7 Jun 2020 16:56:52 -0000 Received: (qmail 18780 invoked by alias); 7 Jun 2020 16:56:41 -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: 46019 Received: (qmail 4284 invoked by uid 1010); 7 Jun 2020 16:56:41 -0000 X-Qmail-Scanner-Diagnostics: from mail-oi1-f195.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.102.3/25828. spamassassin: 3.4.4. Clear:RC:0(209.85.167.195):SA:0(-1.9/5.0):. Processed in 1.883781 secs); 07 Jun 2020 16:56:41 -0000 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.167.195 as permitted sender) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=F2X99XrTTBD+5HiMyxg49Itxo6Mm8XwlAkvtcchdYsU=; b=nX5V3SYMN4nNfHGNJfzp59ViJx+13E0e4t3RgrmDIvFlTuz679/qmbfmaxROS01WNi lBzJJr5qrUyNCJWcayhseNfGA2gC4gZEXBvei4aQrkqQ78FimtZzSC+i8d1qZ/L+QvKv EIwQUrHcoeg8UCzCyyMPl9Q94nUrXKcQuGulQ02RD3pklGDGpCZSFbMyWZNVhwc41kG1 yQN+4bu1GJv5lkSkbJoKxfUUQj3GBKFhj+P6S7EmFPF4vir/vZO6jU/ZTykrNjB1Xm1y hyEuMDWoo48lLGohDO9JRqVypLIIexCXy8L06fpn2IAB+vQkrMKUWjnL4QpDwfRkdlJN VlSA== X-Gm-Message-State: AOAM530Nb0CTYkIBw93kw2itd/AMbJjy57N54Roz0vcSgMMT0aD0L6E9 hns7pV4RkXR5PpqQfNFT7UP9hdUXSoWq9WnXHCPdjVUuryo= X-Google-Smtp-Source: ABdhPJwjAirz0PEXSAj8LvAE4fXDTRJdZ4ehBbXvPxkUMLq4dzTzGeVOs93JW9/XER77ofGhxPOKONFLE5F/gsdqioo= X-Received: by 2002:aca:1b13:: with SMTP id b19mr4889198oib.132.1591548966064; Sun, 07 Jun 2020 09:56:06 -0700 (PDT) MIME-Version: 1.0 References: <20200605015338.1347787-1-sandals@crustytoothpaste.net> <20200605015338.1347787-2-sandals@crustytoothpaste.net> <20200605204144.GD6569@camp.crustytoothpaste.net> In-Reply-To: <20200605204144.GD6569@camp.crustytoothpaste.net> From: Bart Schaefer Date: Sun, 7 Jun 2020 09:55:54 -0700 Message-ID: Subject: Re: [PATCH v2] exec: run final pipeline command in a subshell in sh mode To: "brian m. carlson" Cc: "zsh-workers@zsh.org" Content-Type: text/plain; charset="UTF-8" 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.