]> git.ipfire.org Git - thirdparty/vim.git/commitdiff
runtime(doc): clarify how fuzzy 'completeopt' should work
authorChristian Brabandt <cb@256bit.org>
Tue, 4 Jun 2024 18:27:18 +0000 (20:27 +0200)
committerChristian Brabandt <cb@256bit.org>
Tue, 4 Jun 2024 18:27:18 +0000 (20:27 +0200)
related: #14912

Signed-off-by: Christian Brabandt <cb@256bit.org>
runtime/doc/options.txt

index bc7f687139cde60b46f4f5543fef9e113f9caadb..57fefa2237ab7e271d4d52c2ae9fb5d5e697ba71 100644 (file)
@@ -1,4 +1,4 @@
-*options.txt*  For Vim version 9.1.  Last change: 2024 Jun 03
+*options.txt*  For Vim version 9.1.  Last change: 2024 Jun 04
 
 
                  VIM REFERENCE MANUAL    by Bram Moolenaar
@@ -2147,7 +2147,10 @@ A jump table for the options with a short description can be found at |Q_op|.
           fuzzy    Enable |fuzzy-matching| for completion candidates. This
                    allows for more flexible and intuitive matching, where
                    characters can be skipped and matches can be found even
-                   if the exact sequence is not typed.
+                   if the exact sequence is not typed.  Only makes a
+                   difference how completion candidates are reduced from the
+                   list of alternatives, but not how the candidates are
+                   collected (using different completion types).
 
                                        *'completepopup'* *'cpp'*
 'completepopup' 'cpp'  string (default empty)