adam/vim
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Update runtime files.

Browse Source
This commit is contained in:
Bram Moolenaar
2020-09-07 22:18:52 +02:00
parent 9c929713b7
commit 1c6737b20a
35 changed files with 1272 additions and 307 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
runtime/doc/usr_40.txt
View File

@ -1,4 +1,4 @@
*usr_40.txt* For Vim version 8.2. Last change: 2020 Jul 28
*usr_40.txt* For Vim version 8.2. Last change: 2020 Sep 02
VIM USER MANUAL - by Bram Moolenaar
@ -453,15 +453,15 @@ matching BufWritePre autocommands and executes them, and then it
performs the ":write".
The general form of the :autocmd command is as follows: >
:autocmd [group] {events} {file-pattern} [nested] {command}
:autocmd [group] {events} {file-pattern} [++nested] {command}
The [group] name is optional. It is used in managing and calling the commands
(more on this later). The {events} parameter is a list of events (comma
separated) that trigger the command.
{file-pattern} is a filename, usually with wildcards. For example, using
"*.txt" makes the autocommand be used for all files whose name end in ".txt".
The optional [nested] flag allows for nesting of autocommands (see below), and
finally, {command} is the command to be executed.
The optional [++nested] flag allows for nesting of autocommands (see below),
and finally, {command} is the command to be executed.
EVENTS
@ -578,7 +578,7 @@ trigger any new events. If you read a file in response to a FileChangedShell
event, it will not trigger the autocommands that would set the syntax, for
example. To make the events triggered, add the "nested" argument: >
:autocmd FileChangedShell * nested edit
:autocmd FileChangedShell * ++nested edit
EXECUTING AUTOCOMMANDS