From: Bart Schaefer <schaefer@brasslantern.com>
To: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Cc: Thomas Lauer <thomas.lauer@virgin.net>, Zsh Users <zsh-users@zsh.org>
Subject: Re: _pick_variant
Date: Fri, 13 Nov 2020 14:26:34 -0800 [thread overview]
Message-ID: <CAH+w=7aBLqnchtGB00kPv-XqX1MrXFqYLmWqRVVfUiKmiBaszA@mail.gmail.com> (raw)
In-Reply-To: <CAN=4vMq45pnkpKFx9ntbfP68zGjq5gO5e_43r-F3hoiJcFSiqw@mail.gmail.com>
On Fri, Nov 13, 2020 at 2:42 AM Roman Perepelitsa
<roman.perepelitsa@gmail.com> wrote:
>
> The clash isn't with an existing command but rather with a completion
> function that's included in zsh.
It is conceivably possible to rewrite compinit such that it does not
install completions for commands not found in $path, but as you
mention in a later message in this thread, that will increase startup
time, and/or has to be incorporated into the .zcompdump cache.
> My latest similar clash was with the open command. This is a macOS
> command but I'm using Linux, so I cannot even have the open command
> that _open expects.
That's why _open is in the Completion/Darwin subtree; in an ideal
world, a linux install would omit files in that subtree from $fpath.
In practice, everybody seems to install everything everywhere.
next prev parent reply other threads:[~2020-11-13 22:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 17:41 _pick_variant Thomas Lauer
2020-11-12 18:35 ` _pick_variant Bart Schaefer
2020-11-12 18:40 ` _pick_variant Roman Perepelitsa
2020-11-12 19:07 ` _pick_variant Ray Andrews
2020-11-12 19:17 ` _pick_variant Roman Perepelitsa
2020-11-12 19:20 ` Fwd: _pick_variant JAMES R CUTLER
2020-11-13 9:34 ` _pick_variant Thomas Lauer
2020-11-13 10:42 ` _pick_variant Roman Perepelitsa
2020-11-13 10:57 ` _pick_variant Thomas Lauer
2020-11-13 11:18 ` _pick_variant Roman Perepelitsa
2020-11-13 22:26 ` Bart Schaefer [this message]
2020-11-14 9:56 ` _pick_variant Thomas Lauer
2020-11-14 19:21 ` _pick_variant Bart Schaefer
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=7aBLqnchtGB00kPv-XqX1MrXFqYLmWqRVVfUiKmiBaszA@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=roman.perepelitsa@gmail.com \
--cc=thomas.lauer@virgin.net \
--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).