From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 1199 invoked by alias); 18 Sep 2016 02:06:44 -0000 Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Users List List-Post: List-Help: X-Seq: 21940 Received: (qmail 13707 invoked from network); 18 Sep 2016 02:06:44 -0000 X-Qmail-Scanner-Diagnostics: from mout.gmx.net by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(212.227.17.22):SA:0(0.0/5.0):. Processed in 0.464224 secs); 18 Sep 2016 02:06:44 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=FREEMAIL_FROM,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: llua@gmx.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: pass (ns1.primenet.com.au: SPF record at gmx.com designates 212.227.17.22 as permitted sender) Subject: Re: Strange parameter visibility To: zsh-users@zsh.org References: <87bmzmtmzq.fsf@alfa.kjonca> From: Eric Cook Message-ID: <831b307a-a00f-1df7-5136-17fcb769ccaf@gmx.com> Date: Sat, 17 Sep 2016 21:42:08 -0400 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.2.0 MIME-Version: 1.0 In-Reply-To: <87bmzmtmzq.fsf@alfa.kjonca> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:0Zgd74tUOxYfeJa4jkLpowDsrqOO09g5XlnkglSv116WhbwwOPa Pop/FUfP2aMfSn2pYneN6tHn9tOa3i2zP4abdwjMDpGus1wBRb/U1LRT1lzaX7LxHgRoIz9 amNgtXkLg784BZsr7qr4RhXV9E9uJg8kO2TdX6nHN74K6xeDdi3f2OX7gJhJWZJmB1QVCYw a3F/FbozOU1u1FJGJYipg== X-UI-Out-Filterresults: notjunk:1;V01:K0:56UCHNGQOhg=:5ZCsx34uFWWwO5S2xsNcdR 99gBpj/XuCRwOeYN5QRhP0lSUNqcDib0tsiKv3HzGkMZHkyK0KO/IkgP87bVbPQEw40yG1Na8 Lvkrx0FXQ2hILOPuwsZlvY90gn8sNgF8m2VMF1QNVm5tqfSv26JDj5JV4UDBzqwAJeF/VjOLT UYFElTyl6ry9FB4M7c5bNErX7/qx6AwAd6nvSm4uPwOYDLOBxztedNpJKkmxvuabgjxzhdOP1 jZeDxh7xWPFtjZ7/4tUYjFPyxeEXhUDYINuiJGTBsSsPiOaFxf5BBcJxASC5dEcfuQ8uGKeXp vtQThn4Avxyvtsua00mFfkJJm9hYq1P667vPhWQMUM5fop/V++LV1H8P7/jlN8WZLjcQbRF6e 9sH27ITw5MWQ6neXusAuHOymgeWXFrw7COcwCaCT8MqhSTog92vTCJ1JUqWGtH9iv5CNUdFiQ 7IN+npAAkKc/dNjeOruy0vcOCT6Q+SGna1hbiAKvCxAjzw7QTUyKUVpUnVsvIFD4RIbaXQwOl WBM1C8mYFPdiXafUHpdaoLsj4K9B/FgavIU0yjtmE/hxQy2H9S1dEiu1Rq6ZiPJg2To/enryI v8HGV962mXxrT0HaOs0DWIzo/ji8iMs0nqERc+XEkEIL0QHNmQzfyumcpgdjBpcNN43OQjmJj RG+3wqy2zKIt9acZA/knEJfvrnFSG3gpLe8i2JN3LbjjCbSIepUcQJEmuMWenhD0Pt/jJSgUZ 3wTDGiGYVgpTOiCjIe4GA4QRMDIwguxO/58u0nOstDaxZrDIRD97mjP90+yq0fo2GeM2+z/3u smQb5B0 On 09/17/2016 02:11 PM, Kamil Jońca wrote: > > --8<---------------cut here---------------start------------->8--- > %(x=1; x=2 echo | echo $x ; echo $x) > 1 > 1 > --8<---------------cut here---------------end--------------->8--- > > but : > --8<---------------cut here---------------start------------->8--- > %(x=1; x=2 | echo $x ; echo $x) > 2 > 2 > --8<---------------cut here---------------end--------------->8--- > > What there are "2"-s in second example? > should'n "x=2" be treated as simple null command with its own > assignement? > KJ > It's a normal assignment just like the x=1. the weirdness is zsh optimizing out a fork in the pipeline, so the scope of the reassignment wasn't just a subshell. Though, in the first example you put the variable into echo's environment, the shell parameter x wasn't changed at all.