From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Ray Andrews <rayandrews@eastlink.ca>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: _pick_variant
Date: Thu, 12 Nov 2020 20:17:49 +0100 [thread overview]
Message-ID: <CAN=4vMpYR_5idgr+k-yS+78AeBo7hmuRUr1Z+FdFG+sG4Own0g@mail.gmail.com> (raw)
In-Reply-To: <cafc3aac-62c6-1479-8812-91faa7439a1b@eastlink.ca>
On Thu, Nov 12, 2020 at 8:08 PM Ray Andrews <rayandrews@eastlink.ca> wrote:
>
> On 2020-11-12 10:40 a.m., Roman Perepelitsa wrote:
> > and discovered the hard way that zsh supplies a completion function
> > for a utility of the same name
>
> That's why my last question was how to turn all that kind of thing off.
Sounds like an instance of XY problem. If the problem you are having
is caused by builtin completion functions clashing with your own
private scripts, it doesn't necessarily follow that the best solution
is to disable programmable completions.
FWIW, I know how to disable smart completions for all my scripts
(because they are all in ~/bin, so it's easy) and all my functions
(because they are in ~/functions) with a few lines of zsh but I'm
still wondering what other people do.
Roman.
next prev parent reply other threads:[~2020-11-12 19:18 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 ` Roman Perepelitsa [this message]
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 ` _pick_variant Bart Schaefer
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='CAN=4vMpYR_5idgr+k-yS+78AeBo7hmuRUr1Z+FdFG+sG4Own0g@mail.gmail.com' \
--to=roman.perepelitsa@gmail.com \
--cc=rayandrews@eastlink.ca \
--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).