From 768728b48751c5e937409d12d98bfa1fb4c37266 Mon Sep 17 00:00:00 2001 From: dundargoc Date: Sun, 1 Dec 2024 20:06:42 +0100 Subject: [PATCH] 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: #16148 Signed-off-by: dundargoc Signed-off-by: Christian Brabandt --- runtime/doc/options.txt | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt index 764b4ab337..1de1057b22 100644 --- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -1,4 +1,4 @@ -*options.txt* For Vim version 9.1. Last change: 2024 Nov 27 +*options.txt* For Vim version 9.1. Last change: 2024 Dec 01 VIM REFERENCE MANUAL by Bram Moolenaar @@ -2154,9 +2154,9 @@ A jump table for the options with a short description can be found at |Q_op|. 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