From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Did something change about completion and xtrace ?
Date: Fri, 5 Feb 2021 21:03:18 -0800 [thread overview]
Message-ID: <CAH+w=7ZoumpJWSGYSAcuChJqLC9x2BT=gLR7SqK10m2DRtCjsA@mail.gmail.com> (raw)
I would have sworn that completion used to suppress xtrace output
somehow, but recently if I happen to hit tab after "set -x" I get
everything from _main_complete on down dumped to the terminal.
Am I just conjuring a false memory, or does someone recall a change
that would have affected this? It could have been quite some time
ago.
next reply other threads:[~2021-02-06 5:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-06 5:03 Bart Schaefer [this message]
2021-02-10 18:01 ` Bart Schaefer
2021-02-10 19:07 ` Bart Schaefer
2021-02-10 21:53 ` Phil Pennock
2021-02-10 23:02 ` Bart Schaefer
2021-02-11 23:49 ` Phil Pennock
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=7ZoumpJWSGYSAcuChJqLC9x2BT=gLR7SqK10m2DRtCjsA@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).