From: "Rocky Bernstein" <rocky.bernstein@gmail.com>
To: zsh-workers@sunsite.dk
Subject: trap DEBUG should get run beforehand, not afterwards.
Date: Tue, 29 Jul 2008 22:37:32 -0400 [thread overview]
Message-ID: <6cd6de210807291937p5e864c38o6dd9785acf62632c@mail.gmail.com> (raw)
Think for example about whether you'd like to know that 'rm -fr *' is
about to occur or just occurred.
ksh introduced trap DEBUG and bash, and zsh copied it. Both ksh and
bash originally ran after the statement; I guess because that is same
as other traps. However both have switched so that it is run before
the statement.
Alas, it's impossible to contemplate writing any sort of serious
debugger unless "trap DEBUG" gets run beforehand.
Should I attempt a patch?
next reply other threads:[~2008-07-30 2:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-30 2:37 Rocky Bernstein [this message]
2008-07-30 8:23 ` Peter Stephenson
2008-07-30 13:24 ` Rocky Bernstein
2008-07-30 13:38 ` Bart Schaefer
2008-07-30 14:01 ` Rocky Bernstein
2008-07-30 13:27 ` Richard Hartmann
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=6cd6de210807291937p5e864c38o6dd9785acf62632c@mail.gmail.com \
--to=rocky.bernstein@gmail.com \
--cc=zsh-workers@sunsite.dk \
/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).