From: "Daniel Shahaf" <d.s@daniel.shahaf.name>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] _pick_variant: Update builtin check
Date: Thu, 21 Mar 2019 07:57:38 -0400 [thread overview]
Message-ID: <bc309e59-3f74-4dea-a060-425f429f4430@www.fastmail.com> (raw)
In-Reply-To: <20190321001636.GA57147@CptOrmolo.darkstar>
Matthew Martin wrote on Thu, 21 Mar 2019 00:17 +00:00:
> On Wed, Mar 20, 2019 at 01:05:23PM +0000, Daniel Shahaf wrote:
> > Matthew Martin wrote on Wed, Mar 20, 2019 at 07:52:39 -0500:
> > > +builtin_precommands=(- builtin eval exec nocorrect noglob time)
> >
> > May I suggest a comment here documenting the semantics of this variable?
> > For example, why doesn't it list the 'command' precommand (presumably
> > becaus that one doesn't preserve builtins, but this info should be in
> > the comment, not in the list archives)?
>
> How's
> +# Precommands which allow the command to be builtin (unlike command and sudo).
> +local -ar builtin_precommands=(- builtin eval exec nocorrect noglob time)
I understand what you mean in the context of this thread, but I think
the two uses of the term 'command' might be confusing to someone who
opens the file in a year or three. How about:
# Precommands which allow their wrapped command to be a builtin.
# All of these are necessarily builtins or reserved words themselves, but not all builtin precommands are listed here: for one, the 'command' builtin is excluded.
Cheers,
Daniel
next prev parent reply other threads:[~2019-03-21 11:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-20 2:05 Matthew Martin
2019-03-20 3:38 ` Matthew Martin
2019-03-20 12:52 ` Matthew Martin
2019-03-20 13:05 ` Daniel Shahaf
2019-03-21 0:16 ` Matthew Martin
2019-03-21 11:57 ` Daniel Shahaf [this message]
2019-03-21 12:40 ` Matthew Martin
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=bc309e59-3f74-4dea-a060-425f429f4430@www.fastmail.com \
--to=d.s@daniel.shahaf.name \
--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).