From: Bart Schaefer <schaefer@brasslantern.com>
To: Pier Paolo Grassi <pierpaolog@gmail.com>
Cc: Zsh-Users List <zsh-users@zsh.org>
Subject: Re: debug functions
Date: Wed, 10 Feb 2021 14:56:21 -0800 [thread overview]
Message-ID: <CAH+w=7Y8O7e7Yy7bcK9fm1Yx_966L4g3LiKPxT_GOX9hxeGe_g@mail.gmail.com> (raw)
In-Reply-To: <CAP+y1xC9h5nOC_TBApaPf_qYSUN4=vApbmVvVQ07TE=uh467Aw@mail.gmail.com>
On Wed, Feb 10, 2021 at 2:08 PM Pier Paolo Grassi <pierpaolog@gmail.com> wrote:
>
> function_name (){
> functions -T $0
> ...
> }
I think it'd be a bit convoluted ...
function_name () {
if [[ -o xtrace ]]
then
# The real function body here
else
functions -T function_name
{
function_name "$@"
} always {
functions +T function_name
}
fi
}
next prev parent reply other threads:[~2021-02-10 22:57 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-02-10 22:07 Pier Paolo Grassi
2021-02-10 22:56 ` Bart Schaefer [this message]
2021-02-10 23:04 ` Pier Paolo Grassi
2021-02-12 3:21 ` Bart Schaefer
2021-02-12 9:30 ` Pier Paolo Grassi
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=7Y8O7e7Yy7bcK9fm1Yx_966L4g3LiKPxT_GOX9hxeGe_g@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=pierpaolog@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).