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

Groups > gnu.bash.bug > #15835 > unrolled thread

Re: Protect Loop Execution with Traps

Back to article view | Back to gnu.bash.bug

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

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

#15835 — Re: Protect Loop Execution with Traps

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

[toc] | [standalone]

Back to top | Article view | gnu.bash.bug

csiph-web