From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-users@zsh.org
Subject: Re: How to trap EXIT like in bash
Date: Sat, 4 Apr 2015 11:35:57 -0700 [thread overview]
Message-ID: <150404113557.ZM14788@torch.brasslantern.com> (raw)
In-Reply-To: <mfovfc$g3$1@ger.gmane.org>
On Apr 4, 5:20pm, Thorsten Kampe wrote:
}
} In Zsh, `trap "echo trapped" EXIT` triggers only on normal exit, but
} `trap "echo trapped" EXIT INT` will actually trigger twice on Ctrl-C.
Hmm. This seems to be a side-effect of the rule that the EXIT trap does
not run from inside other traps. The default response to INT in a script
is to behave as if 'trap "exit 130" INT' so the EXIT trap is not run. In
your second (executes twice) example, the script doesn't exit until after
the INT trap has completed.
} How can I trap normal exit, Ctrl-C, SIGTERM and SIGHUP so trap
} function will only run once?
Just add an explicit "exit" to the trap itself:
trap "echo trapped; exit" EXIT HUP INT TERM
This also works:
zshexit() { echo trapped }
trap exit HUP INT TERM
Curiously in an interactive shell, the following prints "trapped" exactly
one time, even though my first answer above also works interactively:
trap "echo trapped" EXIT
trap exit HUP INT TERM
However, that does not work in a script. I'm not sure why interactive
matters here.
next prev parent reply other threads:[~2015-04-04 18:36 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-04 15:20 Thorsten Kampe
2015-04-04 17:08 ` Philippe Troin
2015-04-04 17:43 ` Thorsten Kampe
2015-04-04 18:20 ` Philippe Troin
2015-04-04 18:48 ` Bart Schaefer
2015-04-04 19:59 ` Thorsten Kampe
2015-04-04 20:25 ` Bart Schaefer
2015-04-04 20:55 ` Bart Schaefer
2015-04-04 21:25 ` Bart Schaefer
2015-04-10 16:28 ` Peter Stephenson
2015-04-10 21:16 ` Bart Schaefer
2015-04-04 21:06 ` Thorsten Kampe
2015-04-04 20:45 ` Thorsten Kampe
2015-04-04 20:52 ` Bart Schaefer
2015-04-04 18:35 ` Bart Schaefer [this message]
2015-04-04 19:41 ` Thorsten Kampe
2015-04-07 7:44 ` Han Pingtian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=150404113557.ZM14788@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-users@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).