Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: Strange function/pipestatus behavior, maybe a scope bug?

X-seq: zsh-workers 31871
From: Peter Stephenson <p.stephenson@xxxxxxxxxxx>
To: Ian F <in4mer@xxxxxxxxx>, zsh-workers@xxxxxxx
Subject: Re: Strange function/pipestatus behavior, maybe a scope bug?
Date: Wed, 23 Oct 2013 09:21:55 +0100
In-reply-to: <CAMeu-1WYhBr-hbcgXQy3gEGOSSpS2FFmxDa+QDFyN1m+7Z1kQA@mail.gmail.com>
List-help: <mailto:zsh-workers-help@zsh.org>
List-id: Zsh Workers List <zsh-workers.zsh.org>
List-post: <mailto:zsh-workers@zsh.org>
Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
Organization: Samsung Cambridge Solution Centre
References: <CAMeu-1WYhBr-hbcgXQy3gEGOSSpS2FFmxDa+QDFyN1m+7Z1kQA@mail.gmail.com>

On Tue, 22 Oct 2013 11:03:07 -0700
Ian F <in4mer@xxxxxxxxx> wrote:
> Potential bug case:
> 
> awkFunc() { awk; }
> 
> % false | true | false | true | awkFunc; echo $pipestatus
> 0

Yes, that's a bug owing to the way the shell executes internal shell
commands within the right hand side of a pipeline.  There was a thread
on this starting at zsh-workers/29973:

http://www.zsh.org/mla/workers/2011/msg01394.html

pws

Follow-Ups:
- Re: Strange function/pipestatus behavior, maybe a scope bug?
  - From: Ian F

References:
- Strange function/pipestatus behavior, maybe a scope bug?
  - From: Ian F

Messages sorted by: Reverse Date, Date, Thread, Author