From: Bart Schaefer <schaefer@brasslantern.com>
To: Alan <8fvebtoeq87@gmail.com>
Cc: Zsh Users <zsh-users@zsh.org>
Subject: Re: menu-select doesn't respect COMPLETE_IN_WORD option
Date: Sun, 14 Jun 2020 22:09:12 -0700 [thread overview]
Message-ID: <CAH+w=7bm21k8s9VsNvYdQrK+ReSFk=UViM4_29EHTcTPrDYZXw@mail.gmail.com> (raw)
In-Reply-To: <CAH+w=7aiQNO+-1EG2EyrH0JAMienH+aLQ+k9O27E8eTD0RmJFg@mail.gmail.com>
On Sun, Jun 14, 2020 at 5:37 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
>
> On Sat, Jun 13, 2020 at 9:28 PM Alan <8fvebtoeq87@gmail.com> wrote:
> >
> > When I leave completeinword unset, _prefix completion simply doesn't work, even if I have:
>
> If I turn on "completeinword" then I can reproduce your described
> behavior with menu-complete, although expand-or-complete-prefix still
> works as expected. [...]
>
> So I still think you want to leave complete-in-word turned off and
> find out what other part of your startup is breaking things when you
> do.
Ignore that last part, sorry. I just realized that when you wrote
"_prefix completion simply doesn't work" you did not mean that
completion failed, you just mean that it did something you didn't want
it to, and that "something" is probably exactly what I described it
doing.
This documentation is in fact correct: "One gotcha with the _prefix
completer: you have to make sure the option COMPLETE_IN_WORD is set."
prev parent reply other threads:[~2020-06-15 5:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-09 23:56 Alan
2020-06-10 1:11 ` Bart Schaefer
2020-06-10 1:53 ` Alan
2020-06-10 2:25 ` Alan
2020-06-11 2:33 ` Bart Schaefer
2020-06-11 3:26 ` Alan
2020-06-14 3:07 ` Bart Schaefer
2020-06-14 4:28 ` Alan
2020-06-15 0:37 ` Bart Schaefer
2020-06-15 5:09 ` 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=7bm21k8s9VsNvYdQrK+ReSFk=UViM4_29EHTcTPrDYZXw@mail.gmail.com' \
--to=schaefer@brasslantern.com \
--cc=8fvebtoeq87@gmail.com \
--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).