summaryrefslogtreecommitdiffstats
path: root/runtime/doc/autocmd.txt
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2022-12-31 15:30:45 +0000
committerBram Moolenaar <Bram@vim.org>2022-12-31 15:30:45 +0000
commitf1dcd14fc5d4370476cd82895a4479ca2d252e54 (patch)
treec5d20989d5b5d69af7f0935c7e6f929126c0e5b8 /runtime/doc/autocmd.txt
parentdb4d88c2adfe8f8122341ac9d6cae27ef78451c8 (diff)
Update runtime files
Diffstat (limited to 'runtime/doc/autocmd.txt')
-rw-r--r--runtime/doc/autocmd.txt4
1 files changed, 2 insertions, 2 deletions
diff --git a/runtime/doc/autocmd.txt b/runtime/doc/autocmd.txt
index 5acf7333d3..73506cc4c0 100644
--- a/runtime/doc/autocmd.txt
+++ b/runtime/doc/autocmd.txt
@@ -1,4 +1,4 @@
-*autocmd.txt* For Vim version 9.0. Last change: 2022 Nov 22
+*autocmd.txt* For Vim version 9.0. Last change: 2022 Dec 12
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -97,7 +97,7 @@ If the `:autocmd` is in Vim9 script (a script that starts with `:vim9script`
and in a `:def` function) then {cmd} will be executed as in Vim9
script. Thus this depends on where the autocmd is defined, not where it is
triggered.
-
+ *:autocmd-block*
{cmd} can be a block, like with `:command`, see |:command-repl|. Example: >
au BufReadPost *.xml {
setlocal matchpairs+=<:>