zsh-users
 help / color / mirror / code / Atom feed
From: Pier Paolo Grassi <pierpaolog@gmail.com>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: functions -t
Date: Wed, 13 Oct 2021 13:58:53 +0200	[thread overview]
Message-ID: <CAP+y1xArqkiAy9e3UQpTkhx-WfndWvX_GMDGnW8ECtiXN16pXQ@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7YzwqDu91riW9-CeV-0hha3_7n7Ec3wzYJXgk64arYCmw@mail.gmail.com>

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

Hello Bart, after my email I thought of implementing the way you suggested
and it works fine, I was reluctant to do so since I can have a variable
number of functions to trace (solved with an array and a loop) and was
confronting with the dilemma of don't wanting to clutter any "functions -T"
issued in the parent context, but that would need to be able to know if a
function has the trace activated or not, and I believe this is not
possibile, but of course I can be wrong. Also I don't really see the
practical application for this more complex behaviour so I can be happy
with what I have
thanks

Pier Paolo Grassi


Il giorno mer 13 ott 2021 alle ore 05:47 Bart Schaefer <
schaefer@brasslantern.com> ha scritto:

> On Tue, Oct 12, 2021 at 8:35 PM Bart Schaefer <schaefer@brasslantern.com>
> wrote:
> >
> > Yes.  Tracing of individual functions is not an option controlled by
> > setopt.
>
> Sorry, I'm being imprecise.  You can turn off the trace by using
> setopt INSIDE the traced function.  But it's not controlled by setopt
> in the CALLING function, so you can't localoptions it.
>

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

  reply	other threads:[~2021-10-13 12:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-13  3:03 Pier Paolo Grassi
2021-10-13  3:06 ` Pier Paolo Grassi
2021-10-13  3:35   ` Bart Schaefer
2021-10-13  3:47     ` Bart Schaefer
2021-10-13 11:58       ` Pier Paolo Grassi [this message]
2021-10-13 18:42         ` Daniel Shahaf
2021-10-13 18:44           ` Pier Paolo Grassi
2021-10-13 19:48             ` Bart Schaefer
2021-10-13 20:11               ` Daniel Shahaf
2021-10-13 22:08                 ` Bart Schaefer

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=CAP+y1xArqkiAy9e3UQpTkhx-WfndWvX_GMDGnW8ECtiXN16pXQ@mail.gmail.com \
    --to=pierpaolog@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).