vim-patch:9.1.1197: process_next_cpt_value() uses wrong condition

Problem:  process_next_cpt_value() uses wrong condition
Solution: use cfc_has_mode() instead and remove redundant else if branch
          (glepnir)

closes: vim/vim#16833

https://github.com/vim/vim/commit/53b14578e03f93a53fd6eb21c00caf96484742ed

Co-authored-by: glepnir <glephunter@gmail.com>

1 files changed, 17 insertions, 8 deletions

diff --git a/src/nvim/options.lua b/src/nvim/options.lua
index 71c96b6770..1a66b32ccc 100644
--- a/src/nvim/options.lua
+++ b/src/nvim/options.lua
@@ -1466,14 +1466,23 @@ local options = {
       flags = true,
       deny_duplicates = true,
       desc = [=[
-        This option enables fuzzy collection for (only some) specific
-        |ins-completion| modes, adjusting how items are gathered for fuzzy
-        matching based on input.
-        The option can contain the following values (separated by commas),
-        each enabling fuzzy collection for a specific completion mode:
-        files		file names
-        keyword		keyword completion in 'complete' and current file
-        whole_line	whole lines
+        A comma-separated list of option enables fuzzy collection for specific
+        |ins-completion| modes, affecting how items are gathered during
+        completion. When set, fuzzy matching is used to find completion
+        candidates instead of the standard prefix-based matching. This option
+        can contain the following values are:
+
+        keyword		keywords in the current file |i_CTRL-X_CTRL-N|
+        		keywords with the ".", "w", "b", "u", "U" and
+        		"k{dict}" flags in 'complete'. |i_CTRL-N| |i_CTRL-P|
+
+        files		file names  |i_CTRL-X_CTRL-F|
+
+        whole_line	whole lines |i_CTRL-X_CTRL-L|
+
+        When used with 'completeopt' "longest" option, fuzzy collection can
+        identify the longest common string among the best fuzzy matches and
+        automatically insert it.
       ]=],
       full_name = 'completefuzzycollect',
       list = 'onecomma',