Mercurial > vim
changeset 36125:789009a72bcf
runtime(doc): Revert outdated comment in completeopt's fuzzy documentation
Commit: https://github.com/vim/vim/commit/26e4b000025ea0e25ea7877314d9095737431bae
Author: Yee Cheng Chin <ychin.git@gmail.com>
Date: Tue Sep 10 20:50:08 2024 +0200
runtime(doc): 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.
closes: #15656
Signed-off-by: Yee Cheng Chin <ychin.git@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
author | Christian Brabandt <cb@256bit.org> |
---|---|
date | Tue, 10 Sep 2024 21:00:10 +0200 |
parents | a73a96a11372 |
children | a2ba39a96e85 |
files | runtime/doc/options.txt |
diffstat | 1 files changed, 2 insertions(+), 5 deletions(-) [+] |
line wrap: on
line diff
--- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -1,4 +1,4 @@ -*options.txt* For Vim version 9.1. Last change: 2024 Sep 07 +*options.txt* For Vim version 9.1. Last change: 2024 Sep 10 VIM REFERENCE MANUAL by Bram Moolenaar @@ -2148,10 +2148,7 @@ A jump table for the options with a shor 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)