From bf62672d59299cc548103bdf7d8d162043acd011 Mon Sep 17 00:00:00 2001 From: zeertzjq Date: Wed, 11 Sep 2024 06:04:57 +0800 Subject: vim-patch:26e4b00: 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 vim/vim#14912 to clarify it. vim/vim#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: vim/vim#15656 https://github.com/vim/vim/commit/26e4b000025ea0e25ea7877314d9095737431bae Co-authored-by: Yee Cheng Chin --- src/nvim/options.lua | 5 +---- 1 file changed, 1 insertion(+), 4 deletions(-) (limited to 'src') diff --git a/src/nvim/options.lua b/src/nvim/options.lua index bb63ff638b..c028999d61 100644 --- a/src/nvim/options.lua +++ b/src/nvim/options.lua @@ -1505,10 +1505,7 @@ local options = { 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. longest Only insert the longest common text of the matches. If the menu is displayed you can use CTRL-L to add more -- cgit