From c60b7d440dacd77284567fe824bf247b63518d58 Mon Sep 17 00:00:00 2001 From: Yee Cheng Chin Date: Tue, 10 Sep 2024 02:02:08 -0700 Subject: [PATCH] Revert outdated comment in completeopt's fuzzy documentation Originally, `:set completeopt+=fuzzy` did not affect how the candidate list is collected in default keyword completion. A comment was added to documentation as part of #14912 to clarify it. #15193 later changed the fuzzy behavior to now change the candidate collection behavior as well so the clarification in docs is now wrong. Remove them here. --- runtime/doc/options.txt | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt index 50c25f7b25287c..24e41965f00375 100644 --- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -2148,10 +2148,7 @@ 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. 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). + if the exact sequence is not typed. *'completepopup'* *'cpp'* 'completepopup' 'cpp' string (default empty)