From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-31897-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 4418 invoked by alias); 25 Oct 2013 15:22:06 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 31897
Received: (qmail 1570 invoked from network); 25 Oct 2013 15:21:51 -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=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	SPF_HELO_PASS autolearn=ham version=3.3.2
X-AuditID: cbfec7f5-b7ef66d00000795a-8a-526a8c8bed7c
Date: Fri, 25 Oct 2013 16:21:46 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: Shell job structure
Message-id: <20131025162146.459b92c2@pwslap01u.europe.root.pri>
In-reply-to: <131025081311.ZM9080@torch.brasslantern.com>
References:
 <CADv1Z=pM7H4Xg9+GyWd4zw0cv0mXfbJvqip6vc7e_yrXRN=1sg@mail.gmail.com>
 <20131005223159.25fea6a0@pws-pc.ntlworld.com>
 <131006173621.ZM31831@torch.brasslantern.com>
 <20131007102529.5354f342@pwslap01u.europe.root.pri>
 <131007074049.ZM32707@torch.brasslantern.com>
 <20131008214437.41dc396a@pws-pc.ntlworld.com>
 <131024220214.ZM8256@torch.brasslantern.com>
 <20131025110056.1757a5ab@pwslap01u.europe.root.pri>
 <131025081311.ZM9080@torch.brasslantern.com>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFuplluLIzCtJLcpLzFFi42I5/e/4Zd3unqwggyXrxC0ONj9kcmD0WHXw
	A1MAYxSXTUpqTmZZapG+XQJXxt+ri5kKlrFUHJi7hq2BcS5zFyMnh4SAicSKZeeZIGwxiQv3
	1rOB2EICSxklzjbbdzFyAdnLmSRmtHeBFbEIqErMObEcrIhNwFBi6qbZjCC2iIC4xNm151lA
	bGEBBYlbO66A2bwC9hJf3/1jBbE5BSwl3q97xgox9A6zRP/idWBX8AvoS1z9+wnqCnuJmVfO
	MEI0C0r8mHwPbBCzgJbE5m1NrBC2vMTmNW+ZJzAKzEJSNgtJ2SwkZQsYmVcxiqaWJhcUJ6Xn
	GukVJ+YWl+al6yXn525ihATh1x2MS49ZHWIU4GBU4uEtaM8KEmJNLCuuzD3EKMHBrCTCW18D
	FOJNSaysSi3Kjy8qzUktPsTIxMEp1cAYxjLVMCWZq+vszYOXQyYHLlZP9g2LF7m0+Hv54hqd
	TaufBWre+vphvZ3VgVO3b3KkbdnJH/jEJOjA00mHnRnPmBcyhbwStHwTd97gi4j+tHVioRF/
	7W7duKIQ+XPl6q3GLjN+f7Vcp35K09Xn/cefCaUH3Dhrio+xFwTsEL158/6Wf0oMZy+fUGIp
	zkg01GIuKk4EAInm1oogAgAA

On Fri, 25 Oct 2013 08:13:11 -0700
Bart Schaefer <schaefer@brasslantern.com> wrote:
> You mean like this?
> 
> % true | false | true | (){ false | true | false; print $pipestatus }; print $pipestatus
> 1 0 1
> 0 1 0 0
> 
> Here's a loop construct:
> 
> % false | true | false | while true | false | true; do print $pipestatus; break; done; print $pipestatus
> 0 1 0
> 1 0 1 0

That's the sort of thing I'm worrying about.  As long as it can identify
succesfully which job it needs to worry about at any time, it should be
OK.

pws