zsh-users
 help / color / mirror / code / Atom feed
From: Zach Riggle <zachriggle@gmail.com>
To: "Lawrence Velázquez" <larryv@zsh.org>
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:33:31 -0500	[thread overview]
Message-ID: <CAMP9c5nbL8z+tjTb3Ub1_nS9T33FNiX4O1qkt_Z3B=ZQwgF+jg@mail.gmail.com> (raw)
In-Reply-To: <4369c556-7ccb-4866-8e69-9d829afc81c3@www.fastmail.com>

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

Wouldn't the above also break for this?

    function unhash() { ... }

It would be nice if we could add a feature such that the "builtin"
identifier cannot be overloaded.

*Zach Riggle*


On Fri, Aug 12, 2022 at 1:43 PM Lawrence Velázquez <larryv@zsh.org> wrote:

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

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

  reply	other threads:[~2022-08-12 19:39 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 [this message]
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='CAMP9c5nbL8z+tjTb3Ub1_nS9T33FNiX4O1qkt_Z3B=ZQwgF+jg@mail.gmail.com' \
    --to=zachriggle@gmail.com \
    --cc=congdanhqx@gmail.com \
    --cc=d.s@daniel.shahaf.name \
    --cc=larryv@zsh.org \
    --cc=stephane@chazelas.org \
    --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).