zsh-users
 help / color / mirror / code / Atom feed
From: Philippe Troin <phil@fifi.org>
To: Thorsten Kampe <thorsten@thorstenkampe.de>
Cc: zsh-users@zsh.org
Subject: Re: How to trap EXIT like in bash
Date: Sat, 04 Apr 2015 11:20:26 -0700	[thread overview]
Message-ID: <1428171626.27718.8.camel@ceramic.home.fifi.org> (raw)
In-Reply-To: <mfp7s2$c1r$1@ger.gmane.org>

On Sat, 2015-04-04 at 19:43 +0200, Thorsten Kampe wrote:
> * 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
> ```

Yes, you're right.  For some reason it did work for me but I can't
reproduce it.  This would work everywhere:

  trap "echo trapped; trap - EXIT; exit 0" EXIT INT

With bash:

        % bash --version
        GNU bash, version 4.2.53(1)-release (x86_64-redhat-linux-gnu)
        Copyright (C) 2011 Free Software Foundation, Inc.
        License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
        
        This is free software; you are free to change and redistribute it.
        There is NO WARRANTY, to the extent permitted by law.
        % for i in INT TERM HUP QUIT; do bash -c 'trap "echo trapped \$?; trap - EXIT; exit 0" EXIT INT TERM HUP QUIT; sleep 5' & sleep 1; kill -$i -$!; wait; done
        [2] 28903
        trapped 130
        [2]  + done       bash -c 
        [1] 28906
        Terminated
        trapped 143
        [1]  + done       bash -c 
        [1] 28909
        Hangup
        trapped 129
        [1]  + done       bash -c 
        [1] 28912
        Quit
        trapped 131
        [1]  + done       bash -c 
        % 
        
With zsh:

        % zsh --version
        zsh 5.0.7 (x86_64-redhat-linux-gnu)
        % for i in INT TERM HUP QUIT; do zsh -fc 'trap "echo trapped \$?; trap - EXIT; exit 0" EXIT INT TERM HUP QUIT; sleep 5' & sleep 1; kill -$i -$!; wait; done
        [2] 28936
        trapped 130
        [2]  + done       zsh -fc 
        [1] 28940
        trapped 143
        [1]  + done       zsh -fc 
        [1] 28943
        trapped 129
        [1]  + done       zsh -fc 
        [1] 28947
        trapped 131
        [1]  + done       zsh -fc 
        % 

> 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.

That's not the behavior I'm seeing above.

Phil.


  reply	other threads:[~2015-04-04 18:20 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 [this message]
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=1428171626.27718.8.camel@ceramic.home.fifi.org \
    --to=phil@fifi.org \
    --cc=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).