zsh-users
 help / color / mirror / code / Atom feed
* Prevent a specific function from being xtrace'd
@ 2021-08-23 16:42 Zach Riggle
  2021-08-23 19:42 ` Eric Cook
  2021-08-23 20:04 ` Bart Schaefer
  0 siblings, 2 replies; 6+ messages in thread
From: Zach Riggle @ 2021-08-23 16:42 UTC (permalink / raw)
  To: Zsh Users

[-- 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 --]

^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Prevent a specific function from being xtrace'd
  2021-08-23 16:42 Prevent a specific function from being xtrace'd Zach Riggle
@ 2021-08-23 19:42 ` Eric Cook
  2021-08-23 20:04 ` Bart Schaefer
  1 sibling, 0 replies; 6+ messages in thread
From: Eric Cook @ 2021-08-23 19:42 UTC (permalink / raw)
  To: zsh-users

On 8/23/21 12:42 PM, Zach Riggle wrote:
> 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?

Not really.



^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Prevent a specific function from being xtrace'd
  2021-08-23 16:42 Prevent a specific function from being xtrace'd Zach Riggle
  2021-08-23 19:42 ` Eric Cook
@ 2021-08-23 20:04 ` Bart Schaefer
  2021-08-23 23:23   ` Zach Riggle
  2021-08-24 13:09   ` Daniel Shahaf
  1 sibling, 2 replies; 6+ messages in thread
From: Bart Schaefer @ 2021-08-23 20:04 UTC (permalink / raw)
  To: Zach Riggle; +Cc: Zsh Users

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'*}


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Prevent a specific function from being xtrace'd
  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
  1 sibling, 1 reply; 6+ messages in thread
From: Zach Riggle @ 2021-08-23 23:23 UTC (permalink / raw)
  To: Bart Schaefer; +Cc: Zsh Users

>>> 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'*}


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Prevent a specific function from being xtrace'd
  2021-08-23 23:23   ` Zach Riggle
@ 2021-08-24  2:27     ` Bart Schaefer
  0 siblings, 0 replies; 6+ messages in thread
From: Bart Schaefer @ 2021-08-24  2:27 UTC (permalink / raw)
  To: Zach Riggle; +Cc: Zsh Users

On Mon, Aug 23, 2021 at 4:23 PM Zach Riggle <zachriggle@gmail.com> wrote:
>
> >>> 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 *.

You can also do

local first_line=${${(f)ZSH_DEBUG_CMD}[1]}

if that seems more appealing.


^ permalink raw reply	[flat|nested] 6+ messages in thread

* Re: Prevent a specific function from being xtrace'd
  2021-08-23 20:04 ` Bart Schaefer
  2021-08-23 23:23   ` Zach Riggle
@ 2021-08-24 13:09   ` Daniel Shahaf
  1 sibling, 0 replies; 6+ messages in thread
From: Daniel Shahaf @ 2021-08-24 13:09 UTC (permalink / raw)
  To: Zsh Users; +Cc: Zach Riggle

Bart Schaefer wrote on Mon, Aug 23, 2021 at 13:04:42 -0700:
> 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.

Another idea: instead of «set -x» globally, use «functions -T» on every
function except the ones you don't want to trace, as in:

[[[
% f() { g }
% g() { h }
% h() { pwd }
% functions -mT '*' 
% functions +T g 
% f
+f:7> g
+h:7> pwd
/home/daniel
]]]

This won't apply tracing to top-level code (outside of a function).


^ permalink raw reply	[flat|nested] 6+ messages in thread

end of thread, other threads:[~2021-08-24 13:14 UTC | newest]

Thread overview: 6+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-08-23 16:42 Prevent a specific function from being xtrace'd Zach Riggle
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

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).