From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-31878-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 17542 invoked by alias); 23 Oct 2013 21:14:22 -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: 31878
Received: (qmail 1999 invoked from network); 23 Oct 2013 21:14:16 -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=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
	autolearn=ham version=3.3.2
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:date:from:to:subject:message-id:in-reply-to
         :references:mime-version:content-type:content-transfer-encoding;
        bh=pgYTSYsCI8Ur8NlVEzD4UNrhhkpAxou4sr9Z3sZExnc=;
        b=maPay8KXO/qsYhIDt0ytjX8RwGKoAgmbBHwT5UxyJOXpcpM5+k68sPSxbiQAx6EtGD
         j9Xfo/iytLbcut2wVn8GvhGfdTk77B4BzlHIIqzcDMHSvzTbbW6PwaZyLA3ZsorpXhLW
         cCpPDQ8VcEabzXFI9XE1vK/OJE7MBT2seQ2cdQpyh/9EMEmI61wtasehsIyjaM2FNim3
         0U0G5fKnmn+sOaT4MxHQDYc3uQV2b2J1DbTB/FEn0xfzP3hlp8dRWhdhd/qD0noPwltO
         0LQf+5sZn6kFYrGD2IuRu7VuIQRP9WgJytSVNDroTTGb80H3t3GmYUQqaY11a/eHT4AD
         CmLg==
X-Gm-Message-State: ALoCoQncpcxXRHc3qDrk8GKFwtgtoMNi96AtAghxqI0pU67gsAukADZSknWszGtFaS5iRVb4iQRJ
X-Received: by 10.14.29.67 with SMTP id h43mr3976613eea.7.1382562854151;
        Wed, 23 Oct 2013 14:14:14 -0700 (PDT)
X-ProxyUser-IP: 86.6.157.246
Date: Wed, 23 Oct 2013 22:14:12 +0100
From: Peter Stephenson <p.w.stephenson@ntlworld.com>
To: zsh-workers@zsh.org
Subject: Re: Strange function/pipestatus behavior, maybe a scope bug?
Message-ID: <20131023221412.5cdecd76@pws-pc.ntlworld.com>
In-Reply-To: <CAMeu-1WsKO71YfJ+aO9uy=_oGLJEsKh-yL8HJ_rMicqmCj2FQw@mail.gmail.com>
References: <CAMeu-1WYhBr-hbcgXQy3gEGOSSpS2FFmxDa+QDFyN1m+7Z1kQA@mail.gmail.com>
	<20131023092155.5ba8a54b@pwslap01u.europe.root.pri>
	<CAMeu-1WsKO71YfJ+aO9uy=_oGLJEsKh-yL8HJ_rMicqmCj2FQw@mail.gmail.com>
X-Mailer: Claws Mail 3.8.0 (GTK+ 2.24.7; x86_64-redhat-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Wed, 23 Oct 2013 12:49:51 -0700
Ian F <in4mer@gmail.com> wrote:
> I suggest this to be a significant progression in identification of this
> bug, as well as indicating a greatly heightened severity, owing to the 100%
> incorrect handling of pipeline exit values in the provided, very simple
> test case (again, substantially different than previous reports I've been
> able to find).

The problem isn't any lack of severity; the problem is the shell's job
control code isn't structured to handle this well.  Short of a hack to
fix some subset of cases, which it would be best to avoid as it's likely
to make the real problem worse, it probably means a major rewrite of job
handling: so don't hold your breath.

-- 
Peter Stephenson <p.w.stephenson@ntlworld.com>
Web page now at http://homepage.ntlworld.com/p.w.stephenson/