zsh-users
 help / color / mirror / code / Atom feed
From: "Paul" <GammaFunction@vivaldi.net>
To: "Zsh MailingList" <zsh-users@zsh.org>
Subject: Interactive menu completion bug
Date: Mon, 22 Feb 2021 10:39:47 -0600	[thread overview]
Message-ID: <C9G7HZ4AJF7B.17SN95JM7VB9A@kbvv> (raw)
In-Reply-To: <CADjGqHvGch-bdeDAv1p-AWc7zkJJzErBU3ampro=cFQ5QtnAwQ@mail.gmail.com>

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.

    zmodload zsh/complist
    setopt MENU_COMPLETE
    zstyle ':completion:*:default' menu yes select interactive
    autoload -Uz compinit
    compinit

    # for demo purposes:
    touch ~/a{b,c}

The following and similar inputs show issues [1]:

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

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

The user finishes the token/word themselves instead of accepting one of
the menu's completions. The completer doesn't update the location to
insert the new completion. Instead, the new completion is inserted at
the original location rather than where it should be.

[1]: Demo: https://asciinema.org/a/dZXOf1HGc5zj8AWJ4Ea3lBiGr


  parent reply	other threads:[~2021-02-22 16:59 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             ` Paul [this message]
2021-02-22 21:50               ` Interactive menu completion bug Bart Schaefer
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:
  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=C9G7HZ4AJF7B.17SN95JM7VB9A@kbvv \
    --to=gammafunction@vivaldi.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).