From: Martijn Dekker <martijn@inlv.org>
To: zsh-workers@zsh.org
Cc: Bart Schaefer <schaefer@brasslantern.com>
Subject: Re: [BUG] Sticky-sh POSIX_TRAPS are function-local
Date: Wed, 17 Feb 2016 06:24:47 +0100 [thread overview]
Message-ID: <56C4041F.5060602@inlv.org> (raw)
In-Reply-To: <160216202547.ZM3900@torch.brasslantern.com>
Bart Schaefer schreef op 17-02-16 om 05:25:
> On Feb 17, 12:38am, Martijn Dekker wrote:
> }
> } With your current patch, the function-local trap wipes out the global
> } POSIX exit trap, so the last line of expected output doesn't appear.
>
> Hrm. I think the point is that there are no function-local traps in
> POSIX, so the POSIX trap obeys the POSIX rules even when another trap
> is set in non-POSIX scope.
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.
I think it would actually be more consistent with the intention of the
POSIX trap if it survived a function-local native zsh trap; the
intention of the POSIX trap was for it to be executed on program exit,
so having it wiped out by a temporary function-local trap doesn't seem
helpful.
> I could see an argument either way, though. I could also see an argument
> that the localtraps option should affect this (even though it's not usually
> needed for global traps).
How do you think that option should affect this?
Thanks,
- M.
next prev parent reply other threads:[~2016-02-17 5:24 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 [this message]
2016-02-19 18:59 ` Bart Schaefer
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=56C4041F.5060602@inlv.org \
--to=martijn@inlv.org \
--cc=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).