Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: TRAPDEBUG exit bug?
- X-seq: zsh-workers 35946
 
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
 
- To: zsh-workers@xxxxxxx
 
- Subject: Re: TRAPDEBUG exit bug?
 
- Date: Tue, 28 Jul 2015 12:40:13 -0700
 
- In-reply-to: <20150728184809.GA50119@Qliphoth.local>
 
- List-help: <mailto:zsh-workers-help@zsh.org>
 
- List-id: Zsh Workers List <zsh-workers.zsh.org>
 
- List-post: <mailto:zsh-workers@zsh.org>
 
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
 
- References: <20150728184809.GA50119@Qliphoth.local>
 
On Jul 28,  8:48pm, Joshua Krusell wrote:
}
} Setting TRAPDEBUG seems to make zsh unexpectedly emit SIGEXIT after a
} command following a failed && or || conditional expr.
Hm, it's even weirder than that:
torch% trap "" DEBUG
torch% trap "print exit trap" EXIT
torch% trap
trap -- 'print exit trap' EXIT
trap -- '' DEBUG
torch% false && :
torch% :
exit trap
torch% trap
trap -- '' DEBUG
torch% 
Note that the exit trap itself has now disappeared.  This happens with
a TRAPEXIT function as well.
-- 
Barton E. Schaefer
Messages sorted by:
Reverse Date,
Date,
Thread,
Author