From: Thorsten Kampe <thorsten@thorstenkampe.de>
To: zsh-users@zsh.org
Subject: Re: How to trap EXIT like in bash
Date: Sat, 4 Apr 2015 19:43:22 +0200 [thread overview]
Message-ID: <mfp7s2$c1r$1@ger.gmane.org> (raw)
In-Reply-To: <1428167314.5875.2.camel@niobium.home.fifi.org>
* Philippe Troin (Sat, 04 Apr 2015 10:08:34 -0700)
>
> On Sat, 2015-04-04 at 17:20 +0200, Thorsten Kampe wrote:
> > in Bash `trap "echo trapped" EXIT` will trigger when the script
> > terminates normally and on SIGINT, SIGTERM, and SIGHUP.
> >
> > In Zsh, `trap "echo trapped" EXIT` triggers only on normal exit, but
> > `trap "echo trapped" EXIT INT` will actually trigger twice on Ctrl-C.
> >
> > How can I trap normal exit, Ctrl-C, SIGTERM and SIGHUP so trap
> > function will only run once?
>
> I use this:
>
> trap "echo trapped; exit 0" EXIT INT
I just tested it: Zsh is trapped once but bash twice on INT.
This works:
```
if [[ $shell = bash ]]
then
trap "echo trapped" EXIT
elif [[ $shell = zsh ]]
then
trap "echo trapped; exit" INT
fi
```
BUT: it does not work when I extend the signals to
```
elif [[ $shell = zsh ]]
then
trap "echo trapped; exit" INT HUP TERM
fi
```
Then Zsh does actually ignore the kill (TERM) signal.
Thorsten
next prev parent reply other threads:[~2015-04-04 17:43 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 [this message]
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
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='mfp7s2$c1r$1@ger.gmane.org' \
--to=thorsten@thorstenkampe.de \
--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).