From c1378413c142e1762b80132c41b10c16c4aa7c13 Mon Sep 17 00:00:00 2001 From: dundargoc Date: Sun, 1 Dec 2024 20:30:39 +0100 Subject: vim-patch:768728b: runtime(doc): Update documentation for "noselect" in 'completeopt' In particular, make the distinction and interaction between "noinsert" and "noselect" clearer as it was very confusing before. closes: vim/vim#16148 https://github.com/vim/vim/commit/768728b48751c5e937409d12d98bfa1fb4c37266 Co-authored-by: dundargoc --- src/nvim/options.lua | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'src') diff --git a/src/nvim/options.lua b/src/nvim/options.lua index 84c90e44a7..97fe09f376 100644 --- a/src/nvim/options.lua +++ b/src/nvim/options.lua @@ -1530,9 +1530,9 @@ return { a match from the menu. Only works in combination with "menu" or "menuone". No effect if "longest" is present. - noselect Do not select a match in the menu, force the user to - select one from the menu. Only works in combination with - "menu" or "menuone". + noselect Same as "noinsert", except that no menu item is + pre-selected. If both "noinsert" and "noselect" are present, + "noselect" has precedence. fuzzy Enable |fuzzy-matching| for completion candidates. This allows for more flexible and intuitive matching, where -- cgit