Mercurial > vim
changeset 33443:6da0f8fc3046
runtime(doc): fix two typos in `vim9.txt` and `options.txt` (#13258)
Commit: https://github.com/vim/vim/commit/b043ff34c1e475a90a5142eabaf1db74ab7ebb98
Author: Aliaksei Budavei <32549825+zzzyxwvut@users.noreply.github.com>
Date: Tue Oct 3 17:39:53 2023 +0300
runtime(doc): fix two typos in `vim9.txt` and `options.txt` (https://github.com/vim/vim/issues/13258)
Signed-off-by: Christian Brabandt <cb@256bit.org>
| author | Christian Brabandt <cb@256bit.org> |
|---|---|
| date | Tue, 03 Oct 2023 16:45:05 +0200 |
| parents | 758163111af3 |
| children | 0a2c50b59f30 |
| files | runtime/doc/options.txt runtime/doc/vim9.txt |
| diffstat | 2 files changed, 2 insertions(+), 2 deletions(-) [+] |
line wrap: on
line diff
--- a/runtime/doc/options.txt +++ b/runtime/doc/options.txt @@ -435,7 +435,7 @@ Set using a variable with lambda express let &tagfunc = L In Vim9 script, in a compiled function, you can use a lambda, but a -closured does not work, because the function will be called without the +closure does not work, because the function will be called without the context of where it was defined.
--- a/runtime/doc/vim9.txt +++ b/runtime/doc/vim9.txt @@ -1789,7 +1789,7 @@ filename. For example: > Then you can use "that.item", etc. You are free to choose the name "that". Use something that will be recognized as referring to the imported script. Avoid command names, command modifiers and builtin function names, because the -name will shadow them. Better not start the name starts with a capital +name will shadow them. It's better not to start the name with a capital letter, since it can then also shadow global user commands and functions. Also, you cannot use the name for something else in the script, such as a function or variable name.