From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 18425 invoked by alias); 18 Sep 2016 04:37:19 -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: 21941 Received: (qmail 6175 invoked from network); 18 Sep 2016 04:37:19 -0000 X-Qmail-Scanner-Diagnostics: from mail-qk0-f173.google.com 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(209.85.220.173):SA:0(0.0/5.0):. Processed in 0.710379 secs); 18 Sep 2016 04:37:19 -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=T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=u+BxWBn0P/SXgM32+xiNE1QZIWHLW/4BXtOoGJFCIFc=; b=Zrk+ODpUtWGmsnv9YI7LX24pd9hC5/oXIgtjcGG4A4+JVJhdFTCrT8j0HX2Wz8fzvK qZPkD78XORYpw39DJEqk3d77Hn0drYNLZm4OpY1ORR/zTtoqAjnFBI1ybhVC3ZuVxOWQ e3kGWcnO4x4yTdWzHENmYvi5zZwbOgJ7Bj54o4hQ2xlYhhnc//Hq5fou8JNQpVfVCnzm xTh2dTc8sLx2XwzT3CjIQ/xQdnsJcX0QoR00/bnadILQwVrqD7QvmesyYoW1icakMAas i5hbdNB1rG6njgF3nOI/M0l2qJu4defPDb11iQx0DhqtZOfMa5xWwcaDynAV9vjQpPTD 9hVw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=u+BxWBn0P/SXgM32+xiNE1QZIWHLW/4BXtOoGJFCIFc=; b=lF+Srx86GUXVclXbD4x5dAhlH/APjfHzUjTRKjoXwyn0vQziQYQH2E969kbFWSMMiC EK3U2XcQHnE7OTKBUaPKolBEI9+LIdP8UtKHsbvg1eF31uXvR/RIgieK5R8eIPKls0WB 1y26tYhVn/QSHu9rkf9iKYqAlXqqbuvK9wgyxcMTy2alKtGU2agGsO7PsBmBKUSTO8Lz NhDgfKuz5vueyerGuRVE/0GCzQSuyYfgKJG8ouhrF62CLpILx677ypE7fSqHYCse8x8+ KQCJUjrVC4Qax1kUtYg0Z7wlGo2qAmsTUpdga5vajQ65nPlnz0L05SCDqV4dr1DVZ3Cn 7V9A== X-Gm-Message-State: AE9vXwPLcrFOfrm1PNFeImb5bEnYfcTkqC4CkNzpyFYwT32tT1+eGN0CI9qBYSKWrSTWlCrDJA0BgLS+8toA5w== X-Received: by 10.55.210.67 with SMTP id f64mr24868171qkj.166.1474173432105; Sat, 17 Sep 2016 21:37:12 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: <831b307a-a00f-1df7-5136-17fcb769ccaf@gmx.com> References: <87bmzmtmzq.fsf@alfa.kjonca> <831b307a-a00f-1df7-5136-17fcb769ccaf@gmx.com> From: Bart Schaefer Date: Sat, 17 Sep 2016 21:37:11 -0700 Message-ID: Subject: Re: Strange parameter visibility To: Zsh Users Content-Type: text/plain; charset=UTF-8 On Sat, Sep 17, 2016 at 6:42 PM, Eric Cook wrote: > > 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. I have to conclude that's a bug -- it's OK to optimize out the fork, but not to optimize out its side effects (or cause new ones).