Mercurial > vim
diff runtime/doc/builtin.txt @ 28183:2b595cee4c85 v8.2.4617
patch 8.2.4617: no completion for :scriptnames
Commit: https://github.com/vim/vim/commit/454ce6737cadb82886f1fc0eb9e8666cc59ae42b
Author: Yegappan Lakshmanan <yegappan@yahoo.com>
Date: Thu Mar 24 11:22:13 2022 +0000
patch 8.2.4617: no completion for :scriptnames
Problem: No completion for :scriptnames.
Solution: Implement :scriptnames completion. (Yegappan Lakshmanan,
closes #10005)
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Thu, 24 Mar 2022 12:30:08 +0100 |
| parents | 130f4082a13d |
| children | e3d6184b89fa |
line wrap: on
line diff
--- a/runtime/doc/builtin.txt +++ b/runtime/doc/builtin.txt @@ -3256,6 +3256,7 @@ getcompletion({pat}, {type} [, {filtered messages |:messages| suboptions option options packadd optional package |pack-add| names + scriptnames sourced script names |:scriptnames| shellcmd Shell command sign |:sign| suboptions syntax syntax file names |'syntax'| @@ -3275,7 +3276,10 @@ getcompletion({pat}, {type} [, {filtered If the 'wildoptions' option contains 'fuzzy', then fuzzy matching is used to get the completion matches. Otherwise - regular expression matching is used. + regular expression matching is used. Thus this function + follows the user preference, what happens on the command line. + If you do not want this you can make 'wildoptions' empty + before calling getcompletion() and restore it afterwards. If {type} is "cmdline", then the |cmdline-completion| result is returned. For example, to complete the possible values after