From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Zach Riggle" <zachriggle@gmail.com>
Cc: "Stephane Chazelas" <stephane@chazelas.org>,
"Daniel Shahaf" <d.s@daniel.shahaf.name>,
"Đoàn Trần Công Danh" <congdanhqx@gmail.com>,
zsh-users@zsh.org
Subject: Re: Overriding "builtin"
Date: Fri, 12 Aug 2022 14:42:39 -0400 [thread overview]
Message-ID: <4369c556-7ccb-4866-8e69-9d829afc81c3@www.fastmail.com> (raw)
In-Reply-To: <c76e1e4bd9997802542764dcc31d03b2@chazelas.org>
On Fri, Aug 12, 2022, at 3:57 AM, Stephane Chazelas wrote:
> On 2022-08-12 08:12, Daniel Shahaf wrote:
> [...]
>> «unset 'functions[unfunction]'», provided (zsh/parameter is available
>> and) someone hasn't created an unset() function as well.
> [...]
>
> Or the standard "unset -f builtin"
>
> Or functions=()
>
> (or exec zsh -f)
>
> Or
>
> builtin() {
> echo my builtin wrapper
> set -o localoptions -o posixbuiltins
> command builtin "$@"
> }
Or ''unhash -f builtin''.
I (perhaps overzealously) interpreted the original question as
asking for a method that is impervious to interference from *any*
function (and maybe alias?) definition. But if you've broken your
shell so hard that *none* of these suggestions works, then, as they
say in the IRC channel, you get to keep the pieces.
--
vq
next prev parent reply other threads:[~2022-08-12 18:44 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 [this message]
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
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=4369c556-7ccb-4866-8e69-9d829afc81c3@www.fastmail.com \
--to=larryv@zsh.org \
--cc=congdanhqx@gmail.com \
--cc=d.s@daniel.shahaf.name \
--cc=stephane@chazelas.org \
--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).