zsh-users
 help / color / mirror / code / Atom feed
From: Zach Riggle <zachriggle@gmail.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Prevent a specific function from being xtrace'd
Date: Mon, 23 Aug 2021 11:42:13 -0500	[thread overview]
Message-ID: <CAMP9c5==SoZuvHHB3U+HYu5+KwXMa7Jifjf_TFd31yxrhBiA1w@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]

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?

~~ Research ~~
I've got a handful of functions that get loaded into each script via
"source" or (more frequently) "autoload".

In order for the contents of these functions to not pollute the xtrace
output, I set the first line of each function to do "set +x" which prevents
further tracing.  However, the "set +x" itself shows up in the xtrace.

Chapter 9 (functions) doesn't mention anything about tracing at all.

Chapter 16 (options) mentions a few related things, notably SOURCE_TRACE,
VERBOSE, and XTRACE, but doesn't have anything like that.

Chapter 17 (builtins) discusses the "functions" builtin and some of the
options that are available to it.  None of these look relevant.

~~ Misc Notes ~~
I've created a small script[1] that somewhat achieves this effect, with
TRAPDEBUG and ZSH_DEBUG_COMMAND -- using funcfiletrace to simply not print
any of the lines that come from the file that contains the
do-not-want-traced functions -- but I expect there is something simpler.
It's similar to xtrace / verbose, but only prints the first line of each
statement executed.

[1]: https://gist.github.com/zachriggle/eedbfebee870bf66bfafcc2f78b2da78

*Zach Riggle*

[-- Attachment #2: Type: text/html, Size: 1990 bytes --]

             reply	other threads:[~2021-08-23 16:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-23 16:42 Zach Riggle [this message]
2021-08-23 19:42 ` Eric Cook
2021-08-23 20:04 ` Bart Schaefer
2021-08-23 23:23   ` Zach Riggle
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==SoZuvHHB3U+HYu5+KwXMa7Jifjf_TFd31yxrhBiA1w@mail.gmail.com' \
    --to=zachriggle@gmail.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).