help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Paul <GammaFunction@vivaldi.net>
Cc: Zsh MailingList <zsh-users@zsh.org>
Subject: Re: Interactive menu completion bug
Date: Mon, 22 Feb 2021 13:50:50 -0800	[thread overview]
Message-ID: <CAH+w=7Ydw1hMwccbPJr7Xvr8AkVW-PfvQ6VJMr7mRNZRSweN8Q@mail.gmail.com> (raw)
In-Reply-To: <C9G7HZ4AJF7B.17SN95JM7VB9A@kbvv>

On Mon, Feb 22, 2021 at 8:58 AM Paul <GammaFunction@vivaldi.net> wrote:
> This is unrelated to the previous bug I mentioned, and apologies if this
> has been brought forward before. There is a more problematic issue with
> the menu when in the `interactive` setting.

> echo ~/a<Tab>b <Tab><arrow-right>

I think the issue here is that typing SPACE does not end the
interactive completion, so even though the buffer has advanced, you're
still interactively completing the same word as previously.  This one
is fixed by doing

bindkey -M menuselect " " accept-line

> echo $a<Tab>liases[<arrow-right>

This one is more problematic.  You can at least prevent the word so
far from being clobbered by doing

bindkey -M menuselect "[" .self-insert

but there's probably a context-dependent set of characters that could
be typed at the end of a word, some of which should self-insert and
then end the completion, but others of which should have the effect of
ending the current word, self-inserting, and then resuming completion.

  reply	other threads:[~2021-02-22 21:51 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-15 20:21 Call for volunteers: Patch Manager Daniel Shahaf
2021-02-15 21:06 ` TJ Luoma
2021-02-15 22:20   ` Daniel Shahaf
2021-02-15 23:29     ` Ray Andrews
2021-02-17 22:36       ` Daniel Shahaf
2021-02-17 23:30         ` Ray Andrews
2021-02-18  1:42           ` TJ Luoma
2021-02-18 17:28             ` Daniel Shahaf
2021-02-18 23:16             ` Lawrence Velázquez
2021-02-22 16:39             ` Interactive menu completion bug Paul
2021-02-22 21:50               ` Bart Schaefer [this message]
2021-02-18 23:11         ` Call for volunteers: Patch Manager Lawrence Velázquez
2021-02-19 16:04           ` Daniel Shahaf

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAH+w=7Ydw1hMwccbPJr7Xvr8AkVW-PfvQ6VJMr7mRNZRSweN8Q@mail.gmail.com' \
    --to=schaefer@brasslantern.com \
    --cc=GammaFunction@vivaldi.net \
    --cc=zsh-users@zsh.org \


* 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


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).