From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org
Subject: Re: [BUG] Sticky-sh POSIX_TRAPS are function-local
Date: Fri, 19 Feb 2016 10:59:24 -0800 [thread overview]
Message-ID: <160219105924.ZM17561@torch.brasslantern.com> (raw)
In-Reply-To: <56C4041F.5060602@inlv.org>
On Feb 17, 6:24am, Martijn Dekker wrote:
}
} But POSIX is irrelevant to function-local traps because they are not
} defined in POSIX, so, once emulation mode is exited, there is nothing
} that compels you to make them wipe out a global POSIX trap.
That's sort of the point -- there's nothing that compels us, hence ...
} > I could see an argument either way
... and your argument is a pretty good one.
} > I could also see an argument
} > that the localtraps option should affect this
}
} How do you think that option should affect this?
To be pedantic, I didn't say I think that; I said I could understand how
one might argue that position. To try to frame it -- the implication is
that a trap created under LOCAL_TRAPS should *never* alter traps in any
outer scope. This ought to include the global scope, regardless of the
context in which the global trap was created.
I.e. given "setopt POSIX_TRAPS LOCAL_TRAPS" this argues that LOCAL_TRAPS
should "win". With PWS's patch, POSIX_TRAPS prevails.
next prev parent reply other threads:[~2016-02-19 18:59 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-15 5:11 Martijn Dekker
2016-02-16 9:57 ` Peter Stephenson
2016-02-16 12:46 ` Peter Stephenson
2016-02-16 23:38 ` Martijn Dekker
2016-02-17 4:25 ` Bart Schaefer
2016-02-17 5:24 ` Martijn Dekker
2016-02-19 18:59 ` Bart Schaefer [this message]
2016-02-17 10:36 ` Peter Stephenson
2016-02-25 11:53 ` Peter Stephenson
2016-02-25 13:52 ` Martijn Dekker
2016-02-25 14:17 ` Peter Stephenson
2016-03-04 18:02 ` Peter Stephenson
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=160219105924.ZM17561@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@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).