zsh-users
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zach Riggle <zachriggle@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: Overriding "builtin"
Date: Fri, 12 Aug 2022 13:54:36 -0700	[thread overview]
Message-ID: <CAH+w=7Ywsq=9dcqwWBXQvajnb9NsCe_OBfV8PurkaG+idnSgdg@mail.gmail.com> (raw)
In-Reply-To: <CAMP9c5nbL8z+tjTb3Ub1_nS9T33FNiX4O1qkt_Z3B=ZQwgF+jg@mail.gmail.com>

On Fri, Aug 12, 2022 at 12:33 PM Zach Riggle <zachriggle@gmail.com> wrote:
>
> It would be nice if we could add a feature such that the "builtin" identifier cannot be overloaded.

This isn't really feasible, given that we have e.g. "disable builtin"
and "alias builtin=...".

That does point out that another approach to bypassing the function is
 disable -f builtin
which is pretty nice in that it leaves the function defined but
inaccessible.  Of course one can still "disable disable" as well.

I can't imagine why anyone would do this, but of course

disable -rm \*
disable -m \*

leaves the shell able to only to execute pipelines built from external
commands.  Preceded with a few "alias -g" of separators, you end up
limited to simple external commands.


  parent reply	other threads:[~2022-08-12 21:02 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 [this message]
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='CAH+w=7Ywsq=9dcqwWBXQvajnb9NsCe_OBfV8PurkaG+idnSgdg@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --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).