From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 13451 invoked from network); 3 Oct 2001 16:17:10 -0000 Received: from sunsite.dk (130.225.51.30) by ns1.primenet.com.au with SMTP; 3 Oct 2001 16:17:10 -0000 Received: (qmail 22539 invoked by alias); 3 Oct 2001 16:17:01 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 15932 Received: (qmail 22510 invoked from network); 3 Oct 2001 16:16:58 -0000 From: Bart Schaefer Message-Id: <1011003161636.ZM29448@candle.brasslantern.com> Date: Wed, 3 Oct 2001 16:16:35 +0000 In-Reply-To: <19164.1002122295@csr.com> Comments: In reply to Peter Stephenson "PATCH: (2) test for trap EXIT fix." (Oct 3, 4:18pm) References: <19164.1002122295@csr.com> X-Mailer: Z-Mail (5.0.0 30July97) To: Peter Stephenson , zsh-workers@sunsite.dk (Zsh hackers list) Subject: Re: PATCH: (2) test for trap EXIT fix. MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Oct 3, 4:18pm, Peter Stephenson wrote: } } Are you saying this is correct and the inconsistency between falling off } the end and exiting is the intended behaviour? Not exactly; I'm just providing a historical reference point so we're sure we've made the right decision. } The following might do we what you want. Maybe you'd better try it and } then complain further. OK, I'm good at that. 15931 has almost got it, but: bash2-2.03$ (trap 'echo exiting' 0; true) exiting bash2-2.03$ zagzig% (trap 'echo exiting' 0; true) zagzig% It matters where the trap was set, as well. -- Bart Schaefer Brass Lantern Enterprises http://www.well.com/user/barts http://www.brasslantern.com Zsh: http://www.zsh.org | PHPerl Project: http://phperl.sourceforge.net