Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Aliases that ignore "noaliases"
- X-seq: zsh-workers 52869
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: Re: Aliases that ignore "noaliases"
- Date: Mon, 1 Apr 2024 17:28:23 -0700
- Archived-at: <https://zsh.org/workers/52869>
- In-reply-to: <20240401201841.dpet5winsejmb3bn@chazelas.org>
- List-id: <zsh-workers.zsh.org>
- References: <CAH+w=7bgYJTaMfurw357eHikQL9bQs=DUfBU_VNy4BEyWgvFZg@mail.gmail.com> <20240401201841.dpet5winsejmb3bn@chazelas.org>
On Mon, Apr 1, 2024 at 1:18 PM Stephane Chazelas <stephane@xxxxxxxxxxxx> 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.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author