From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Aliases that ignore "noaliases"
Date: Mon, 1 Apr 2024 17:28:23 -0700 [thread overview]
Message-ID: <CAH+w=7YgQD-X4dD5rurpKNkThwcoL6==Xvs+Qsa_Sn0-GWavbQ@mail.gmail.com> (raw)
In-Reply-To: <20240401201841.dpet5winsejmb3bn@chazelas.org>
On Mon, Apr 1, 2024 at 1:18 PM Stephane Chazelas <stephane@chazelas.org> wrote:
>
> TLDR, I think zsh should avoid having builtin aliases.
In the cases I'm thinking of, it doesn't really have to behave like an
alias in the sense of lex-time textual replacement. For builtins, we
already have a number of them that invoke the same C function
underneath, with different lists of allowed and default options
handled by the "front end" for builtintab entries. Something similar
for reserved words would go a long way. Sort of the way "zle -C" uses
a builtin widget to define how a user-defined one should behave.
The "suspend" example from ksh is not particularly apt here because
I'm interested in defining syntax rather than (re-)implementing
commands, so naming would have to be approached just as carefully as
with any new reserved word.
prev parent reply other threads:[~2024-04-02 0:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-01 19:59 Bart Schaefer
2024-04-01 20:18 ` Stephane Chazelas
2024-04-01 20:20 ` Stephane Chazelas
2024-04-02 0:28 ` Bart Schaefer [this message]
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=7YgQD-X4dD5rurpKNkThwcoL6==Xvs+Qsa_Sn0-GWavbQ@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@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).