From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 7879 invoked by alias); 10 Dec 2011 13:03:27 -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: X-Seq: 29974 Received: (qmail 3094 invoked from network); 10 Dec 2011 13:03:15 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, SPF_HELO_PASS autolearn=ham version=3.3.2 Received-SPF: none (ns1.primenet.com.au: domain at bewatermyfriend.org does not designate permitted sender hosts) From: Frank Terbeck To: zsh-workers@zsh.org Subject: Re: $pipestatus broken? In-Reply-To: <87borgzkap.fsf@ft.bewatermyfriend.org> (Frank Terbeck's message of "Sat, 10 Dec 2011 13:24:30 +0100") References: <87borgzkap.fsf@ft.bewatermyfriend.org> User-Agent: Gnus/5.110018 (No Gnus v0.18) Emacs/24.0.91 (gnu/linux) Date: Sat, 10 Dec 2011 13:48:46 +0100 Message-ID: <877h24zj69.fsf@ft.bewatermyfriend.org> MIME-Version: 1.0 Content-Type: text/plain X-Df-Sender: NDMwNDQ0 Frank Terbeck wrote: [...] > Here's my test script: You can actually dumb this down to: [snip] : | while read a; do : done print "${pipestatus[@]}" [snap] It (pipestatus just containing a single "1") seems to happen less frequently with this simpler loop, but still in the range of 5% of the invocations on my machine. If I use the simplest pipe I can think of: [snip] : | : print "${pipestatus[@]}" [snap] I didn't get a misstep in 10000 test runs. I'm running the latest zsh snapshot on a 2.6.32 linux box on a intel core2duo laptop (that's an amd64 architecture), if it matters. Regards, Frank