From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-31892-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 14003 invoked by alias); 25 Oct 2013 00:39:18 -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: 31892
Received: (qmail 28655 invoked from network); 25 Oct 2013 00:39:02 -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
	autolearn=ham version=3.3.2
From: Bart Schaefer <schaefer@brasslantern.com>
Message-id: <131024173848.ZM8087@torch.brasslantern.com>
Date: Thu, 24 Oct 2013 17:38:48 -0700
In-reply-to: <20131024174610.0da2aaaf@pwslap01u.europe.root.pri>
Comments: In reply to Peter Stephenson <p.stephenson@samsung.com>
 "Re: Strange function/pipestatus behavior, maybe a scope bug?" (Oct 24,
 5:46pm)
References:
 <CAMeu-1WYhBr-hbcgXQy3gEGOSSpS2FFmxDa+QDFyN1m+7Z1kQA@mail.gmail.com>
	<20131023092155.5ba8a54b@pwslap01u.europe.root.pri>
	<CAMeu-1WsKO71YfJ+aO9uy=_oGLJEsKh-yL8HJ_rMicqmCj2FQw@mail.gmail.com>
	<20131023221412.5cdecd76@pws-pc.ntlworld.com>
	<131023221548.ZM2352@torch.brasslantern.com>
	<20131024095713.44d2982e@pwslap01u.europe.root.pri>
	<131024092633.ZM27623@torch.brasslantern.com>
	<20131024174610.0da2aaaf@pwslap01u.europe.root.pri>
X-Mailer: OpenZMail Classic (0.9.2 24April2005)
To: zsh-workers@zsh.org
Subject: Re: Strange function/pipestatus behavior, maybe a scope bug?
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii

On Oct 24,  5:46pm, Peter Stephenson wrote:
}
} Amusingly (or otherwise), running this from the command line was for a
} time consistently giving me the "no job control in this shell message",
} then it stopped, so this definitely looks like a race.

Yes, I fully expect Eitan Adler to pop up in a few weeks having managed
to crash the shell again, which will tell us what function needs to
be made signal safe now ...