From 15e42dd4498829e5315b9b0da7384bedf466d707 Mon Sep 17 00:00:00 2001 From: zeertzjq Date: Tue, 17 Jan 2023 12:38:16 +0800 Subject: vim-patch:8.2.4608: getcompletion() does not work when 'wildoptions' has "fuzzy" Problem: getcompletion() does not work properly when 'wildoptions contains "fuzzy". Solution: Do not use addstar(). (Yegappan Lakshmanan, closes vim/vim#9992, closes vim/vim#9986) https://github.com/vim/vim/commit/e7dd0fa2c61fe71f12c72b0dcb7bb6415eb048fb Co-authored-by: Yegappan Lakshmanan --- runtime/doc/builtin.txt | 4 ++++ 1 file changed, 4 insertions(+) (limited to 'runtime') diff --git a/runtime/doc/builtin.txt b/runtime/doc/builtin.txt index 3dc21c0d73..bdbd026a09 100644 --- a/runtime/doc/builtin.txt +++ b/runtime/doc/builtin.txt @@ -3000,6 +3000,10 @@ getcompletion({pat}, {type} [, {filtered}]) *getcompletion()* is applied to filter the results. Otherwise all the matches are returned. The 'wildignorecase' option always applies. + If the 'wildoptions' option contains "fuzzy", then fuzzy + matching is used to get the completion matches. Otherwise + regular expression matching is used. + If {type} is "cmdline", then the |cmdline-completion| result is returned. For example, to complete the possible values after a ":call" command: > -- cgit