From: Bart Schaefer <schaefer@brasslantern.com>
To: zsh-workers@zsh.org (Zsh hackers list)
Subject: Re: PATCH: POSIX_TRAPS option
Date: Sat, 11 Sep 2010 20:49:15 -0700 [thread overview]
Message-ID: <100911204915.ZM24282@torch.brasslantern.com> (raw)
In-Reply-To: <7900.1284147069@pws-pc>
On Sep 10, 8:31pm, Peter Stephenson wrote:
}
} It's high time we were able to treat EXIT traps the same way as other
} shells.
Hrm. A couple of thoughts ...
(1) POSIX doesn't have anything to do with TRAPEXIT (or with any of
the other special TRAP functions). Perhaps the POSIX_TRAPS option
should apply only to the "trap" builtin? I don't feel very strongly
about it either way, but for example TRAPEXIT persists into subshells
whereas "trap" does not.
(2) The documentation should explain (somewhere) in what order the
EXIT trap and the zshexit hook function are executed. Emprically,
zshexit is always last.
prev parent reply other threads:[~2010-09-12 3:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-10 19:31 Peter Stephenson
2010-09-12 3:49 ` Bart Schaefer [this message]
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=100911204915.ZM24282@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).