From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-21459-mason-zsh=primenet.com.au@sunsite.dk>
Received: (qmail 24613 invoked from network); 14 Jul 2005 09:39:21 -0000
Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88)
  by ns1.primenet.com.au with SMTP; 14 Jul 2005 09:39:21 -0000
Received: (qmail 65588 invoked from network); 14 Jul 2005 09:39:15 -0000
Received: from sunsite.dk (130.225.247.90)
  by a.mx.sunsite.dk with SMTP; 14 Jul 2005 09:39:15 -0000
Received: (qmail 16259 invoked by alias); 14 Jul 2005 09:39:12 -0000
Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm
Precedence: bulk
X-No-Archive: yes
X-Seq: 21459
Received: (qmail 16250 invoked from network); 14 Jul 2005 09:39:11 -0000
Received: from news.dotsrc.org (HELO a.mx.sunsite.dk) (130.225.247.88)
  by sunsite.dk with SMTP; 14 Jul 2005 09:39:11 -0000
Received: (qmail 65279 invoked from network); 14 Jul 2005 09:39:11 -0000
Received: from vms044pub.verizon.net (206.46.252.44)
  by a.mx.sunsite.dk with SMTP; 14 Jul 2005 09:39:05 -0000
Received: from candle.brasslantern.com ([71.116.88.149])
 by vms044.mailsrvcs.net
 (Sun Java System Messaging Server 6.2 HotFix 0.04 (built Dec 24 2004))
 with ESMTPA id <0IJM005B62SS38A0@vms044.mailsrvcs.net> for
 zsh-workers@sunsite.dk; Thu, 14 Jul 2005 04:38:54 -0500 (CDT)
Received: from candle.brasslantern.com (IDENT:schaefer@localhost [127.0.0.1])
	by candle.brasslantern.com (8.12.11/8.12.11) with ESMTP id j6E9cp4J027999;
 Thu, 14 Jul 2005 02:38:51 -0700
Received: (from schaefer@localhost)	by candle.brasslantern.com
 (8.12.11/8.12.11/Submit) id j6E9co1l027998; Thu, 14 Jul 2005 02:38:50 -0700
Date: Thu, 14 Jul 2005 09:38:49 +0000
From: Bart Schaefer <schaefer@brasslantern.com>
Subject: Re: [Brian May] zsh random behaviour
In-reply-to: <sa43bqi6ohp.fsf@snoopy.microcomaustralia.com.au>
To: Brian May <bam@snoopy.apana.org.au>
Cc: zsh-workers@sunsite.dk
Message-id: <1050714093849.ZM27997@candle.brasslantern.com>
MIME-version: 1.0
X-Mailer: Z-Mail (5.0.0 30July97)
Content-type: text/plain; charset=us-ascii
References: <sa4hdf2i0uq.fsf@snoopy.microcomaustralia.com.au>
	<1050711030705.ZM24700@candle.brasslantern.com>
	<sa43bqi6ohp.fsf@snoopy.microcomaustralia.com.au>
Comments: In reply to Brian May <bam@snoopy.apana.org.au>
 "Re: [Brian May] zsh random behaviour" (Jul 14,  1:44pm)
X-Spam-Checker-Version: SpamAssassin 3.0.2 on a.mx.sunsite.dk
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=6.0 tests=BAYES_00 autolearn=ham 
	version=3.0.2
X-Spam-Hits: -2.6

On Jul 14,  1:44pm, Brian May wrote:
} Subject: Re: [Brian May] zsh random behaviour
}
} I assume you mean the thread starting at
} <URL:http://www.zsh.org/mla/workers/2005/msg00690.html>.

Yes.

} Or is it a matter that zsh is getting confused when the first process
} returns 255, and aborts because it thinks the program was killed due
} to a signal?

Yes, again.

} Also, there was the comment "...this only effects interactive shells",
} but it my case I first encountered the problem in a shell script.

It extends from interactive shells to processes run by interactive shells.
It depends on zsh's notion of what process is "in the foreground".