patch 8.2.4463: completion only uses strict matching
Problem: Completion only uses strict matching.
Solution: Add the "fuzzy" item for 'wildoptions'. (Yegappan Lakshmanan,
closes #9803)
diff --git a/runtime/doc/options.txt b/runtime/doc/options.txt
index 3f77562..c8b40ec 100644
--- a/runtime/doc/options.txt
+++ b/runtime/doc/options.txt
@@ -9087,6 +9087,14 @@
feature}
A list of words that change how |cmdline-completion| is done.
The following values are supported:
+ fuzzy Use fuzzy matching to find completion matches. When
+ this value is specified, wildcard expansion will not
+ be used for completion. The matches will be sorted by
+ the "best match" rather than alphabetically sorted.
+ This will find more matches than the wildcard
+ expansion. Currently fuzzy matching based completion
+ is not supported for file and directory names and
+ instead wildcard expansion is used.
pum Display the completion matches using the popupmenu
in the same style as the |ins-completion-menu|.
tagfile When using CTRL-D to list matching tags, the kind of