From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Redefining TRAPDEBUG causes loop?
Date: Sat, 4 Sep 2021 20:07:11 -0700 [thread overview]
Message-ID: <CAH+w=7ZNqMGpa4UOw5XRXMn8L+6SHJqoMzS=cr88qcq1B4aTkA@mail.gmail.com> (raw)
I haven't worked out a simple test case yet, but several times while
playing with Zach Riggle's question about ZSH_DEBUG_CMD, I managed to
put the shell into an infinite loop by redefining TRAPDEBUG() { ... }
at the command line without first doing unfunction TRAPDEBUG.
This probably requires making a reference to $ZSH_DEBUG_CMD in the
function body (and therefore requires DEBUG_BEFORE_CMD) but I'm not
certain.
reply other threads:[~2021-09-05 3:08 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAH+w=7ZNqMGpa4UOw5XRXMn8L+6SHJqoMzS=cr88qcq1B4aTkA@mail.gmail.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).