From: Thomas Lauer <thomas.lauer@virgin.net>
To: "Daniel Shahaf" <d.s@daniel.shahaf.name>
Cc: "?oàn Tr?n Công Danh" <congdanhqx@gmail.com>,
"Zach Riggle" <zachriggle@gmail.com>,
"Zsh Users" <zsh-users@zsh.org>
Subject: Re: Overriding "builtin"
Date: Fri, 12 Aug 2022 14:54:39 +0100 [thread overview]
Message-ID: <glmcfh1u38uks553f5lq84jjoo6pn561i0@tlc.com> (raw)
In-Reply-To: <64b57144-d4af-4708-983b-0bd202557bbd@www.fastmail.com>
From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
Date: Fri, 12 Aug 2022 07:12:56 +0000
> ?oàn Tr?n Công Danh wrote on Fri, 12 Aug 2022 02:24 +00:00:
> > On 2022-08-11 20:18:49-0500, Zach Riggle <zachriggle@gmail.com> wrote:
> >> I recently learned that 'builtin' can be overridden with a function. Neat
> >> for some silly tricks!
> >>
> >> However, is there a way to save / restore 'builtin' such that it can be
> >> restored?
> >>
> >> All that I can think of is 'unfunction builtin', but 'unfunction' itself
> >> can be overridden with a function.
> >
>
> «unset 'functions[unfunction]'», provided (zsh/parameter is available
> and) someone hasn't created an unset() function as well.
>
> > You can run original builtin with "builtin".
> >
> > e.g.:
> >
> > echo() { printf '++%s\n' "$@"; }
> > echo this will run function
> > builtin echo this will run builtin
>
> No, he can't, because in his case that'd be a bottomless recursive call
> (= an infinite loop).
Hm... this works here as I'd expect, but since you said "in his case"
there may be something that turns that into a non-terminating recursion
just for Zach's case. But what? (Always eager to learn something :-/ )
Tom
next prev parent reply other threads:[~2022-08-12 13:55 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-12 1:18 Zach Riggle
2022-08-12 2:24 ` Đoàn Trần Công Danh
2022-08-12 7:12 ` Daniel Shahaf
2022-08-12 7:57 ` Stephane Chazelas
2022-08-12 18:42 ` Lawrence Velázquez
2022-08-12 19:33 ` Zach Riggle
2022-08-12 20:35 ` Lawrence Velázquez
2022-08-12 20:54 ` Bart Schaefer
2022-08-29 20:42 ` Zach Riggle
2022-08-30 1:31 ` Bart Schaefer
2022-08-30 1:41 ` Bart Schaefer
2022-08-12 13:54 ` Thomas Lauer [this message]
2022-08-12 15:41 ` Bart Schaefer
2022-08-12 16:07 ` Thomas Lauer
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=glmcfh1u38uks553f5lq84jjoo6pn561i0@tlc.com \
--to=thomas.lauer@virgin.net \
--cc=congdanhqx@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=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).