Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > gnu.bash.bug > #15835

Re: Protect Loop Execution with Traps

From Greg Wooledge <wooledg@eeg.ccf.org>
Newsgroups gnu.bash.bug
Subject Re: Protect Loop Execution with Traps
Date 2020-01-29 09:33 -0500
Message-ID <mailman.28.1580308440.2384.bug-bash@gnu.org> (permalink)
References (2 earlier) <20200128134935.GM1350@eeg.ccf.org> <20200128204932.GB12574@localhost4.local> <20200128210721.GU1350@eeg.ccf.org> <59.1580277932@jinx.noi.kre.to> <20200129143352.GY1350@eeg.ccf.org>

Show all headers | View raw


On Wed, Jan 29, 2020 at 01:05:32PM +0700, Robert Elz wrote:
> and (with all respect to Gred) please avoid archaic uses, and use the
> commands as they're currently specified, while "trap - INT" and "trap INT"
> do the same thing, the former is the standard way, similarly for
> "kill -INT ..." and "kill -s INT ..." the latter is the modern version.

I had <https://www.cons.org/cracauer/sigint.html> open at the time,
and got the syntax from there.  He actually uses the numeric signal
specifiers ("trap 2"), which I replaced with the modern standard naming
strings; but I didn't replace the legacy single-argument form with
the "-" form.  Bash, of course, accepts both.

You're not going to talk me into using "kill -s" any time soon, though.
I don't think I've *ever* seen anyone use that.

>   | I'm thinking, put "trap INT; kill -INT $$" inside of it's own function,

Yeah, that's pretty common.

sigint_handler() {
    trap - INT
    kill -INT $$
}
trap sigint_handler INT

Back to gnu.bash.bug | Previous | Next | Find similar | Unroll thread


Thread

Re: Protect Loop Execution with Traps Greg Wooledge <wooledg@eeg.ccf.org> - 2020-01-29 09:33 -0500

csiph-web