Mercurial > vim
changeset 35329:2a0286c234b8
runtime(doc): clarify how fuzzy 'completeopt' should work
Commit: https://github.com/vim/vim/commit/2a2c4fffd7e04f74b316209404767f128684a9e1
Author: Christian Brabandt <cb@256bit.org>
Date: Tue Jun 4 20:27:18 2024 +0200
runtime(doc): clarify how fuzzy 'completeopt' should work
related: https://github.com/vim/vim/issues/14912
Signed-off-by: Christian Brabandt <cb@256bit.org>
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Tue, 04 Jun 2024 20:30:05 +0200 |
| parents | 409d7108eb2b |
| children | f3b25db9e802 |
| files | runtime/doc/options.txt |
| diffstat | 1 files changed, 5 insertions(+), 2 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 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 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. + 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)