Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: trap question

X-seq: zsh-users 28429
From: Ray Andrews <rayandrews@xxxxxxxxxxx>
To: zsh-users@xxxxxxx
Subject: Re: trap question
Date: Fri, 25 Nov 2022 15:25:38 -0800
Archived-at: <https://zsh.org/users/28429>
In-reply-to: <CAN=4vMoT--+fknaDpjQJ8i4SadTVV=30GTvA6DL-fEwMvB-cuw@mail.gmail.com>
List-id: <zsh-users.zsh.org>
References: <e3382835-c9a6-a304-b8df-31700759844f@eastlink.ca> <CAN=4vMoT--+fknaDpjQJ8i4SadTVV=30GTvA6DL-fEwMvB-cuw@mail.gmail.com>


On 2022-11-25 10:57, Roman Perepelitsa wrote:

Try replacing this:
     trap " [[ $var == '0' ]] && echo trap: var is: $var" EXIT

with this:

     trap ' [[ $var == 0 ]] && echo trap: var is: $var' EXIT

Bullseye. And I understand it I think. Double quotes evaluated whenparsed, single quotes kept as literal until trap is sprung, yes? Itwouldn't have occurred to me since I'd have expected the '$var' toremain un-expandable within single quotes. Is this an exception orsomehow to be viewed as routine? BTW, will this trap catch exitingerrors or just proper returns? I know it doesn't catch ^C.

Follow-Ups:
- Re: trap question
  - From: Bart Schaefer

References:
- trap question
  - From: Ray Andrews
- Re: trap question
  - From: Roman Perepelitsa

Messages sorted by: Reverse Date, Date, Thread, Author