From: Zach Riggle <zachriggle@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: Prevent a specific function from being xtrace'd
Date: Mon, 23 Aug 2021 18:23:02 -0500 [thread overview]
Message-ID: <CAMP9c5=hTpffYG_EydhhtD-ig7yzZYXxKDOFrRLXAs+PmOr52Q@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7bOCbkjRhGj8HjeJ6t-uyg7Uye26M5NnLqai+ThyXR_5A@mail.gmail.com>
>>> local first_line=$(head -1 <<<$ZSH_DEBUG_CMD)
> Egad.
> local first_line=${ZSH_DEBUG_CMD%%$'\n'*}
That's (almost!) the following line! I couldn't quite get it to work,
looks like I was missing a $ and the *.
Thanks!
Zach Riggle
Zach Riggle
On Mon, Aug 23, 2021 at 3:04 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Mon, Aug 23, 2021 at 9:42 AM Zach Riggle <zachriggle@gmail.com> wrote:
> >
> > Hello all!
> >
> > ~~ TL; DR ~~
> > Is there any way to mark or annotate a function such that its internals should not be traced, even if "set -x" or "zsh -x" is used?
>
> emulate zsh +x -c 'autoload untraced'
>
> (The name "untraced" is for example, not some sort of extra magic.)
> It also works for
>
> emulate zsh +x -c 'untraced() { ... }'
>
> but that requires that you're careful about quoting in the function body.
>
> Of course you can still force tracing back on with
> functions -t untraced
> or the function internally calling "set -x" etc.
>
> > I've created a small script[1] that somewhat achieves this effect, with TRAPDEBUG and ZSH_DEBUG_COMMAND
>
> >> local first_line=$(head -1 <<<$ZSH_DEBUG_CMD)
>
> Egad.
>
> local first_line=${ZSH_DEBUG_CMD%%$'\n'*}
next prev parent reply other threads:[~2021-08-23 23:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-23 16:42 Zach Riggle
2021-08-23 19:42 ` Eric Cook
2021-08-23 20:04 ` Bart Schaefer
2021-08-23 23:23 ` Zach Riggle [this message]
2021-08-24 2:27 ` Bart Schaefer
2021-08-24 13:09 ` Daniel Shahaf
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='CAMP9c5=hTpffYG_EydhhtD-ig7yzZYXxKDOFrRLXAs+PmOr52Q@mail.gmail.com' \
--to=zachriggle@gmail.com \
--cc=schaefer@brasslantern.com \
--cc=zsh-users@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).