[vim/vim] `completeopt=menuone,noinsert,fuzzy` leads to selecting second candidate instead of the first (Issue #18802)

11 views
Skip to first unread message

Evgeni Chasnovski

unread,
Nov 23, 2025, 11:26:14 AM (6 days ago) Nov 23
to vim/vim, Subscribed
echasnovski created an issue (vim/vim#18802)

Steps to reproduce

  1. vim --clean
  2. :set completeopt=menuone,noinsert,fuzzy
  3. Add lines "aa", "aaa", and "aaaa" to the current buffer.
  4. On the fourth line in Insert mode press a and <C-n>. Three candidates appear and the second ("aaa") is selected. While I'd expect the first one being selected.

Each of the following changes make it work as expected (order of :

  • Use :set completeopt=menuone,noinsert - first item selected.
  • Use :set completeopt=menuone,noinsert,fuzzy,nosort - first item selected.
  • Use :set completeopt=menuone,noselect,fuzzy - no item is selected.

The likely source of this is #18497 (@girishji). I've bisected it in Neovim codebase.

Expected behaviour

Presence of fuzzy flag in 'completeopt' does not affect how 'noinsert' flag works.

Version of Vim

9.1.1908

Environment

OS: EndeavourOS Linux x86_64, 6.17.8-arch1-1
Terminal: Ghostty 1.2.3-arch2
Value of $TERM: xterm-ghostty
Shell: nushell 0.108.0

Logs and stack traces


Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18802@github.com>

Brian Carbone

unread,
Nov 23, 2025, 11:36:05 AM (6 days ago) Nov 23
to vim/vim, Subscribed
briancarbone left a comment (vim/vim#18802)

Linking to #18800 (comment).


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issues/18802/3568134398@github.com>

Christian Brabandt

unread,
Nov 27, 2025, 3:26:03 PM (2 days ago) Nov 27
to vim/vim, Subscribed

Closed #18802 as completed via 057ea12.


Reply to this email directly, view it on GitHub.

You are receiving this because you are subscribed to this thread.Message ID: <vim/vim/issue/18802/issue_event/21229294843@github.com>

Reply all
Reply to author
Forward
0 new messages