Mercurial > vim
annotate runtime/doc/autocmd.txt @ 25978:40b17deb294f v8.2.3522
patch 8.2.3522: cannot use x and u when setting 'listchars'
Commit: https://github.com/vim/vim/commit/93ff6720fe4427341bc426b6d46e6324f226c270
Author: Bram Moolenaar <Bram@vim.org>
Date: Sat Oct 16 17:51:40 2021 +0100
patch 8.2.3522: cannot use \x and \u when setting 'listchars'
Problem: Cannot use \x and \u when setting 'listchars'.
Solution: Support hex and unicode in hex form. (closes https://github.com/vim/vim/issues/9006)
author | Bram Moolenaar <Bram@vim.org> |
---|---|
date | Sat, 16 Oct 2021 19:00:03 +0200 |
parents | 3b34837f4538 |
children | 6b39ab99e367 |
rev | line source |
---|---|
25880 | 1 *autocmd.txt* For Vim version 8.2. Last change: 2021 Oct 04 |
7 | 2 |
3 | |
4 VIM REFERENCE MANUAL by Bram Moolenaar | |
5 | |
6 | |
14193 | 7 Automatic commands *autocommand* *autocommands* |
7 | 8 |
9 For a basic explanation, see section |40.3| in the user manual. | |
10 | |
11 1. Introduction |autocmd-intro| | |
12 2. Defining autocommands |autocmd-define| | |
13 3. Removing autocommands |autocmd-remove| | |
14 4. Listing autocommands |autocmd-list| | |
15 5. Events |autocmd-events| | |
16 6. Patterns |autocmd-patterns| | |
40 | 17 7. Buffer-local autocommands |autocmd-buflocal| |
18 8. Groups |autocmd-groups| | |
19 9. Executing autocommands |autocmd-execute| | |
20 10. Using autocommands |autocmd-use| | |
590 | 21 11. Disabling autocommands |autocmd-disable| |
7 | 22 |
23 | |
24 ============================================================================== | |
25 1. Introduction *autocmd-intro* | |
26 | |
22 | 27 You can specify commands to be executed automatically when reading or writing |
28 a file, when entering or leaving a buffer or window, and when exiting Vim. | |
29 For example, you can create an autocommand to set the 'cindent' option for | |
30 files matching *.c. You can also use autocommands to implement advanced | |
7 | 31 features, such as editing compressed files (see |gzip-example|). The usual |
32 place to put autocommands is in your .vimrc or .exrc file. | |
33 | |
13231 | 34 *E203* *E204* *E143* *E855* *E937* *E952* |
7 | 35 WARNING: Using autocommands is very powerful, and may lead to unexpected side |
36 effects. Be careful not to destroy your text. | |
37 - It's a good idea to do some testing on an expendable copy of a file first. | |
38 For example: If you use autocommands to decompress a file when starting to | |
39 edit it, make sure that the autocommands for compressing when writing work | |
40 correctly. | |
41 - Be prepared for an error halfway through (e.g., disk full). Vim will mostly | |
42 be able to undo the changes to the buffer, but you may have to clean up the | |
43 changes to other files by hand (e.g., compress a file that has been | |
44 decompressed). | |
45 - If the BufRead* events allow you to edit a compressed file, the FileRead* | |
46 events should do the same (this makes recovery possible in some rare cases). | |
47 It's a good idea to use the same autocommands for the File* and Buf* events | |
48 when possible. | |
49 | |
50 ============================================================================== | |
51 2. Defining autocommands *autocmd-define* | |
52 | |
53 *:au* *:autocmd* | |
16217
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
54 :au[tocmd] [group] {event} {pat} [++once] [++nested] {cmd} |
7 | 55 Add {cmd} to the list of commands that Vim will |
56 execute automatically on {event} for a file matching | |
24911 | 57 {pat} |autocmd-patterns|. |
23798
59efd230b373
patch 8.2.2440: documentation based on patches is outdated
Bram Moolenaar <Bram@vim.org>
parents:
23305
diff
changeset
|
58 Here {event} cannot be "*". *E1155* |
13482
9eebe457eb3c
Update runtime files. Convert a couple of help files to utf-8.
Christian Brabandt <cb@256bit.org>
parents:
13444
diff
changeset
|
59 Note: A quote character is seen as argument to the |
9eebe457eb3c
Update runtime files. Convert a couple of help files to utf-8.
Christian Brabandt <cb@256bit.org>
parents:
13444
diff
changeset
|
60 :autocmd and won't start a comment. |
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1919
diff
changeset
|
61 Vim always adds the {cmd} after existing autocommands, |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1919
diff
changeset
|
62 so that the autocommands execute in the order in which |
16217
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
63 they were given. |
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
64 See |autocmd-nested| for [++nested]. "nested" |
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
65 (without the ++) can also be used, for backwards |
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
66 compatibility. |
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
67 *autocmd-once* |
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
68 If [++once] is supplied the command is executed once, |
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
69 then removed ("one shot"). |
7 | 70 |
40 | 71 The special pattern <buffer> or <buffer=N> defines a buffer-local autocommand. |
72 See |autocmd-buflocal|. | |
73 | |
23164 | 74 If the `:autocmd` is in Vim9 script (a script that starts with `:vim9script` |
75 and in a `:def` function) then {cmd} will be executed as in Vim9 | |
22958 | 76 script. Thus this depends on where the autocmd is defined, not where it is |
77 triggered. | |
78 | |
25619 | 79 {cmd} can be a block, like with `:command`, see |:command-repl|. Example: > |
25463
05f9e8f2016c
patch 8.2.3268: cannot use a block with :autocmd like with :command
Bram Moolenaar <Bram@vim.org>
parents:
25402
diff
changeset
|
80 au BufReadPost *.xml { |
05f9e8f2016c
patch 8.2.3268: cannot use a block with :autocmd like with :command
Bram Moolenaar <Bram@vim.org>
parents:
25402
diff
changeset
|
81 setlocal matchpairs+=<:> |
05f9e8f2016c
patch 8.2.3268: cannot use a block with :autocmd like with :command
Bram Moolenaar <Bram@vim.org>
parents:
25402
diff
changeset
|
82 /<start |
05f9e8f2016c
patch 8.2.3268: cannot use a block with :autocmd like with :command
Bram Moolenaar <Bram@vim.org>
parents:
25402
diff
changeset
|
83 } |
05f9e8f2016c
patch 8.2.3268: cannot use a block with :autocmd like with :command
Bram Moolenaar <Bram@vim.org>
parents:
25402
diff
changeset
|
84 |
9653
01c9630e80e0
commit https://github.com/vim/vim/commit/e99e84497b89e5f91df519790802770920ecf4fe
Christian Brabandt <cb@256bit.org>
parents:
9599
diff
changeset
|
85 Note: The ":autocmd" command can only be followed by another command when the |
01c9630e80e0
commit https://github.com/vim/vim/commit/e99e84497b89e5f91df519790802770920ecf4fe
Christian Brabandt <cb@256bit.org>
parents:
9599
diff
changeset
|
86 '|' appears before {cmd}. This works: > |
01c9630e80e0
commit https://github.com/vim/vim/commit/e99e84497b89e5f91df519790802770920ecf4fe
Christian Brabandt <cb@256bit.org>
parents:
9599
diff
changeset
|
87 :augroup mine | au! BufRead | augroup END |
01c9630e80e0
commit https://github.com/vim/vim/commit/e99e84497b89e5f91df519790802770920ecf4fe
Christian Brabandt <cb@256bit.org>
parents:
9599
diff
changeset
|
88 But this sees "augroup" as part of the defined command: > |
12785 | 89 :augroup mine | au! BufRead * | augroup END |
9653
01c9630e80e0
commit https://github.com/vim/vim/commit/e99e84497b89e5f91df519790802770920ecf4fe
Christian Brabandt <cb@256bit.org>
parents:
9599
diff
changeset
|
90 :augroup mine | au BufRead * set tw=70 | augroup END |
12785 | 91 Instead you can put the group name into the command: > |
92 :au! mine BufRead * | |
93 :au mine BufRead * set tw=70 | |
94 Or use `:execute`: > | |
95 :augroup mine | exe "au! BufRead *" | augroup END | |
96 :augroup mine | exe "au BufRead * set tw=70" | augroup END | |
9653
01c9630e80e0
commit https://github.com/vim/vim/commit/e99e84497b89e5f91df519790802770920ecf4fe
Christian Brabandt <cb@256bit.org>
parents:
9599
diff
changeset
|
97 |
7 | 98 Note that special characters (e.g., "%", "<cword>") in the ":autocmd" |
99 arguments are not expanded when the autocommand is defined. These will be | |
100 expanded when the Event is recognized, and the {cmd} is executed. The only | |
101 exception is that "<sfile>" is expanded when the autocmd is defined. Example: | |
102 > | |
103 :au BufNewFile,BufRead *.html so <sfile>:h/html.vim | |
104 | |
105 Here Vim expands <sfile> to the name of the file containing this line. | |
106 | |
10244
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
107 `:autocmd` adds to the list of autocommands regardless of whether they are |
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
108 already present. When your .vimrc file is sourced twice, the autocommands |
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
109 will appear twice. To avoid this, define your autocommands in a group, so |
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
110 that you can easily clear them: > |
7 | 111 |
10244
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
112 augroup vimrc |
13482
9eebe457eb3c
Update runtime files. Convert a couple of help files to utf-8.
Christian Brabandt <cb@256bit.org>
parents:
13444
diff
changeset
|
113 " Remove all vimrc autocommands |
9eebe457eb3c
Update runtime files. Convert a couple of help files to utf-8.
Christian Brabandt <cb@256bit.org>
parents:
13444
diff
changeset
|
114 autocmd! |
10244
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
115 au BufNewFile,BufRead *.html so <sfile>:h/html.vim |
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
116 augroup END |
7 | 117 |
118 If you don't want to remove all autocommands, you can instead use a variable | |
119 to ensure that Vim includes the autocommands only once: > | |
120 | |
121 :if !exists("autocommands_loaded") | |
122 : let autocommands_loaded = 1 | |
123 : au ... | |
124 :endif | |
125 | |
126 When the [group] argument is not given, Vim uses the current group (as defined | |
127 with ":augroup"); otherwise, Vim uses the group defined with [group]. Note | |
128 that [group] must have been defined before. You cannot define a new group | |
129 with ":au group ..."; use ":augroup" for that. | |
130 | |
131 While testing autocommands, you might find the 'verbose' option to be useful: > | |
132 :set verbose=9 | |
133 This setting makes Vim echo the autocommands as it executes them. | |
134 | |
135 When defining an autocommand in a script, it will be able to call functions | |
136 local to the script and use mappings local to the script. When the event is | |
137 triggered and the command executed, it will run in the context of the script | |
138 it was defined in. This matters if |<SID>| is used in a command. | |
139 | |
1621 | 140 When executing the commands, the message from one command overwrites a |
7 | 141 previous message. This is different from when executing the commands |
142 manually. Mostly the screen will not scroll up, thus there is no hit-enter | |
143 prompt. When one command outputs two messages this can happen anyway. | |
144 | |
145 ============================================================================== | |
146 3. Removing autocommands *autocmd-remove* | |
147 | |
16217
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
148 :au[tocmd]! [group] {event} {pat} [++once] [++nested] {cmd} |
7 | 149 Remove all autocommands associated with {event} and |
16217
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
150 {pat}, and add the command {cmd}. |
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
151 See |autocmd-once| for [++once]. |
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
152 See |autocmd-nested| for [++nested]. |
7 | 153 |
154 :au[tocmd]! [group] {event} {pat} | |
155 Remove all autocommands associated with {event} and | |
156 {pat}. | |
157 | |
158 :au[tocmd]! [group] * {pat} | |
159 Remove all autocommands associated with {pat} for all | |
160 events. | |
161 | |
162 :au[tocmd]! [group] {event} | |
163 Remove ALL autocommands for {event}. | |
10244
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
164 Warning: You should not do this without a group for |
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
165 |BufRead| and other common events, it can break |
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
166 plugins, syntax highlighting, etc. |
7 | 167 |
168 :au[tocmd]! [group] Remove ALL autocommands. | |
13482
9eebe457eb3c
Update runtime files. Convert a couple of help files to utf-8.
Christian Brabandt <cb@256bit.org>
parents:
13444
diff
changeset
|
169 Note: a quote will be seen as argument to the :autocmd |
9eebe457eb3c
Update runtime files. Convert a couple of help files to utf-8.
Christian Brabandt <cb@256bit.org>
parents:
13444
diff
changeset
|
170 and won't start a comment. |
10244
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
171 Warning: You should normally not do this without a |
876fbdd84e52
commit https://github.com/vim/vim/commit/2ec618c9feac4573b154510236ad8121c77d0eca
Christian Brabandt <cb@256bit.org>
parents:
10218
diff
changeset
|
172 group, it breaks plugins, syntax highlighting, etc. |
7 | 173 |
174 When the [group] argument is not given, Vim uses the current group (as defined | |
175 with ":augroup"); otherwise, Vim uses the group defined with [group]. | |
176 | |
177 ============================================================================== | |
178 4. Listing autocommands *autocmd-list* | |
179 | |
180 :au[tocmd] [group] {event} {pat} | |
181 Show the autocommands associated with {event} and | |
182 {pat}. | |
183 | |
184 :au[tocmd] [group] * {pat} | |
185 Show the autocommands associated with {pat} for all | |
186 events. | |
187 | |
188 :au[tocmd] [group] {event} | |
189 Show all autocommands for {event}. | |
190 | |
191 :au[tocmd] [group] Show all autocommands. | |
192 | |
193 If you provide the [group] argument, Vim lists only the autocommands for | |
194 [group]; otherwise, Vim lists the autocommands for ALL groups. Note that this | |
195 argument behavior differs from that for defining and removing autocommands. | |
196 | |
40 | 197 In order to list buffer-local autocommands, use a pattern in the form <buffer> |
198 or <buffer=N>. See |autocmd-buflocal|. | |
199 | |
500 | 200 *:autocmd-verbose* |
201 When 'verbose' is non-zero, listing an autocommand will also display where it | |
202 was last defined. Example: > | |
203 | |
204 :verbose autocmd BufEnter | |
205 FileExplorer BufEnter | |
856 | 206 * call s:LocalBrowse(expand("<amatch>")) |
500 | 207 Last set from /usr/share/vim/vim-7.0/plugin/NetrwPlugin.vim |
208 < | |
209 See |:verbose-cmd| for more information. | |
210 | |
7 | 211 ============================================================================== |
212 5. Events *autocmd-events* *E215* *E216* | |
213 | |
579 | 214 You can specify a comma-separated list of event names. No white space can be |
215 used in this list. The command applies to all the events in the list. | |
216 | |
217 For READING FILES there are four kinds of events possible: | |
218 BufNewFile starting to edit a non-existent file | |
219 BufReadPre BufReadPost starting to edit an existing file | |
220 FilterReadPre FilterReadPost read the temp file with filter output | |
221 FileReadPre FileReadPost any other file read | |
222 Vim uses only one of these four kinds when reading a file. The "Pre" and | |
223 "Post" events are both triggered, before and after reading the file. | |
224 | |
225 Note that the autocommands for the *ReadPre events and all the Filter events | |
226 are not allowed to change the current buffer (you will get an error message if | |
227 this happens). This is to prevent the file to be read into the wrong buffer. | |
228 | |
229 Note that the 'modified' flag is reset AFTER executing the BufReadPost | |
230 and BufNewFile autocommands. But when the 'modified' option was set by the | |
231 autocommands, this doesn't happen. | |
232 | |
233 You can use the 'eventignore' option to ignore a number of events or all | |
234 events. | |
7 | 235 *autocommand-events* *{event}* |
236 Vim recognizes the following events. Vim ignores the case of event names | |
237 (e.g., you can use "BUFread" or "bufread" instead of "BufRead"). | |
238 | |
579 | 239 First an overview by function with a short explanation. Then the list |
843 | 240 alphabetically with full explanations |autocmd-events-abc|. |
579 | 241 |
242 Name triggered by ~ | |
243 | |
244 Reading | |
245 |BufNewFile| starting to edit a file that doesn't exist | |
246 |BufReadPre| starting to edit a new buffer, before reading the file | |
247 |BufRead| starting to edit a new buffer, after reading the file | |
248 |BufReadPost| starting to edit a new buffer, after reading the file | |
249 |BufReadCmd| before starting to edit a new buffer |Cmd-event| | |
250 | |
251 |FileReadPre| before reading a file with a ":read" command | |
252 |FileReadPost| after reading a file with a ":read" command | |
843 | 253 |FileReadCmd| before reading a file with a ":read" command |Cmd-event| |
579 | 254 |
255 |FilterReadPre| before reading a file from a filter command | |
256 |FilterReadPost| after reading a file from a filter command | |
257 | |
258 |StdinReadPre| before reading from stdin into the buffer | |
259 |StdinReadPost| After reading from the stdin into the buffer | |
260 | |
261 Writing | |
262 |BufWrite| starting to write the whole buffer to a file | |
263 |BufWritePre| starting to write the whole buffer to a file | |
264 |BufWritePost| after writing the whole buffer to a file | |
265 |BufWriteCmd| before writing the whole buffer to a file |Cmd-event| | |
266 | |
267 |FileWritePre| starting to write part of a buffer to a file | |
268 |FileWritePost| after writing part of a buffer to a file | |
269 |FileWriteCmd| before writing part of a buffer to a file |Cmd-event| | |
270 | |
271 |FileAppendPre| starting to append to a file | |
272 |FileAppendPost| after appending to a file | |
273 |FileAppendCmd| before appending to a file |Cmd-event| | |
274 | |
275 |FilterWritePre| starting to write a file for a filter command or diff | |
276 |FilterWritePost| after writing a file for a filter command or diff | |
277 | |
278 Buffers | |
279 |BufAdd| just after adding a buffer to the buffer list | |
280 |BufCreate| just after adding a buffer to the buffer list | |
281 |BufDelete| before deleting a buffer from the buffer list | |
282 |BufWipeout| before completely deleting a buffer | |
283 | |
284 |BufFilePre| before changing the name of the current buffer | |
285 |BufFilePost| after changing the name of the current buffer | |
286 | |
287 |BufEnter| after entering a buffer | |
288 |BufLeave| before leaving to another buffer | |
289 |BufWinEnter| after a buffer is displayed in a window | |
290 |BufWinLeave| before a buffer is removed from a window | |
291 | |
292 |BufUnload| before unloading a buffer | |
22723 | 293 |BufHidden| just before a buffer becomes hidden |
579 | 294 |BufNew| just after creating a new buffer |
295 | |
296 |SwapExists| detected an existing swap file | |
297 | |
298 Options | |
299 |FileType| when the 'filetype' option has been set | |
300 |Syntax| when the 'syntax' option has been set | |
301 |EncodingChanged| after the 'encoding' option has been changed | |
302 |TermChanged| after the value of 'term' has changed | |
6935 | 303 |OptionSet| after setting any option |
579 | 304 |
305 Startup and exit | |
306 |VimEnter| after doing all the startup stuff | |
307 |GUIEnter| after starting the GUI successfully | |
3830 | 308 |GUIFailed| after starting the GUI failed |
1154 | 309 |TermResponse| after the terminal response to |t_RV| is received |
579 | 310 |
13442
94e638936d3e
patch 8.0.1595: no autocommand triggered before exiting
Christian Brabandt <cb@256bit.org>
parents:
13437
diff
changeset
|
311 |QuitPre| when using `:quit`, before deciding whether to exit |
94e638936d3e
patch 8.0.1595: no autocommand triggered before exiting
Christian Brabandt <cb@256bit.org>
parents:
13437
diff
changeset
|
312 |ExitPre| when using a command that may make Vim exit |
579 | 313 |VimLeavePre| before exiting Vim, before writing the viminfo file |
314 |VimLeave| before exiting Vim, after writing the viminfo file | |
315 | |
23165
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
316 |VimSuspend| when suspending Vim |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
317 |VimResume| when Vim is resumed after being suspended |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
318 |
18450
507348b211b4
patch 8.1.2219: no autocommand for open window with terminal
Bram Moolenaar <Bram@vim.org>
parents:
18130
diff
changeset
|
319 Terminal |
507348b211b4
patch 8.1.2219: no autocommand for open window with terminal
Bram Moolenaar <Bram@vim.org>
parents:
18130
diff
changeset
|
320 |TerminalOpen| after a terminal buffer was created |
507348b211b4
patch 8.1.2219: no autocommand for open window with terminal
Bram Moolenaar <Bram@vim.org>
parents:
18130
diff
changeset
|
321 |TerminalWinOpen| after a terminal buffer was created in a new window |
507348b211b4
patch 8.1.2219: no autocommand for open window with terminal
Bram Moolenaar <Bram@vim.org>
parents:
18130
diff
changeset
|
322 |
579 | 323 Various |
324 |FileChangedShell| Vim notices that a file changed since editing started | |
766 | 325 |FileChangedShellPost| After handling a file changed since editing started |
579 | 326 |FileChangedRO| before making the first change to a read-only file |
327 | |
14945 | 328 |DiffUpdated| after diffs have been updated |
13170
6559e98f3e74
patch 8.0.1459: cannot handle change of directory
Christian Brabandt <cb@256bit.org>
parents:
13142
diff
changeset
|
329 |DirChanged| after the working directory has changed |
6559e98f3e74
patch 8.0.1459: cannot handle change of directory
Christian Brabandt <cb@256bit.org>
parents:
13142
diff
changeset
|
330 |
724 | 331 |ShellCmdPost| after executing a shell command |
332 |ShellFilterPost| after filtering with a shell command | |
333 | |
6154 | 334 |CmdUndefined| a user command is used but it isn't defined |
579 | 335 |FuncUndefined| a user function is used but it isn't defined |
650 | 336 |SpellFileMissing| a spell file is used but it can't be found |
716 | 337 |SourcePre| before sourcing a Vim script |
15640 | 338 |SourcePost| after sourcing a Vim script |
1061 | 339 |SourceCmd| before sourcing a Vim script |Cmd-event| |
579 | 340 |
766 | 341 |VimResized| after the Vim window size changed |
579 | 342 |FocusGained| Vim got input focus |
343 |FocusLost| Vim lost input focus | |
344 |CursorHold| the user doesn't press a key for a while | |
661 | 345 |CursorHoldI| the user doesn't press a key for a while in Insert mode |
346 |CursorMoved| the cursor was moved in Normal mode | |
347 |CursorMovedI| the cursor was moved in Insert mode | |
579 | 348 |
9595
0190d5de215f
commit https://github.com/vim/vim/commit/c917da4b3e8801a255dbefea8e4ed19c1c716dd8
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
349 |WinNew| after creating a new window |
9599
42a8a81decdf
commit https://github.com/vim/vim/commit/12c11d553053f5a9eae9eb3c518279b12fa928c2
Christian Brabandt <cb@256bit.org>
parents:
9595
diff
changeset
|
350 |TabNew| after creating a new tab page |
42a8a81decdf
commit https://github.com/vim/vim/commit/12c11d553053f5a9eae9eb3c518279b12fa928c2
Christian Brabandt <cb@256bit.org>
parents:
9595
diff
changeset
|
351 |TabClosed| after closing a tab page |
579 | 352 |WinEnter| after entering another window |
353 |WinLeave| before leaving a window | |
677 | 354 |TabEnter| after entering another tab page |
355 |TabLeave| before leaving a tab page | |
579 | 356 |CmdwinEnter| after entering the command-line window |
357 |CmdwinLeave| before leaving the command-line window | |
358 | |
13437 | 359 |CmdlineChanged| after a change was made to the command-line text |
360 |CmdlineEnter| after the cursor moves to the command line | |
361 |CmdlineLeave| before the cursor leaves the command line | |
362 | |
579 | 363 |InsertEnter| starting Insert mode |
364 |InsertChange| when typing <Insert> while in Insert or Replace mode | |
365 |InsertLeave| when leaving Insert mode | |
2845 | 366 |InsertCharPre| when a character was typed in Insert mode, before |
367 inserting it | |
579 | 368 |
25790
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
369 |ModeChanged| after changing the mode |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
370 |
5555 | 371 |TextChanged| after a change was made to the text in Normal mode |
372 |TextChangedI| after a change was made to the text in Insert mode | |
13240
5ed6e4a25925
patch 8.0.1494: no autocmd triggered in Insert mode with visible popup menu
Christian Brabandt <cb@256bit.org>
parents:
13231
diff
changeset
|
373 when popup menu is not visible |
5ed6e4a25925
patch 8.0.1494: no autocmd triggered in Insert mode with visible popup menu
Christian Brabandt <cb@256bit.org>
parents:
13231
diff
changeset
|
374 |TextChangedP| after a change was made to the text in Insert mode |
5ed6e4a25925
patch 8.0.1494: no autocmd triggered in Insert mode with visible popup menu
Christian Brabandt <cb@256bit.org>
parents:
13231
diff
changeset
|
375 when popup menu visible |
14347 | 376 |TextYankPost| after text has been yanked or deleted |
5555 | 377 |
18098
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
378 |SafeState| nothing pending, going to wait for the user to type a |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
379 character |
18102
0d9ec3a2821f
patch 8.1.2046: SafeState may be triggered at the wrong moment
Bram Moolenaar <Bram@vim.org>
parents:
18098
diff
changeset
|
380 |SafeStateAgain| repeated SafeState |
18098
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
381 |
13818
28ac7914b2b6
Update runtime files and translations
Christian Brabandt <cb@256bit.org>
parents:
13735
diff
changeset
|
382 |ColorSchemePre| before loading a color scheme |
579 | 383 |ColorScheme| after loading a color scheme |
384 | |
385 |RemoteReply| a reply from a server Vim was received | |
386 | |
387 |QuickFixCmdPre| before a quickfix command is run | |
388 |QuickFixCmdPost| after a quickfix command is run | |
389 | |
390 |SessionLoadPost| after loading a session file | |
391 | |
392 |MenuPopup| just before showing the popup menu | |
16268
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
393 |CompleteChanged| after Insert mode completion menu changed |
19199
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
394 |CompleteDonePre| after Insert mode completion is done, before clearing |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
395 info |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
396 |CompleteDone| after Insert mode completion is done, after clearing |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
397 info |
579 | 398 |
399 |User| to be used in combination with ":doautocmd" | |
20800
e76b83c07bd8
patch 8.2.0952: no simple way to interrupt Vim
Bram Moolenaar <Bram@vim.org>
parents:
19303
diff
changeset
|
400 |SigUSR1| after the SIGUSR1 signal has been detected |
579 | 401 |
402 | |
403 The alphabetical list of autocommand events: *autocmd-events-abc* | |
404 | |
405 *BufCreate* *BufAdd* | |
406 BufAdd or BufCreate Just after creating a new buffer which is | |
407 added to the buffer list, or adding a buffer | |
408 to the buffer list. | |
409 Also used just after a buffer in the buffer | |
410 list has been renamed. | |
18878
ef90e5bbb971
Minor runtime file updates.
Bram Moolenaar <Bram@vim.org>
parents:
18450
diff
changeset
|
411 Not triggered for the initial buffers created |
ef90e5bbb971
Minor runtime file updates.
Bram Moolenaar <Bram@vim.org>
parents:
18450
diff
changeset
|
412 during startup. |
579 | 413 The BufCreate event is for historic reasons. |
414 NOTE: When this autocommand is executed, the | |
415 current buffer "%" may be different from the | |
416 buffer being created "<afile>". | |
417 *BufDelete* | |
418 BufDelete Before deleting a buffer from the buffer list. | |
419 The BufUnload may be called first (if the | |
420 buffer was loaded). | |
421 Also used just before a buffer in the buffer | |
422 list is renamed. | |
423 NOTE: When this autocommand is executed, the | |
424 current buffer "%" may be different from the | |
1621 | 425 buffer being deleted "<afile>" and "<abuf>". |
1919 | 426 Don't change to another buffer, it will cause |
427 problems. | |
579 | 428 *BufEnter* |
429 BufEnter After entering a buffer. Useful for setting | |
430 options for a file type. Also executed when | |
431 starting to edit a buffer, after the | |
432 BufReadPost autocommands. | |
433 *BufFilePost* | |
434 BufFilePost After changing the name of the current buffer | |
435 with the ":file" or ":saveas" command. | |
625 | 436 *BufFilePre* |
579 | 437 BufFilePre Before changing the name of the current buffer |
438 with the ":file" or ":saveas" command. | |
439 *BufHidden* | |
17261 | 440 BufHidden Just before a buffer becomes hidden. That is, |
441 when there are no longer windows that show | |
579 | 442 the buffer, but the buffer is not unloaded or |
443 deleted. Not used for ":qa" or ":q" when | |
444 exiting Vim. | |
445 NOTE: When this autocommand is executed, the | |
446 current buffer "%" may be different from the | |
447 buffer being unloaded "<afile>". | |
448 *BufLeave* | |
449 BufLeave Before leaving to another buffer. Also when | |
450 leaving or closing the current window and the | |
451 new current window is not for the same buffer. | |
452 Not used for ":qa" or ":q" when exiting Vim. | |
453 *BufNew* | |
454 BufNew Just after creating a new buffer. Also used | |
455 just after a buffer has been renamed. When | |
456 the buffer is added to the buffer list BufAdd | |
457 will be triggered too. | |
458 NOTE: When this autocommand is executed, the | |
459 current buffer "%" may be different from the | |
460 buffer being created "<afile>". | |
7 | 461 *BufNewFile* |
462 BufNewFile When starting to edit a file that doesn't | |
463 exist. Can be used to read in a skeleton | |
464 file. | |
465 *BufRead* *BufReadPost* | |
466 BufRead or BufReadPost When starting to edit a new buffer, after | |
467 reading the file into the buffer, before | |
468 executing the modelines. See |BufWinEnter| | |
469 for when you need to do something after | |
470 processing the modelines. | |
471 This does NOT work for ":r file". Not used | |
472 when the file doesn't exist. Also used after | |
473 successfully recovering a file. | |
3682 | 474 Also triggered for the filetypedetect group |
475 when executing ":filetype detect" and when | |
476 writing an unnamed buffer in a way that the | |
477 buffer gets a name. | |
625 | 478 *BufReadCmd* |
7 | 479 BufReadCmd Before starting to edit a new buffer. Should |
480 read the file into the buffer. |Cmd-event| | |
625 | 481 *BufReadPre* *E200* *E201* |
579 | 482 BufReadPre When starting to edit a new buffer, before |
483 reading the file into the buffer. Not used | |
484 if the file doesn't exist. | |
485 *BufUnload* | |
486 BufUnload Before unloading a buffer. This is when the | |
487 text in the buffer is going to be freed. This | |
488 may be after a BufWritePost and before a | |
489 BufDelete. Also used for all buffers that are | |
490 loaded when Vim is going to exit. | |
491 NOTE: When this autocommand is executed, the | |
492 current buffer "%" may be different from the | |
493 buffer being unloaded "<afile>". | |
10140
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
494 Don't change to another buffer or window, it |
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
495 will cause problems! |
2226
36a9ac99e1ca
Don't execute some autocommands when v:dying is 2 or more.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
496 When exiting and v:dying is 2 or more this |
36a9ac99e1ca
Don't execute some autocommands when v:dying is 2 or more.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
497 event is not triggered. |
579 | 498 *BufWinEnter* |
499 BufWinEnter After a buffer is displayed in a window. This | |
500 can be when the buffer is loaded (after | |
1621 | 501 processing the modelines) or when a hidden |
579 | 502 buffer is displayed in a window (and is no |
1621 | 503 longer hidden). |
504 Does not happen for |:split| without | |
505 arguments, since you keep editing the same | |
506 buffer, or ":split" with a file that's already | |
1668 | 507 open in a window, because it re-uses an |
508 existing buffer. But it does happen for a | |
509 ":split" with the name of the current buffer, | |
510 since it reloads that buffer. | |
13835
8e583c52eb44
patch 8.0.1789: BufWinEnter does not work well for a terminal window
Christian Brabandt <cb@256bit.org>
parents:
13818
diff
changeset
|
511 Does not happen for a terminal window, because |
8e583c52eb44
patch 8.0.1789: BufWinEnter does not work well for a terminal window
Christian Brabandt <cb@256bit.org>
parents:
13818
diff
changeset
|
512 it starts in Terminal-Job mode and Normal mode |
8e583c52eb44
patch 8.0.1789: BufWinEnter does not work well for a terminal window
Christian Brabandt <cb@256bit.org>
parents:
13818
diff
changeset
|
513 commands won't work. Use |TerminalOpen| instead. |
579 | 514 *BufWinLeave* |
515 BufWinLeave Before a buffer is removed from a window. | |
516 Not when it's still visible in another window. | |
517 Also triggered when exiting. It's triggered | |
518 before BufUnload or BufHidden. | |
519 NOTE: When this autocommand is executed, the | |
520 current buffer "%" may be different from the | |
521 buffer being unloaded "<afile>". | |
2226
36a9ac99e1ca
Don't execute some autocommands when v:dying is 2 or more.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
522 When exiting and v:dying is 2 or more this |
36a9ac99e1ca
Don't execute some autocommands when v:dying is 2 or more.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
523 event is not triggered. |
579 | 524 *BufWipeout* |
525 BufWipeout Before completely deleting a buffer. The | |
526 BufUnload and BufDelete events may be called | |
527 first (if the buffer was loaded and was in the | |
528 buffer list). Also used just before a buffer | |
529 is renamed (also when it's not in the buffer | |
530 list). | |
531 NOTE: When this autocommand is executed, the | |
532 current buffer "%" may be different from the | |
533 buffer being deleted "<afile>". | |
1919 | 534 Don't change to another buffer, it will cause |
535 problems. | |
7 | 536 *BufWrite* *BufWritePre* |
537 BufWrite or BufWritePre Before writing the whole buffer to a file. | |
538 *BufWriteCmd* | |
539 BufWriteCmd Before writing the whole buffer to a file. | |
540 Should do the writing of the file and reset | |
39 | 541 'modified' if successful, unless '+' is in |
542 'cpo' and writing to another file |cpo-+|. | |
543 The buffer contents should not be changed. | |
3082 | 544 When the command resets 'modified' the undo |
545 information is adjusted to mark older undo | |
546 states as 'modified', like |:write| does. | |
39 | 547 |Cmd-event| |
579 | 548 *BufWritePost* |
549 BufWritePost After writing the whole buffer to a file | |
550 (should undo the commands for BufWritePre). | |
6154 | 551 *CmdUndefined* |
552 CmdUndefined When a user command is used but it isn't | |
553 defined. Useful for defining a command only | |
554 when it's used. The pattern is matched | |
555 against the command name. Both <amatch> and | |
556 <afile> are set to the name of the command. | |
557 NOTE: Autocompletion won't work until the | |
558 command is defined. An alternative is to | |
559 always define the user command and have it | |
560 invoke an autoloaded function. See |autoload|. | |
13142
59a16624400a
patch 8.0.1445: cannot act on edits in the command line
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
561 *CmdlineChanged* |
13437 | 562 CmdlineChanged After a change was made to the text in the |
563 command line. Be careful not to mess up | |
564 the command line, it may cause Vim to lock up. | |
13142
59a16624400a
patch 8.0.1445: cannot act on edits in the command line
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
565 <afile> is set to a single character, |
59a16624400a
patch 8.0.1445: cannot act on edits in the command line
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
566 indicating the type of command-line. |
59a16624400a
patch 8.0.1445: cannot act on edits in the command line
Christian Brabandt <cb@256bit.org>
parents:
13051
diff
changeset
|
567 |cmdwin-char| |
12656
0a9dacb8826a
patch 8.0.1206: no autocmd for entering or leaving the command line
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
568 *CmdlineEnter* |
0a9dacb8826a
patch 8.0.1206: no autocmd for entering or leaving the command line
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
569 CmdlineEnter After moving the cursor to the command line, |
0a9dacb8826a
patch 8.0.1206: no autocmd for entering or leaving the command line
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
570 where the user can type a command or search |
22862
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22723
diff
changeset
|
571 string; including non-interactive use of ":" |
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22723
diff
changeset
|
572 in a mapping, but not when using |<Cmd>|. |
12656
0a9dacb8826a
patch 8.0.1206: no autocmd for entering or leaving the command line
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
573 <afile> is set to a single character, |
0a9dacb8826a
patch 8.0.1206: no autocmd for entering or leaving the command line
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
574 indicating the type of command-line. |
0a9dacb8826a
patch 8.0.1206: no autocmd for entering or leaving the command line
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
575 |cmdwin-char| |
0a9dacb8826a
patch 8.0.1206: no autocmd for entering or leaving the command line
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
576 *CmdlineLeave* |
22862
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22723
diff
changeset
|
577 CmdlineLeave Before leaving the command line; including |
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22723
diff
changeset
|
578 non-interactive use of ":" in a mapping, but |
6d50182e7e24
patch 8.2.1978: making a mapping work in all modes is complicated
Bram Moolenaar <Bram@vim.org>
parents:
22723
diff
changeset
|
579 not when using |<Cmd>|. |
12756
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
12656
diff
changeset
|
580 Also when abandoning the command line, after |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
12656
diff
changeset
|
581 typing CTRL-C or <Esc>. |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
12656
diff
changeset
|
582 When the commands result in an error the |
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
12656
diff
changeset
|
583 command line is still executed. |
12656
0a9dacb8826a
patch 8.0.1206: no autocmd for entering or leaving the command line
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
584 <afile> is set to a single character, |
0a9dacb8826a
patch 8.0.1206: no autocmd for entering or leaving the command line
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
585 indicating the type of command-line. |
0a9dacb8826a
patch 8.0.1206: no autocmd for entering or leaving the command line
Christian Brabandt <cb@256bit.org>
parents:
11659
diff
changeset
|
586 |cmdwin-char| |
579 | 587 *CmdwinEnter* |
588 CmdwinEnter After entering the command-line window. | |
589 Useful for setting options specifically for | |
18043
5a0d5f8e1778
patch 8.1.2017: cannot execute commands after closing the cmdline window
Bram Moolenaar <Bram@vim.org>
parents:
17756
diff
changeset
|
590 this special type of window. |
579 | 591 <afile> is set to a single character, |
592 indicating the type of command-line. | |
593 |cmdwin-char| | |
594 *CmdwinLeave* | |
595 CmdwinLeave Before leaving the command-line window. | |
596 Useful to clean up any global setting done | |
18043
5a0d5f8e1778
patch 8.1.2017: cannot execute commands after closing the cmdline window
Bram Moolenaar <Bram@vim.org>
parents:
17756
diff
changeset
|
597 with CmdwinEnter. |
579 | 598 <afile> is set to a single character, |
599 indicating the type of command-line. | |
600 |cmdwin-char| | |
601 *ColorScheme* | |
602 ColorScheme After loading a color scheme. |:colorscheme| | |
5521 | 603 The pattern is matched against the |
604 colorscheme name. <afile> can be used for the | |
605 name of the actual file where this option was | |
606 set, and <amatch> for the new colorscheme | |
607 name. | |
608 | |
13818
28ac7914b2b6
Update runtime files and translations
Christian Brabandt <cb@256bit.org>
parents:
13735
diff
changeset
|
609 *ColorSchemePre* |
28ac7914b2b6
Update runtime files and translations
Christian Brabandt <cb@256bit.org>
parents:
13735
diff
changeset
|
610 ColorSchemePre Before loading a color scheme. |:colorscheme| |
28ac7914b2b6
Update runtime files and translations
Christian Brabandt <cb@256bit.org>
parents:
13735
diff
changeset
|
611 Useful to setup removing things added by a |
28ac7914b2b6
Update runtime files and translations
Christian Brabandt <cb@256bit.org>
parents:
13735
diff
changeset
|
612 color scheme, before another one is loaded. |
18130 | 613 CompleteChanged *CompleteChanged* |
16268
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
614 After each time the Insert mode completion |
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
615 menu changed. Not fired on popup menu hide, |
19199
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
616 use |CompleteDonePre| or |CompleteDone| for |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
617 that. Never triggered recursively. |
661 | 618 |
16268
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
619 Sets these |v:event| keys: |
16380 | 620 completed_item See |complete-items|. |
16268
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
621 height nr of items visible |
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
622 width screen cells |
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
623 row top screen row |
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
624 col leftmost screen column |
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
625 size total nr of items |
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
626 scrollbar TRUE if visible |
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
627 |
0f65f2808470
patch 8.1.1138: plugins don't get notified when the popup menu changes
Bram Moolenaar <Bram@vim.org>
parents:
16217
diff
changeset
|
628 It is not allowed to change the text |textlock|. |
17756
a7afcea6f40a
patch 8.1.1875: cannot get size and position of the popup menu
Bram Moolenaar <Bram@vim.org>
parents:
17261
diff
changeset
|
629 |
a7afcea6f40a
patch 8.1.1875: cannot get size and position of the popup menu
Bram Moolenaar <Bram@vim.org>
parents:
17261
diff
changeset
|
630 The size and position of the popup are also |
a7afcea6f40a
patch 8.1.1875: cannot get size and position of the popup menu
Bram Moolenaar <Bram@vim.org>
parents:
17261
diff
changeset
|
631 available by calling |pum_getpos()|. |
a7afcea6f40a
patch 8.1.1875: cannot get size and position of the popup menu
Bram Moolenaar <Bram@vim.org>
parents:
17261
diff
changeset
|
632 |
19199
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
633 *CompleteDonePre* |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
634 CompleteDonePre After Insert mode completion is done. Either |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
635 when something was completed or abandoning |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
636 completion. |ins-completion| |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
637 |complete_info()| can be used, the info is |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
638 cleared after triggering CompleteDonePre. |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
639 The |v:completed_item| variable contains |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
640 information about the completed item. |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
641 |
3682 | 642 *CompleteDone* |
643 CompleteDone After Insert mode completion is done. Either | |
644 when something was completed or abandoning | |
645 completion. |ins-completion| | |
19199
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
646 |complete_info()| cannot be used, the info is |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
647 cleared before triggering CompleteDone. Use |
8cbadf7fb9d4
patch 8.2.0158: triggering CompleteDone earlier is not backwards compatible
Bram Moolenaar <Bram@vim.org>
parents:
19127
diff
changeset
|
648 CompleteDonePre if you need it. |
6909 | 649 The |v:completed_item| variable contains |
650 information about the completed item. | |
3682 | 651 |
579 | 652 *CursorHold* |
653 CursorHold When the user doesn't press a key for the time | |
22441 | 654 specified with 'updatetime'. Not triggered |
579 | 655 until the user has pressed a key (i.e. doesn't |
656 fire every 'updatetime' ms if you leave Vim to | |
657 make some coffee. :) See |CursorHold-example| | |
658 for previewing tags. | |
659 This event is only triggered in Normal mode. | |
1154 | 660 It is not triggered when waiting for a command |
661 argument to be typed, or a movement after an | |
662 operator. | |
610 | 663 While recording the CursorHold event is not |
664 triggered. |q| | |
6259 | 665 *<CursorHold>* |
666 Internally the autocommand is triggered by the | |
667 <CursorHold> key. In an expression mapping | |
668 |getchar()| may see this character. | |
669 | |
579 | 670 Note: Interactive commands cannot be used for |
671 this event. There is no hit-enter prompt, | |
672 the screen is updated directly (when needed). | |
673 Note: In the future there will probably be | |
674 another option to set the time. | |
675 Hint: to force an update of the status lines | |
676 use: > | |
677 :let &ro = &ro | |
18972 | 678 < {only on Amiga, Unix, Win32 and all GUI |
579 | 679 versions} |
661 | 680 *CursorHoldI* |
681 CursorHoldI Just like CursorHold, but in Insert mode. | |
8951
0bdeaf7092bc
commit https://github.com/vim/vim/commit/aa3b15dbebf333282503d6031e2f9ba6ee4398ed
Christian Brabandt <cb@256bit.org>
parents:
8748
diff
changeset
|
682 Not triggered when waiting for another key, |
0bdeaf7092bc
commit https://github.com/vim/vim/commit/aa3b15dbebf333282503d6031e2f9ba6ee4398ed
Christian Brabandt <cb@256bit.org>
parents:
8748
diff
changeset
|
683 e.g. after CTRL-V, and not when in CTRL-X mode |
0bdeaf7092bc
commit https://github.com/vim/vim/commit/aa3b15dbebf333282503d6031e2f9ba6ee4398ed
Christian Brabandt <cb@256bit.org>
parents:
8748
diff
changeset
|
684 |insert_expand|. |
661 | 685 |
686 *CursorMoved* | |
4911 | 687 CursorMoved After the cursor was moved in Normal or Visual |
688 mode. Also when the text of the cursor line | |
689 has been changed, e.g., with "x", "rx" or "p". | |
25402 | 690 Not triggered when there is typeahead, while |
691 executing commands in a script file, when | |
25161 | 692 an operator is pending or when moving to |
693 another window while remaining at the same | |
694 cursor position. | |
667 | 695 For an example see |match-parens|. |
16023 | 696 Note: This can not be skipped with |
697 `:noautocmd`. | |
4264 | 698 Careful: This is triggered very often, don't |
699 do anything that the user does not expect or | |
700 that is slow. | |
661 | 701 *CursorMovedI* |
702 CursorMovedI After the cursor was moved in Insert mode. | |
3082 | 703 Not triggered when the popup menu is visible. |
661 | 704 Otherwise the same as CursorMoved. |
579 | 705 *EncodingChanged* |
706 EncodingChanged Fires off after the 'encoding' option has been | |
707 changed. Useful to set up fonts, for example. | |
7 | 708 *FileAppendCmd* |
709 FileAppendCmd Before appending to a file. Should do the | |
26 | 710 appending to the file. Use the '[ and '] |
25973 | 711 marks for the range of lines. |Cmd-event| |
579 | 712 *FileAppendPost* |
713 FileAppendPost After appending to a file. | |
714 *FileAppendPre* | |
715 FileAppendPre Before appending to a file. Use the '[ and '] | |
716 marks for the range of lines. | |
717 *FileChangedRO* | |
718 FileChangedRO Before making the first change to a read-only | |
719 file. Can be used to check-out the file from | |
720 a source control system. Not triggered when | |
721 the change was caused by an autocommand. | |
722 This event is triggered when making the first | |
723 change in a buffer or the first change after | |
823 | 724 'readonly' was set, just before the change is |
725 applied to the text. | |
579 | 726 WARNING: If the autocommand moves the cursor |
727 the effect of the change is undefined. | |
819 | 728 *E788* |
729 It is not allowed to change to another buffer | |
730 here. You can reload the buffer but not edit | |
731 another one. | |
5663
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5555
diff
changeset
|
732 *E881* |
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5555
diff
changeset
|
733 If the number of lines changes saving for undo |
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5555
diff
changeset
|
734 may fail and the change will be aborted. |
14770
27055ad9276b
patch 8.1.0397: no event triggered after updating diffs
Christian Brabandt <cb@256bit.org>
parents:
14519
diff
changeset
|
735 *DiffUpdated* |
27055ad9276b
patch 8.1.0397: no event triggered after updating diffs
Christian Brabandt <cb@256bit.org>
parents:
14519
diff
changeset
|
736 DiffUpdated After diffs have been updated. Depending on |
27055ad9276b
patch 8.1.0397: no event triggered after updating diffs
Christian Brabandt <cb@256bit.org>
parents:
14519
diff
changeset
|
737 what kind of diff is being used (internal or |
27055ad9276b
patch 8.1.0397: no event triggered after updating diffs
Christian Brabandt <cb@256bit.org>
parents:
14519
diff
changeset
|
738 external) this can be triggered on every |
27055ad9276b
patch 8.1.0397: no event triggered after updating diffs
Christian Brabandt <cb@256bit.org>
parents:
14519
diff
changeset
|
739 change or when doing |:diffupdate|. |
13170
6559e98f3e74
patch 8.0.1459: cannot handle change of directory
Christian Brabandt <cb@256bit.org>
parents:
13142
diff
changeset
|
740 *DirChanged* |
6559e98f3e74
patch 8.0.1459: cannot handle change of directory
Christian Brabandt <cb@256bit.org>
parents:
13142
diff
changeset
|
741 DirChanged The working directory has changed in response |
16427
8c3a1bd270bb
patch 8.1.1218: cannot set a directory for a tab page
Bram Moolenaar <Bram@vim.org>
parents:
16380
diff
changeset
|
742 to the |:cd| or |:tcd| or |:lcd| commands, or |
8c3a1bd270bb
patch 8.1.1218: cannot set a directory for a tab page
Bram Moolenaar <Bram@vim.org>
parents:
16380
diff
changeset
|
743 as a result of the 'autochdir' option. |
13170
6559e98f3e74
patch 8.0.1459: cannot handle change of directory
Christian Brabandt <cb@256bit.org>
parents:
13142
diff
changeset
|
744 The pattern can be: |
16427
8c3a1bd270bb
patch 8.1.1218: cannot set a directory for a tab page
Bram Moolenaar <Bram@vim.org>
parents:
16380
diff
changeset
|
745 "window" to trigger on `:lcd` |
8c3a1bd270bb
patch 8.1.1218: cannot set a directory for a tab page
Bram Moolenaar <Bram@vim.org>
parents:
16380
diff
changeset
|
746 "tabpage" to trigger on `:tcd` |
8c3a1bd270bb
patch 8.1.1218: cannot set a directory for a tab page
Bram Moolenaar <Bram@vim.org>
parents:
16380
diff
changeset
|
747 "global" to trigger on `:cd` |
8c3a1bd270bb
patch 8.1.1218: cannot set a directory for a tab page
Bram Moolenaar <Bram@vim.org>
parents:
16380
diff
changeset
|
748 "auto" to trigger on 'autochdir'. |
8c3a1bd270bb
patch 8.1.1218: cannot set a directory for a tab page
Bram Moolenaar <Bram@vim.org>
parents:
16380
diff
changeset
|
749 "drop" to trigger on editing a file |
13170
6559e98f3e74
patch 8.0.1459: cannot handle change of directory
Christian Brabandt <cb@256bit.org>
parents:
13142
diff
changeset
|
750 <afile> is set to the new directory name. |
13442
94e638936d3e
patch 8.0.1595: no autocommand triggered before exiting
Christian Brabandt <cb@256bit.org>
parents:
13437
diff
changeset
|
751 *ExitPre* |
94e638936d3e
patch 8.0.1595: no autocommand triggered before exiting
Christian Brabandt <cb@256bit.org>
parents:
13437
diff
changeset
|
752 ExitPre When using `:quit`, `:wq` in a way it makes |
94e638936d3e
patch 8.0.1595: no autocommand triggered before exiting
Christian Brabandt <cb@256bit.org>
parents:
13437
diff
changeset
|
753 Vim exit, or using `:qall`, just after |
94e638936d3e
patch 8.0.1595: no autocommand triggered before exiting
Christian Brabandt <cb@256bit.org>
parents:
13437
diff
changeset
|
754 |QuitPre|. Can be used to close any |
14123 | 755 non-essential window. Exiting may still be |
756 cancelled if there is a modified buffer that | |
757 isn't automatically saved, use |VimLeavePre| | |
758 for really exiting. | |
7 | 759 *FileChangedShell* |
760 FileChangedShell When Vim notices that the modification time of | |
761 a file has changed since editing started. | |
762 Also when the file attributes of the file | |
5908 | 763 change or when the size of the file changes. |
764 |timestamp| | |
7 | 765 Mostly triggered after executing a shell |
766 command, but also with a |:checktime| command | |
11473 | 767 or when gvim regains input focus. |
7 | 768 This autocommand is triggered for each changed |
769 file. It is not used when 'autoread' is set | |
770 and the buffer was not changed. If a | |
771 FileChangedShell autocommand is present the | |
772 warning message and prompt is not given. | |
179 | 773 The |v:fcs_reason| variable is set to indicate |
774 what happened and |v:fcs_choice| can be used | |
775 to tell Vim what to do next. | |
7 | 776 NOTE: When this autocommand is executed, the |
777 current buffer "%" may be different from the | |
11347 | 778 buffer that was changed, which is in "<afile>". |
7 | 779 NOTE: The commands must not change the current |
780 buffer, jump to another buffer or delete a | |
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1919
diff
changeset
|
781 buffer. *E246* *E811* |
7 | 782 NOTE: This event never nests, to avoid an |
783 endless loop. This means that while executing | |
784 commands for the FileChangedShell event no | |
785 other FileChangedShell event will be | |
786 triggered. | |
766 | 787 *FileChangedShellPost* |
788 FileChangedShellPost After handling a file that was changed outside | |
789 of Vim. Can be used to update the statusline. | |
579 | 790 *FileEncoding* |
791 FileEncoding Obsolete. It still works and is equivalent | |
792 to |EncodingChanged|. | |
793 *FileReadCmd* | |
794 FileReadCmd Before reading a file with a ":read" command. | |
795 Should do the reading of the file. |Cmd-event| | |
796 *FileReadPost* | |
797 FileReadPost After reading a file with a ":read" command. | |
798 Note that Vim sets the '[ and '] marks to the | |
799 first and last line of the read. This can be | |
800 used to operate on the lines just read. | |
801 *FileReadPre* | |
802 FileReadPre Before reading a file with a ":read" command. | |
803 *FileType* | |
1154 | 804 FileType When the 'filetype' option has been set. The |
805 pattern is matched against the filetype. | |
579 | 806 <afile> can be used for the name of the file |
807 where this option was set, and <amatch> for | |
11659
49c12c93abf3
Updated runtime files and translations.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
808 the new value of 'filetype'. Navigating to |
49c12c93abf3
Updated runtime files and translations.
Christian Brabandt <cb@256bit.org>
parents:
11473
diff
changeset
|
809 another window or buffer is not allowed. |
579 | 810 See |filetypes|. |
811 *FileWriteCmd* | |
812 FileWriteCmd Before writing to a file, when not writing the | |
813 whole buffer. Should do the writing to the | |
814 file. Should not change the buffer. Use the | |
815 '[ and '] marks for the range of lines. | |
816 |Cmd-event| | |
817 *FileWritePost* | |
818 FileWritePost After writing to a file, when not writing the | |
819 whole buffer. | |
820 *FileWritePre* | |
821 FileWritePre Before writing to a file, when not writing the | |
822 whole buffer. Use the '[ and '] marks for the | |
823 range of lines. | |
824 *FilterReadPost* | |
825 FilterReadPost After reading a file from a filter command. | |
826 Vim checks the pattern against the name of | |
827 the current buffer as with FilterReadPre. | |
828 Not triggered when 'shelltemp' is off. | |
829 *FilterReadPre* *E135* | |
830 FilterReadPre Before reading a file from a filter command. | |
831 Vim checks the pattern against the name of | |
832 the current buffer, not the name of the | |
833 temporary file that is the output of the | |
834 filter command. | |
835 Not triggered when 'shelltemp' is off. | |
836 *FilterWritePost* | |
837 FilterWritePost After writing a file for a filter command or | |
15334 | 838 making a diff with an external diff (see |
25973 | 839 |DiffUpdated| for internal diff). |
579 | 840 Vim checks the pattern against the name of |
841 the current buffer as with FilterWritePre. | |
842 Not triggered when 'shelltemp' is off. | |
843 *FilterWritePre* | |
844 FilterWritePre Before writing a file for a filter command or | |
15334 | 845 making a diff with an external diff. |
579 | 846 Vim checks the pattern against the name of |
847 the current buffer, not the name of the | |
848 temporary file that is the output of the | |
849 filter command. | |
850 Not triggered when 'shelltemp' is off. | |
7 | 851 *FocusGained* |
852 FocusGained When Vim got input focus. Only for the GUI | |
853 version and a few console versions where this | |
854 can be detected. | |
855 *FocusLost* | |
856 FocusLost When Vim lost input focus. Only for the GUI | |
857 version and a few console versions where this | |
11 | 858 can be detected. May also happen when a |
859 dialog pops up. | |
7 | 860 *FuncUndefined* |
861 FuncUndefined When a user function is used but it isn't | |
862 defined. Useful for defining a function only | |
1154 | 863 when it's used. The pattern is matched |
864 against the function name. Both <amatch> and | |
865 <afile> are set to the name of the function. | |
23305 | 866 Not triggered when compiling a |Vim9| |
867 function. | |
6154 | 868 NOTE: When writing Vim scripts a better |
869 alternative is to use an autoloaded function. | |
161 | 870 See |autoload-functions|. |
579 | 871 *GUIEnter* |
872 GUIEnter After starting the GUI successfully, and after | |
873 opening the window. It is triggered before | |
874 VimEnter when using gvim. Can be used to | |
875 position the window from a .gvimrc file: > | |
876 :autocmd GUIEnter * winpos 100 50 | |
1154 | 877 < *GUIFailed* |
878 GUIFailed After starting the GUI failed. Vim may | |
879 continue to run in the terminal, if possible | |
880 (only on Unix and alikes, when connecting the | |
881 X server fails). You may want to quit Vim: > | |
882 :autocmd GUIFailed * qall | |
579 | 883 < *InsertChange* |
884 InsertChange When typing <Insert> while in Insert or | |
885 Replace mode. The |v:insertmode| variable | |
886 indicates the new mode. | |
887 Be careful not to move the cursor or do | |
888 anything else that the user does not expect. | |
2845 | 889 *InsertCharPre* |
890 InsertCharPre When a character is typed in Insert mode, | |
891 before inserting the char. | |
892 The |v:char| variable indicates the char typed | |
893 and can be changed during the event to insert | |
894 a different character. When |v:char| is set | |
895 to more than one character this text is | |
896 inserted literally. | |
897 It is not allowed to change the text |textlock|. | |
898 The event is not triggered when 'paste' is | |
13437 | 899 set. {only with the +eval feature} |
579 | 900 *InsertEnter* |
1154 | 901 InsertEnter Just before starting Insert mode. Also for |
902 Replace mode and Virtual Replace mode. The | |
579 | 903 |v:insertmode| variable indicates the mode. |
4448 | 904 Be careful not to do anything else that the |
905 user does not expect. | |
906 The cursor is restored afterwards. If you do | |
907 not want that set |v:char| to a non-empty | |
908 string. | |
22651
fba5ccf33794
patch 8.2.1874: can't do something just before leaving Insert mode
Bram Moolenaar <Bram@vim.org>
parents:
22441
diff
changeset
|
909 *InsertLeavePre* |
fba5ccf33794
patch 8.2.1874: can't do something just before leaving Insert mode
Bram Moolenaar <Bram@vim.org>
parents:
22441
diff
changeset
|
910 InsertLeavePre Just before leaving Insert mode. Also when |
22723 | 911 using CTRL-O |i_CTRL-O|. Be careful not to |
22651
fba5ccf33794
patch 8.2.1874: can't do something just before leaving Insert mode
Bram Moolenaar <Bram@vim.org>
parents:
22441
diff
changeset
|
912 change mode or use `:normal`, it will likely |
fba5ccf33794
patch 8.2.1874: can't do something just before leaving Insert mode
Bram Moolenaar <Bram@vim.org>
parents:
22441
diff
changeset
|
913 cause trouble. |
579 | 914 *InsertLeave* |
22651
fba5ccf33794
patch 8.2.1874: can't do something just before leaving Insert mode
Bram Moolenaar <Bram@vim.org>
parents:
22441
diff
changeset
|
915 InsertLeave Just after leaving Insert mode. Also when |
fba5ccf33794
patch 8.2.1874: can't do something just before leaving Insert mode
Bram Moolenaar <Bram@vim.org>
parents:
22441
diff
changeset
|
916 using CTRL-O |i_CTRL-O|. But not for |i_CTRL-C|. |
579 | 917 *MenuPopup* |
918 MenuPopup Just before showing the popup menu (under the | |
919 right mouse button). Useful for adjusting the | |
920 menu for what is under the cursor or mouse | |
921 pointer. | |
14952
405309f9dd13
patch 8.1.0487: no menus specifically for the terminal window
Bram Moolenaar <Bram@vim.org>
parents:
14945
diff
changeset
|
922 The pattern is matched against one or two |
405309f9dd13
patch 8.1.0487: no menus specifically for the terminal window
Bram Moolenaar <Bram@vim.org>
parents:
14945
diff
changeset
|
923 characters representing the mode: |
579 | 924 n Normal |
925 v Visual | |
926 o Operator-pending | |
927 i Insert | |
843 | 928 c Command line |
14952
405309f9dd13
patch 8.1.0487: no menus specifically for the terminal window
Bram Moolenaar <Bram@vim.org>
parents:
14945
diff
changeset
|
929 tl Terminal |
25790
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
930 *ModeChanged* |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
931 ModeChanged After changing the mode. The pattern is |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
932 matched against `'old_mode:new_mode'`, for |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
933 example match against `i:*` to simulate |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
934 |InsertLeave|. |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
935 The following values of |v:event| are set: |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
936 old_mode The mode before it changed. |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
937 new_mode The new mode as also returned |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
938 by |mode()|. |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
939 When ModeChanged is triggered, old_mode will |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
940 have the value of new_mode when the event was |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
941 last triggered. |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
942 Usage example to use relative line numbers |
25880 | 943 when entering Visual mode: > |
25790
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
944 :autocmd ModeChanged *:v set relativenumber |
16a7d1154be8
patch 8.2.3430: no generic way to trigger an autocommand on mode change
Bram Moolenaar <Bram@vim.org>
parents:
25619
diff
changeset
|
945 < *OptionSet* |
6935 | 946 OptionSet After setting an option. The pattern is |
947 matched against the long option name. | |
17085
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
948 |<amatch>| indicates what option has been set. |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
949 |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
950 |v:option_type| indicates whether it's global |
17161 | 951 or local scoped. |
17085
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
952 |v:option_command| indicates what type of |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
953 set/let command was used (follow the tag to |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
954 see the table). |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
955 |v:option_new| indicates the newly set value. |
17161 | 956 |v:option_oldlocal| has the old local value. |
957 |v:option_oldglobal| has the old global value. | |
17085
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
958 |v:option_old| indicates the old option value. |
6935 | 959 |
17085
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
960 |v:option_oldlocal| is only set when |:set| |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
961 or |:setlocal| or a |modeline| was used to set |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
962 the option. Similarly |v:option_oldglobal| is |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
963 only set when |:set| or |:setglobal| was used. |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
964 |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
965 Note that when setting a |global-local| string |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
966 option with |:set|, then |v:option_old| is the |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
967 old global value. However, for all other kinds |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
968 of options (local string options, global-local |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
969 number options, ...) it is the old local |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
970 value. |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
971 |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
972 OptionSet is not triggered on startup and for |
620e9011b685
patch 8.1.1542: an OptionSet autocommand does not get enough info
Bram Moolenaar <Bram@vim.org>
parents:
16944
diff
changeset
|
973 the 'key' option for obvious reasons. |
6935 | 974 |
6951
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6935
diff
changeset
|
975 Usage example: Check for the existence of the |
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6935
diff
changeset
|
976 directory in the 'backupdir' and 'undodir' |
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6935
diff
changeset
|
977 options, create the directory if it doesn't |
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6935
diff
changeset
|
978 exist yet. |
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6935
diff
changeset
|
979 |
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6935
diff
changeset
|
980 Note: It's a bad idea to reset an option |
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6935
diff
changeset
|
981 during this autocommand, this may break a |
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6935
diff
changeset
|
982 plugin. You can always use `:noa` to prevent |
b2673982c625
Updated and new runtime files.
Bram Moolenaar <bram@vim.org>
parents:
6935
diff
changeset
|
983 triggering this autocommand. |
6935 | 984 |
14864 | 985 When using |:set| in the autocommand the event |
986 is not triggered again. | |
579 | 987 *QuickFixCmdPre* |
988 QuickFixCmdPre Before a quickfix command is run (|:make|, | |
657 | 989 |:lmake|, |:grep|, |:lgrep|, |:grepadd|, |
990 |:lgrepadd|, |:vimgrep|, |:lvimgrep|, | |
3281 | 991 |:vimgrepadd|, |:lvimgrepadd|, |:cscope|, |
3410
94601b379f38
Updated runtime files. Add Dutch translations.
Bram Moolenaar <bram@vim.org>
parents:
3404
diff
changeset
|
992 |:cfile|, |:cgetfile|, |:caddfile|, |:lfile|, |
94601b379f38
Updated runtime files. Add Dutch translations.
Bram Moolenaar <bram@vim.org>
parents:
3404
diff
changeset
|
993 |:lgetfile|, |:laddfile|, |:helpgrep|, |
10140
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
994 |:lhelpgrep|, |:cexpr|, |:cgetexpr|, |
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
995 |:caddexpr|, |:cbuffer|, |:cgetbuffer|, |
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
996 |:caddbuffer|). |
2151
ae22c450546c
updated for version 7.2.433
Bram Moolenaar <bram@zimbu.org>
parents:
2033
diff
changeset
|
997 The pattern is matched against the command |
ae22c450546c
updated for version 7.2.433
Bram Moolenaar <bram@zimbu.org>
parents:
2033
diff
changeset
|
998 being run. When |:grep| is used but 'grepprg' |
ae22c450546c
updated for version 7.2.433
Bram Moolenaar <bram@zimbu.org>
parents:
2033
diff
changeset
|
999 is set to "internal" it still matches "grep". |
579 | 1000 This command cannot be used to set the |
1001 'makeprg' and 'grepprg' variables. | |
1002 If this command causes an error, the quickfix | |
1003 command is not executed. | |
1004 *QuickFixCmdPost* | |
1005 QuickFixCmdPost Like QuickFixCmdPre, but after a quickfix | |
842 | 1006 command is run, before jumping to the first |
3404 | 1007 location. For |:cfile| and |:lfile| commands |
1008 it is run after error file is read and before | |
5663
1dea14d4c738
Update runtime files. Add support for systemverilog.
Bram Moolenaar <bram@vim.org>
parents:
5555
diff
changeset
|
1009 moving to the first error. |
3404 | 1010 See |QuickFixCmdPost-example|. |
3682 | 1011 *QuitPre* |
4229 | 1012 QuitPre When using `:quit`, `:wq` or `:qall`, before |
1013 deciding whether it closes the current window | |
24751 | 1014 or quits Vim. For `:wq` the buffer is written |
1015 before QuitPre is triggered. Can be used to | |
1016 close any non-essential window if the current | |
1017 window is the last ordinary window. | |
13442
94e638936d3e
patch 8.0.1595: no autocommand triggered before exiting
Christian Brabandt <cb@256bit.org>
parents:
13437
diff
changeset
|
1018 Also see |ExitPre|. |
579 | 1019 *RemoteReply* |
1020 RemoteReply When a reply from a Vim that functions as | |
1154 | 1021 server was received |server2client()|. The |
1022 pattern is matched against the {serverid}. | |
579 | 1023 <amatch> is equal to the {serverid} from which |
1024 the reply was sent, and <afile> is the actual | |
1025 reply string. | |
1026 Note that even if an autocommand is defined, | |
1027 the reply should be read with |remote_read()| | |
1028 to consume it. | |
18098
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1029 *SafeState* |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1030 SafeState When nothing is pending, going to wait for the |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1031 user to type a character. |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1032 This will not be triggered when: |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1033 - an operator is pending |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1034 - a register was entered with "r |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1035 - halfway executing a command |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1036 - executing a mapping |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1037 - there is typeahead |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1038 - Insert mode completion is active |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1039 - Command line completion is active |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1040 You can use `mode()` to find out what state |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1041 Vim is in. That may be: |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1042 - VIsual mode |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1043 - Normal mode |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1044 - Insert mode |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1045 - Command-line mode |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1046 Depending on what you want to do, you may also |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1047 check more with `state()`, e.g. whether the |
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1048 screen was scrolled for messages. |
18102
0d9ec3a2821f
patch 8.1.2046: SafeState may be triggered at the wrong moment
Bram Moolenaar <Bram@vim.org>
parents:
18098
diff
changeset
|
1049 *SafeStateAgain* |
0d9ec3a2821f
patch 8.1.2046: SafeState may be triggered at the wrong moment
Bram Moolenaar <Bram@vim.org>
parents:
18098
diff
changeset
|
1050 SafeStateAgain Like SafeState but after processing any |
0d9ec3a2821f
patch 8.1.2046: SafeState may be triggered at the wrong moment
Bram Moolenaar <Bram@vim.org>
parents:
18098
diff
changeset
|
1051 messages and invoking callbacks. This may be |
0d9ec3a2821f
patch 8.1.2046: SafeState may be triggered at the wrong moment
Bram Moolenaar <Bram@vim.org>
parents:
18098
diff
changeset
|
1052 triggered often, don't do something that takes |
0d9ec3a2821f
patch 8.1.2046: SafeState may be triggered at the wrong moment
Bram Moolenaar <Bram@vim.org>
parents:
18098
diff
changeset
|
1053 time. |
18098
a2870e6f5b45
patch 8.1.2044: no easy way to process postponed work
Bram Moolenaar <Bram@vim.org>
parents:
18043
diff
changeset
|
1054 |
579 | 1055 *SessionLoadPost* |
1056 SessionLoadPost After loading the session file created using | |
1057 the |:mksession| command. | |
724 | 1058 *ShellCmdPost* |
1059 ShellCmdPost After executing a shell command with |:!cmd|, | |
1060 |:shell|, |:make| and |:grep|. Can be used to | |
1061 check for any changed files. | |
1062 *ShellFilterPost* | |
1063 ShellFilterPost After executing a shell command with | |
1064 ":{range}!cmd", ":w !cmd" or ":r !cmd". | |
1065 Can be used to check for any changed files. | |
716 | 1066 *SourcePre* |
1067 SourcePre Before sourcing a Vim script. |:source| | |
1061 | 1068 <afile> is the name of the file being sourced. |
15442
3e2e1608efa4
patch 8.1.0729: there is a SourcePre autocommand event but not a SourcePost
Bram Moolenaar <Bram@vim.org>
parents:
15334
diff
changeset
|
1069 *SourcePost* |
3e2e1608efa4
patch 8.1.0729: there is a SourcePre autocommand event but not a SourcePost
Bram Moolenaar <Bram@vim.org>
parents:
15334
diff
changeset
|
1070 SourcePost After sourcing a Vim script. |:source| |
3e2e1608efa4
patch 8.1.0729: there is a SourcePre autocommand event but not a SourcePost
Bram Moolenaar <Bram@vim.org>
parents:
15334
diff
changeset
|
1071 <afile> is the name of the file being sourced. |
3e2e1608efa4
patch 8.1.0729: there is a SourcePre autocommand event but not a SourcePost
Bram Moolenaar <Bram@vim.org>
parents:
15334
diff
changeset
|
1072 Not triggered when sourcing was interrupted. |
3e2e1608efa4
patch 8.1.0729: there is a SourcePre autocommand event but not a SourcePost
Bram Moolenaar <Bram@vim.org>
parents:
15334
diff
changeset
|
1073 Also triggered after a SourceCmd autocommand |
3e2e1608efa4
patch 8.1.0729: there is a SourcePre autocommand event but not a SourcePost
Bram Moolenaar <Bram@vim.org>
parents:
15334
diff
changeset
|
1074 was triggered. |
1061 | 1075 *SourceCmd* |
1076 SourceCmd When sourcing a Vim script. |:source| | |
1077 <afile> is the name of the file being sourced. | |
1078 The autocommand must source this file. | |
1079 |Cmd-event| | |
650 | 1080 *SpellFileMissing* |
1081 SpellFileMissing When trying to load a spell checking file and | |
1061 | 1082 it can't be found. The pattern is matched |
1083 against the language. <amatch> is the | |
1084 language, 'encoding' also matters. See | |
650 | 1085 |spell-SpellFileMissing|. |
579 | 1086 *StdinReadPost* |
1087 StdinReadPost After reading from the stdin into the buffer, | |
1088 before executing the modelines. Only used | |
1089 when the "-" argument was used when Vim was | |
1090 started |--|. | |
1091 *StdinReadPre* | |
1092 StdinReadPre Before reading from stdin into the buffer. | |
1093 Only used when the "-" argument was used when | |
1094 Vim was started |--|. | |
1095 *SwapExists* | |
1096 SwapExists Detected an existing swap file when starting | |
1097 to edit a file. Only when it is possible to | |
1098 select a way to handle the situation, when Vim | |
1099 would ask the user what to do. | |
1100 The |v:swapname| variable holds the name of | |
590 | 1101 the swap file found, <afile> the file being |
1102 edited. |v:swapcommand| may contain a command | |
1103 to be executed in the opened file. | |
1104 The commands should set the |v:swapchoice| | |
1105 variable to a string with one character to | |
1106 tell Vim what should be done next: | |
579 | 1107 'o' open read-only |
1108 'e' edit the file anyway | |
1109 'r' recover | |
1110 'd' delete the swap file | |
1111 'q' quit, don't edit the file | |
1112 'a' abort, like hitting CTRL-C | |
1113 When set to an empty string the user will be | |
1114 asked, as if there was no SwapExists autocmd. | |
1919 | 1115 *E812* |
1116 It is not allowed to change to another buffer, | |
1117 change a buffer name or change directory | |
1118 here. | |
13437 | 1119 {only available with the +eval feature} |
579 | 1120 *Syntax* |
1154 | 1121 Syntax When the 'syntax' option has been set. The |
1122 pattern is matched against the syntax name. | |
579 | 1123 <afile> can be used for the name of the file |
1124 where this option was set, and <amatch> for | |
1125 the new value of 'syntax'. | |
1126 See |:syn-on|. | |
9599
42a8a81decdf
commit https://github.com/vim/vim/commit/12c11d553053f5a9eae9eb3c518279b12fa928c2
Christian Brabandt <cb@256bit.org>
parents:
9595
diff
changeset
|
1127 *TabClosed* |
42a8a81decdf
commit https://github.com/vim/vim/commit/12c11d553053f5a9eae9eb3c518279b12fa928c2
Christian Brabandt <cb@256bit.org>
parents:
9595
diff
changeset
|
1128 TabClosed After closing a tab page. |
677 | 1129 *TabEnter* |
1130 TabEnter Just after entering a tab page. |tab-page| | |
872 | 1131 After triggering the WinEnter and before |
1132 triggering the BufEnter event. | |
677 | 1133 *TabLeave* |
1134 TabLeave Just before leaving a tab page. |tab-page| | |
1135 A WinLeave event will have been triggered | |
1136 first. | |
9595
0190d5de215f
commit https://github.com/vim/vim/commit/c917da4b3e8801a255dbefea8e4ed19c1c716dd8
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
1137 *TabNew* |
0190d5de215f
commit https://github.com/vim/vim/commit/c917da4b3e8801a255dbefea8e4ed19c1c716dd8
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
1138 TabNew When a tab page was created. |tab-page| |
0190d5de215f
commit https://github.com/vim/vim/commit/c917da4b3e8801a255dbefea8e4ed19c1c716dd8
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
1139 A WinEnter event will have been triggered |
0190d5de215f
commit https://github.com/vim/vim/commit/c917da4b3e8801a255dbefea8e4ed19c1c716dd8
Christian Brabandt <cb@256bit.org>
parents:
9286
diff
changeset
|
1140 first, TabEnter follows. |
579 | 1141 *TermChanged* |
1142 TermChanged After the value of 'term' has changed. Useful | |
1143 for re-loading the syntax file to update the | |
1144 colors, fonts and other terminal-dependent | |
1145 settings. Executed for all loaded buffers. | |
13444
9f06f7aca74c
patch 8.0.1596: no autocommand specifically for opening a terminal window
Christian Brabandt <cb@256bit.org>
parents:
13442
diff
changeset
|
1146 *TerminalOpen* |
9f06f7aca74c
patch 8.0.1596: no autocommand specifically for opening a terminal window
Christian Brabandt <cb@256bit.org>
parents:
13442
diff
changeset
|
1147 TerminalOpen Just after a terminal buffer was created, with |
9f06f7aca74c
patch 8.0.1596: no autocommand specifically for opening a terminal window
Christian Brabandt <cb@256bit.org>
parents:
13442
diff
changeset
|
1148 `:terminal` or |term_start()|. This event is |
9f06f7aca74c
patch 8.0.1596: no autocommand specifically for opening a terminal window
Christian Brabandt <cb@256bit.org>
parents:
13442
diff
changeset
|
1149 triggered even if the buffer is created |
9f06f7aca74c
patch 8.0.1596: no autocommand specifically for opening a terminal window
Christian Brabandt <cb@256bit.org>
parents:
13442
diff
changeset
|
1150 without a window, with the ++hidden option. |
18450
507348b211b4
patch 8.1.2219: no autocommand for open window with terminal
Bram Moolenaar <Bram@vim.org>
parents:
18130
diff
changeset
|
1151 *TerminalWinOpen* |
507348b211b4
patch 8.1.2219: no autocommand for open window with terminal
Bram Moolenaar <Bram@vim.org>
parents:
18130
diff
changeset
|
1152 TerminalWinOpen Just after a terminal buffer was created, with |
507348b211b4
patch 8.1.2219: no autocommand for open window with terminal
Bram Moolenaar <Bram@vim.org>
parents:
18130
diff
changeset
|
1153 `:terminal` or |term_start()|. This event is |
507348b211b4
patch 8.1.2219: no autocommand for open window with terminal
Bram Moolenaar <Bram@vim.org>
parents:
18130
diff
changeset
|
1154 triggered only if the buffer is created |
507348b211b4
patch 8.1.2219: no autocommand for open window with terminal
Bram Moolenaar <Bram@vim.org>
parents:
18130
diff
changeset
|
1155 with a window. Can be used to set window |
507348b211b4
patch 8.1.2219: no autocommand for open window with terminal
Bram Moolenaar <Bram@vim.org>
parents:
18130
diff
changeset
|
1156 local options for the terminal window. |
579 | 1157 *TermResponse* |
1158 TermResponse After the response to |t_RV| is received from | |
1159 the terminal. The value of |v:termresponse| | |
1160 can be used to do things depending on the | |
2788 | 1161 terminal version. Note that this event may be |
1162 triggered halfway executing another event, | |
1163 especially if file I/O, a shell command or | |
1164 anything else that takes time is involved. | |
4264 | 1165 *TextChanged* |
1166 TextChanged After a change was made to the text in the | |
15512 | 1167 current buffer in Normal mode. That is after |
1168 |b:changedtick| has changed (also when that | |
1169 happened before the TextChanged autocommand | |
1170 was defined). | |
4264 | 1171 Not triggered when there is typeahead or when |
1172 an operator is pending. | |
16023 | 1173 Note: This can not be skipped with |
1174 `:noautocmd`. | |
4264 | 1175 Careful: This is triggered very often, don't |
1176 do anything that the user does not expect or | |
1177 that is slow. | |
1178 *TextChangedI* | |
1179 TextChangedI After a change was made to the text in the | |
1180 current buffer in Insert mode. | |
1181 Not triggered when the popup menu is visible. | |
1182 Otherwise the same as TextChanged. | |
13240
5ed6e4a25925
patch 8.0.1494: no autocmd triggered in Insert mode with visible popup menu
Christian Brabandt <cb@256bit.org>
parents:
13231
diff
changeset
|
1183 *TextChangedP* |
5ed6e4a25925
patch 8.0.1494: no autocmd triggered in Insert mode with visible popup menu
Christian Brabandt <cb@256bit.org>
parents:
13231
diff
changeset
|
1184 TextChangedP After a change was made to the text in the |
5ed6e4a25925
patch 8.0.1494: no autocmd triggered in Insert mode with visible popup menu
Christian Brabandt <cb@256bit.org>
parents:
13231
diff
changeset
|
1185 current buffer in Insert mode, only when the |
5ed6e4a25925
patch 8.0.1494: no autocmd triggered in Insert mode with visible popup menu
Christian Brabandt <cb@256bit.org>
parents:
13231
diff
changeset
|
1186 popup menu is visible. Otherwise the same as |
5ed6e4a25925
patch 8.0.1494: no autocmd triggered in Insert mode with visible popup menu
Christian Brabandt <cb@256bit.org>
parents:
13231
diff
changeset
|
1187 TextChanged. |
13051 | 1188 *TextYankPost* |
13037
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1189 TextYankPost After text has been yanked or deleted in the |
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1190 current buffer. The following values of |
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1191 |v:event| can be used to determine the operation |
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1192 that triggered this autocmd: |
18130 | 1193 operator The operation performed. |
1194 regcontents Text that was stored in the | |
13037
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1195 register, as a list of lines, |
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1196 like with: > |
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1197 getreg(r, 1, 1) |
25973 | 1198 < regname Name of the register or empty |
1199 string for the unnamed | |
1200 register, see |registers|. | |
13037
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1201 regtype Type of the register, see |
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1202 |getregtype()|. |
20824
b8ca32dcfabb
patch 8.2.0964: TextYankPost does not provide info about Visual selection
Bram Moolenaar <Bram@vim.org>
parents:
20800
diff
changeset
|
1203 visual True if the operation is |
b8ca32dcfabb
patch 8.2.0964: TextYankPost does not provide info about Visual selection
Bram Moolenaar <Bram@vim.org>
parents:
20800
diff
changeset
|
1204 performed on a |Visual| area. |
13037
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1205 Not triggered when |quote_| is used nor when |
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1206 called recursively. |
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1207 It is not allowed to change the buffer text, |
6e81a68d63a1
patch 8.0.1394: cannot intercept a yank command
Christian Brabandt <cb@256bit.org>
parents:
12785
diff
changeset
|
1208 see |textlock|. |
13437 | 1209 {only when compiled with the +eval feature} |
20800
e76b83c07bd8
patch 8.2.0952: no simple way to interrupt Vim
Bram Moolenaar <Bram@vim.org>
parents:
19303
diff
changeset
|
1210 |
579 | 1211 *User* |
1212 User Never executed automatically. To be used for | |
1213 autocommands that are only executed with | |
1214 ":doautocmd". | |
13735 | 1215 Note that when `:doautocmd User MyEvent` is |
1216 used while there are no matching autocommands, | |
1217 you will get an error. If you don't want | |
1218 that, define a dummy autocommand yourself. | |
20800
e76b83c07bd8
patch 8.2.0952: no simple way to interrupt Vim
Bram Moolenaar <Bram@vim.org>
parents:
19303
diff
changeset
|
1219 |
e76b83c07bd8
patch 8.2.0952: no simple way to interrupt Vim
Bram Moolenaar <Bram@vim.org>
parents:
19303
diff
changeset
|
1220 *SigUSR1* |
e76b83c07bd8
patch 8.2.0952: no simple way to interrupt Vim
Bram Moolenaar <Bram@vim.org>
parents:
19303
diff
changeset
|
1221 SigUSR1 After the SIGUSR1 signal has been detected. |
e76b83c07bd8
patch 8.2.0952: no simple way to interrupt Vim
Bram Moolenaar <Bram@vim.org>
parents:
19303
diff
changeset
|
1222 Could be used if other ways of notifying Vim |
e76b83c07bd8
patch 8.2.0952: no simple way to interrupt Vim
Bram Moolenaar <Bram@vim.org>
parents:
19303
diff
changeset
|
1223 are not feasible. E.g. to check for the |
e76b83c07bd8
patch 8.2.0952: no simple way to interrupt Vim
Bram Moolenaar <Bram@vim.org>
parents:
19303
diff
changeset
|
1224 result of a build that takes a long time, or |
e76b83c07bd8
patch 8.2.0952: no simple way to interrupt Vim
Bram Moolenaar <Bram@vim.org>
parents:
19303
diff
changeset
|
1225 when a motion sensor is triggered. |
e76b83c07bd8
patch 8.2.0952: no simple way to interrupt Vim
Bram Moolenaar <Bram@vim.org>
parents:
19303
diff
changeset
|
1226 {only on Unix} |
e76b83c07bd8
patch 8.2.0952: no simple way to interrupt Vim
Bram Moolenaar <Bram@vim.org>
parents:
19303
diff
changeset
|
1227 |
579 | 1228 *UserGettingBored* |
4264 | 1229 UserGettingBored When the user presses the same key 42 times. |
1230 Just kidding! :-) | |
579 | 1231 *VimEnter* |
1232 VimEnter After doing all the startup stuff, including | |
1233 loading .vimrc files, executing the "-c cmd" | |
1234 arguments, creating all windows and loading | |
1235 the buffers in them. | |
8738
e770986c855a
commit https://github.com/vim/vim/commit/1473551a4457d4920b235eeeb9f279e196ee7225
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
1236 Just before this event is triggered the |
e770986c855a
commit https://github.com/vim/vim/commit/1473551a4457d4920b235eeeb9f279e196ee7225
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
1237 |v:vim_did_enter| variable is set, so that you |
e770986c855a
commit https://github.com/vim/vim/commit/1473551a4457d4920b235eeeb9f279e196ee7225
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
1238 can do: > |
e770986c855a
commit https://github.com/vim/vim/commit/1473551a4457d4920b235eeeb9f279e196ee7225
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
1239 if v:vim_did_enter |
e770986c855a
commit https://github.com/vim/vim/commit/1473551a4457d4920b235eeeb9f279e196ee7225
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
1240 call s:init() |
e770986c855a
commit https://github.com/vim/vim/commit/1473551a4457d4920b235eeeb9f279e196ee7225
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
1241 else |
18130 | 1242 au VimEnter * call s:init() |
8738
e770986c855a
commit https://github.com/vim/vim/commit/1473551a4457d4920b235eeeb9f279e196ee7225
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
1243 endif |
e770986c855a
commit https://github.com/vim/vim/commit/1473551a4457d4920b235eeeb9f279e196ee7225
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
1244 < *VimLeave* |
579 | 1245 VimLeave Before exiting Vim, just after writing the |
1246 .viminfo file. Executed only once, like | |
1247 VimLeavePre. | |
1248 To detect an abnormal exit use |v:dying|. | |
2226
36a9ac99e1ca
Don't execute some autocommands when v:dying is 2 or more.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
1249 When v:dying is 2 or more this event is not |
36a9ac99e1ca
Don't execute some autocommands when v:dying is 2 or more.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
1250 triggered. |
23048
ad674a98058a
patch 8.2.2070: can't get the exit value in VimLeave(Pre) autocommands
Bram Moolenaar <Bram@vim.org>
parents:
22958
diff
changeset
|
1251 To get the exit code use |v:exiting|. |
579 | 1252 *VimLeavePre* |
1253 VimLeavePre Before exiting Vim, just before writing the | |
1254 .viminfo file. This is executed only once, | |
1255 if there is a match with the name of what | |
1256 happens to be the current buffer when exiting. | |
1257 Mostly useful with a "*" pattern. > | |
1258 :autocmd VimLeavePre * call CleanupStuff() | |
1259 < To detect an abnormal exit use |v:dying|. | |
2226
36a9ac99e1ca
Don't execute some autocommands when v:dying is 2 or more.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
1260 When v:dying is 2 or more this event is not |
36a9ac99e1ca
Don't execute some autocommands when v:dying is 2 or more.
Bram Moolenaar <bram@vim.org>
parents:
2154
diff
changeset
|
1261 triggered. |
23048
ad674a98058a
patch 8.2.2070: can't get the exit value in VimLeave(Pre) autocommands
Bram Moolenaar <Bram@vim.org>
parents:
22958
diff
changeset
|
1262 To get the exit code use |v:exiting|. |
766 | 1263 *VimResized* |
1264 VimResized After the Vim window was resized, thus 'lines' | |
1265 and/or 'columns' changed. Not when starting | |
1266 up though. | |
23165
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
1267 *VimResume* |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
1268 VimResume When the Vim instance is resumed after being |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
1269 suspended and |VimSuspend| was triggered. |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
1270 Useful for triggering |:checktime| and ensure |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
1271 the buffers content did not change while Vim |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
1272 was suspended: > |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
1273 :autocmd VimResume * checktime |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
1274 < *VimSuspend* |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
1275 VimSuspend When the Vim instance is suspended. Only when |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
1276 CTRL-Z was typed inside Vim, not when the |
a916fca16d4b
patch 8.2.2128: there is no way to do something on CTRL-Z
Bram Moolenaar <Bram@vim.org>
parents:
23164
diff
changeset
|
1277 SIGSTOP or SIGTSTP signal was sent to Vim. |
7 | 1278 *WinEnter* |
1279 WinEnter After entering another window. Not done for | |
1280 the first window, when Vim has just started. | |
1281 Useful for setting the window height. | |
1282 If the window is for another buffer, Vim | |
1283 executes the BufEnter autocommands after the | |
1284 WinEnter autocommands. | |
13735 | 1285 Note: For split and tabpage commands the |
1286 WinEnter event is triggered after the split | |
1287 or tab command but before the file is loaded. | |
1288 | |
7 | 1289 *WinLeave* |
1290 WinLeave Before leaving a window. If the window to be | |
1291 entered next is for a different buffer, Vim | |
1292 executes the BufLeave autocommands before the | |
1293 WinLeave autocommands (but not for ":new"). | |
1294 Not used for ":qa" or ":q" when exiting Vim. | |
1295 | |
9599
42a8a81decdf
commit https://github.com/vim/vim/commit/12c11d553053f5a9eae9eb3c518279b12fa928c2
Christian Brabandt <cb@256bit.org>
parents:
9595
diff
changeset
|
1296 *WinNew* |
42a8a81decdf
commit https://github.com/vim/vim/commit/12c11d553053f5a9eae9eb3c518279b12fa928c2
Christian Brabandt <cb@256bit.org>
parents:
9595
diff
changeset
|
1297 WinNew When a new window was created. Not done for |
10218
584c835a2de1
commit https://github.com/vim/vim/commit/50ba526fbf3e9e5e0e6b0b3086a4d5df581ebc7e
Christian Brabandt <cb@256bit.org>
parents:
10198
diff
changeset
|
1298 the first window, when Vim has just started. |
9599
42a8a81decdf
commit https://github.com/vim/vim/commit/12c11d553053f5a9eae9eb3c518279b12fa928c2
Christian Brabandt <cb@256bit.org>
parents:
9595
diff
changeset
|
1299 Before a WinEnter event. |
42a8a81decdf
commit https://github.com/vim/vim/commit/12c11d553053f5a9eae9eb3c518279b12fa928c2
Christian Brabandt <cb@256bit.org>
parents:
9595
diff
changeset
|
1300 |
7 | 1301 ============================================================================== |
1302 6. Patterns *autocmd-patterns* *{pat}* | |
1303 | |
6741 | 1304 The {pat} argument can be a comma separated list. This works as if the |
1305 command was given with each pattern separately. Thus this command: > | |
1306 :autocmd BufRead *.txt,*.info set et | |
1307 Is equivalent to: > | |
1308 :autocmd BufRead *.txt set et | |
1309 :autocmd BufRead *.info set et | |
1310 | |
7 | 1311 The file pattern {pat} is tested for a match against the file name in one of |
1312 two ways: | |
1313 1. When there is no '/' in the pattern, Vim checks for a match against only | |
1314 the tail part of the file name (without its leading directory path). | |
2033
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1919
diff
changeset
|
1315 2. When there is a '/' in the pattern, Vim checks for a match against both the |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1919
diff
changeset
|
1316 short file name (as you typed it) and the full file name (after expanding |
de5a43c5eedc
Update documentation files.
Bram Moolenaar <bram@zimbu.org>
parents:
1919
diff
changeset
|
1317 it to a full path and resolving symbolic links). |
7 | 1318 |
40 | 1319 The special pattern <buffer> or <buffer=N> is used for buffer-local |
1320 autocommands |autocmd-buflocal|. This pattern is not matched against the name | |
1321 of a buffer. | |
1322 | |
7 | 1323 Examples: > |
1324 :autocmd BufRead *.txt set et | |
1325 Set the 'et' option for all text files. > | |
1326 | |
1327 :autocmd BufRead /vim/src/*.c set cindent | |
1328 Set the 'cindent' option for C files in the /vim/src directory. > | |
1329 | |
1330 :autocmd BufRead /tmp/*.c set ts=5 | |
1331 If you have a link from "/tmp/test.c" to "/home/nobody/vim/src/test.c", and | |
1332 you start editing "/tmp/test.c", this autocommand will match. | |
1333 | |
1334 Note: To match part of a path, but not from the root directory, use a '*' as | |
1335 the first character. Example: > | |
1336 :autocmd BufRead */doc/*.txt set tw=78 | |
1337 This autocommand will for example be executed for "/tmp/doc/xx.txt" and | |
1338 "/usr/home/piet/doc/yy.txt". The number of directories does not matter here. | |
1339 | |
1340 | |
1341 The file name that the pattern is matched against is after expanding | |
1621 | 1342 wildcards. Thus if you issue this command: > |
7 | 1343 :e $ROOTDIR/main.$EXT |
1344 The argument is first expanded to: > | |
1345 /usr/root/main.py | |
1346 Before it's matched with the pattern of the autocommand. Careful with this | |
1347 when using events like FileReadCmd, the value of <amatch> may not be what you | |
1348 expect. | |
1349 | |
1350 | |
1351 Environment variables can be used in a pattern: > | |
1352 :autocmd BufRead $VIMRUNTIME/doc/*.txt set expandtab | |
1353 And ~ can be used for the home directory (if $HOME is defined): > | |
1354 :autocmd BufWritePost ~/.vimrc so ~/.vimrc | |
1355 :autocmd BufRead ~archive/* set readonly | |
1356 The environment variable is expanded when the autocommand is defined, not when | |
1357 the autocommand is executed. This is different from the command! | |
1358 | |
1359 *file-pattern* | |
1360 The pattern is interpreted like mostly used in file names: | |
5294 | 1361 * matches any sequence of characters; Unusual: includes path |
5277 | 1362 separators |
7 | 1363 ? matches any single character |
1364 \? matches a '?' | |
1365 . matches a '.' | |
1366 ~ matches a '~' | |
1367 , separates patterns | |
1368 \, matches a ',' | |
1369 { } like \( \) in a |pattern| | |
1370 , inside { }: like \| in a |pattern| | |
5259
6b7ab6a4f31a
updated for version 7.4b.006
Bram Moolenaar <bram@vim.org>
parents:
5247
diff
changeset
|
1371 \} literal } |
6b7ab6a4f31a
updated for version 7.4b.006
Bram Moolenaar <bram@vim.org>
parents:
5247
diff
changeset
|
1372 \{ literal { |
6b7ab6a4f31a
updated for version 7.4b.006
Bram Moolenaar <bram@vim.org>
parents:
5247
diff
changeset
|
1373 \\\{n,m\} like \{n,m} in a |pattern| |
7 | 1374 \ special meaning like in a |pattern| |
1375 [ch] matches 'c' or 'h' | |
1376 [^ch] match any character but 'c' and 'h' | |
1377 | |
1378 Note that for all systems the '/' character is used for path separator (even | |
18912
ccd16426a1f9
patch 8.2.0017: OS/2 and MS-DOS are still mentioned
Bram Moolenaar <Bram@vim.org>
parents:
18879
diff
changeset
|
1379 for MS-Windows). This was done because the backslash is difficult to use in a |
ccd16426a1f9
patch 8.2.0017: OS/2 and MS-DOS are still mentioned
Bram Moolenaar <Bram@vim.org>
parents:
18879
diff
changeset
|
1380 pattern and to make the autocommands portable across different systems. |
7 | 1381 |
10140
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
1382 It is possible to use |pattern| items, but they may not work as expected, |
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
1383 because of the translation done for the above. |
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
1384 |
40 | 1385 *autocmd-changes* |
7 | 1386 Matching with the pattern is done when an event is triggered. Changing the |
1387 buffer name in one of the autocommands, or even deleting the buffer, does not | |
1388 change which autocommands will be executed. Example: > | |
1389 | |
1390 au BufEnter *.foo bdel | |
1391 au BufEnter *.foo set modified | |
1392 | |
1393 This will delete the current buffer and then set 'modified' in what has become | |
1394 the current buffer instead. Vim doesn't take into account that "*.foo" | |
1395 doesn't match with that buffer name. It matches "*.foo" with the name of the | |
1396 buffer at the moment the event was triggered. | |
1397 | |
40 | 1398 However, buffer-local autocommands will not be executed for a buffer that has |
1399 been wiped out with |:bwipe|. After deleting the buffer with |:bdel| the | |
1400 buffer actually still exists (it becomes unlisted), thus the autocommands are | |
1401 still executed. | |
1402 | |
7 | 1403 ============================================================================== |
856 | 1404 7. Buffer-local autocommands *autocmd-buflocal* *autocmd-buffer-local* |
1405 *<buffer=N>* *<buffer=abuf>* *E680* | |
40 | 1406 |
1407 Buffer-local autocommands are attached to a specific buffer. They are useful | |
1408 if the buffer does not have a name and when the name does not match a specific | |
1409 pattern. But it also means they must be explicitly added to each buffer. | |
1410 | |
1411 Instead of a pattern buffer-local autocommands use one of these forms: | |
1412 <buffer> current buffer | |
1413 <buffer=99> buffer number 99 | |
1414 <buffer=abuf> using <abuf> (only when executing autocommands) | |
1415 |<abuf>| | |
1416 | |
1417 Examples: > | |
1418 :au CursorHold <buffer> echo 'hold' | |
1419 :au CursorHold <buffer=33> echo 'hold' | |
7051
eff26a8620ce
commit https://github.com/vim/vim/commit/88774fdd23f08355297bb8cda78856859051d3c7
Christian Brabandt <cb@256bit.org>
parents:
7013
diff
changeset
|
1420 :au BufNewFile * au CursorHold <buffer=abuf> echo 'hold' |
40 | 1421 |
1422 All the commands for autocommands also work with buffer-local autocommands, | |
1423 simply use the special string instead of the pattern. Examples: > | |
856 | 1424 :au! * <buffer> " remove buffer-local autocommands for |
1425 " current buffer | |
1426 :au! * <buffer=33> " remove buffer-local autocommands for | |
1427 " buffer #33 | |
1621 | 1428 :bufdo :au! CursorHold <buffer> " remove autocmd for given event for all |
856 | 1429 " buffers |
1430 :au * <buffer> " list buffer-local autocommands for | |
1431 " current buffer | |
40 | 1432 |
1433 Note that when an autocommand is defined for the current buffer, it is stored | |
1434 with the buffer number. Thus it uses the form "<buffer=12>", where 12 is the | |
1435 number of the current buffer. You will see this when listing autocommands, | |
1436 for example. | |
1437 | |
1438 To test for presence of buffer-local autocommands use the |exists()| function | |
1439 as follows: > | |
1440 :if exists("#CursorHold#<buffer=12>") | ... | endif | |
1441 :if exists("#CursorHold#<buffer>") | ... | endif " for current buffer | |
1442 | |
1443 When a buffer is wiped out its buffer-local autocommands are also gone, of | |
1444 course. Note that when deleting a buffer, e.g., with ":bdel", it is only | |
1445 unlisted, the autocommands are still present. In order to see the removal of | |
1446 buffer-local autocommands: > | |
1447 :set verbose=6 | |
1448 | |
1449 It is not possible to define buffer-local autocommands for a non-existent | |
1450 buffer. | |
1451 | |
1452 ============================================================================== | |
1453 8. Groups *autocmd-groups* | |
7 | 1454 |
1455 Autocommands can be put together in a group. This is useful for removing or | |
1456 executing a group of autocommands. For example, all the autocommands for | |
1457 syntax highlighting are put in the "highlight" group, to be able to execute | |
1458 ":doautoall highlight BufRead" when the GUI starts. | |
1459 | |
1460 When no specific group is selected, Vim uses the default group. The default | |
1461 group does not have a name. You cannot execute the autocommands from the | |
1462 default group separately; you can execute them only by executing autocommands | |
1463 for all groups. | |
1464 | |
1465 Normally, when executing autocommands automatically, Vim uses the autocommands | |
1466 for all groups. The group only matters when executing autocommands with | |
1467 ":doautocmd" or ":doautoall", or when defining or deleting autocommands. | |
1468 | |
1469 The group name can contain any characters except white space. The group name | |
1470 "end" is reserved (also in uppercase). | |
1471 | |
1472 The group name is case sensitive. Note that this is different from the event | |
1473 name! | |
1474 | |
1475 *:aug* *:augroup* | |
1476 :aug[roup] {name} Define the autocmd group name for the | |
1477 following ":autocmd" commands. The name "end" | |
1478 or "END" selects the default group. | |
7384
aea5ebf352c4
commit https://github.com/vim/vim/commit/256972a9849b5d575b62a6a71be5b6934b5b0e8b
Christian Brabandt <cb@256bit.org>
parents:
7051
diff
changeset
|
1479 To avoid confusion, the name should be |
aea5ebf352c4
commit https://github.com/vim/vim/commit/256972a9849b5d575b62a6a71be5b6934b5b0e8b
Christian Brabandt <cb@256bit.org>
parents:
7051
diff
changeset
|
1480 different from existing {event} names, as this |
aea5ebf352c4
commit https://github.com/vim/vim/commit/256972a9849b5d575b62a6a71be5b6934b5b0e8b
Christian Brabandt <cb@256bit.org>
parents:
7051
diff
changeset
|
1481 most likely will not do what you intended. |
7 | 1482 |
10140
b11ceef7116e
commit https://github.com/vim/vim/commit/64d8e25bf6efe5f18b032563521c3ce278c316ab
Christian Brabandt <cb@256bit.org>
parents:
9737
diff
changeset
|
1483 *:augroup-delete* *E367* *W19* *E936* |
7 | 1484 :aug[roup]! {name} Delete the autocmd group {name}. Don't use |
1485 this if there is still an autocommand using | |
9737
35ce559b8553
commit https://github.com/vim/vim/commit/bc8801c9317eb721a2ee91322669f2dd5d136380
Christian Brabandt <cb@256bit.org>
parents:
9653
diff
changeset
|
1486 this group! You will get a warning if doing |
21676 | 1487 it anyway. When the group is the current |
1488 group you will get error E936. | |
7 | 1489 |
1490 To enter autocommands for a specific group, use this method: | |
1491 1. Select the group with ":augroup {name}". | |
1492 2. Delete any old autocommands with ":au!". | |
1493 3. Define the autocommands. | |
1494 4. Go back to the default group with "augroup END". | |
1495 | |
1496 Example: > | |
1497 :augroup uncompress | |
1498 : au! | |
1499 : au BufEnter *.gz %!gunzip | |
1500 :augroup END | |
1501 | |
1502 This prevents having the autocommands defined twice (e.g., after sourcing the | |
1503 .vimrc file again). | |
1504 | |
25880 | 1505 *FileExplorer* |
1506 There is one group that is recognized by Vim: FileExplorer. If this group | |
1507 exists Vim assumes that editing a directory is possible and will trigger a | |
1508 plugin that lists the files in that directory. This is used by the |netrw| | |
1509 plugin. This allows you to do: > | |
1510 browse edit | |
1511 | |
7 | 1512 ============================================================================== |
40 | 1513 9. Executing autocommands *autocmd-execute* |
7 | 1514 |
1515 Vim can also execute Autocommands non-automatically. This is useful if you | |
1516 have changed autocommands, or when Vim has executed the wrong autocommands | |
1517 (e.g., the file pattern match was wrong). | |
1518 | |
1519 Note that the 'eventignore' option applies here too. Events listed in this | |
1520 option will not cause any commands to be executed. | |
1521 | |
16944 | 1522 *:do* *:doau* *:doaut* *:doautocmd* *E217* |
3356 | 1523 :do[autocmd] [<nomodeline>] [group] {event} [fname] |
7 | 1524 Apply the autocommands matching [fname] (default: |
1525 current file name) for {event} to the current buffer. | |
1526 You can use this when the current file name does not | |
1527 match the right pattern, after changing settings, or | |
1528 to execute autocommands for a certain event. | |
1529 It's possible to use this inside an autocommand too, | |
1530 so you can base the autocommands for one extension on | |
1531 another extension. Example: > | |
3224 | 1532 :au BufEnter *.cpp so ~/.vimrc_cpp |
1533 :au BufEnter *.cpp doau BufEnter x.c | |
7 | 1534 < Be careful to avoid endless loops. See |
1535 |autocmd-nested|. | |
1536 | |
1537 When the [group] argument is not given, Vim executes | |
1538 the autocommands for all groups. When the [group] | |
1539 argument is included, Vim executes only the matching | |
1540 autocommands for that group. Note: if you use an | |
1541 undefined group name, Vim gives you an error message. | |
3350 | 1542 *<nomodeline>* |
1543 After applying the autocommands the modelines are | |
1544 processed, so that their settings overrule the | |
1545 settings from autocommands, like what happens when | |
1546 editing a file. This is skipped when the <nomodeline> | |
1547 argument is present. You probably want to use | |
1548 <nomodeline> for events that are not used when loading | |
1549 a buffer, such as |User|. | |
9286
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1550 Processing modelines is also skipped when no |
64035abb986b
commit https://github.com/vim/vim/commit/c95a302a4c42ec8230473cd4a5e0064d0a143aa8
Christian Brabandt <cb@256bit.org>
parents:
8951
diff
changeset
|
1551 matching autocommands were executed. |
7 | 1552 |
1553 *:doautoa* *:doautoall* | |
3342 | 1554 :doautoa[ll] [<nomodeline>] [group] {event} [fname] |
7 | 1555 Like ":doautocmd", but apply the autocommands to each |
24278 | 1556 loaded buffer. The current buffer is done last. |
1557 | |
1558 Note that [fname] is used to select the autocommands, | |
24569 | 1559 not the buffers to which they are applied. Example: > |
1560 augroup mine | |
1561 autocmd! | |
1562 autocmd FileType * echo expand('<amatch>') | |
1563 augroup END | |
1564 doautoall mine FileType Loaded-Buffer | |
1565 < Sourcing this script, you'll see as many | |
1566 "Loaded-Buffer" echoed as there are loaded buffers. | |
24278 | 1567 |
7 | 1568 Careful: Don't use this for autocommands that delete a |
1569 buffer, change to another buffer or change the | |
1570 contents of a buffer; the result is unpredictable. | |
1571 This command is intended for autocommands that set | |
1572 options, change highlighting, and things like that. | |
1573 | |
1574 ============================================================================== | |
40 | 1575 10. Using autocommands *autocmd-use* |
7 | 1576 |
1577 For WRITING FILES there are four possible sets of events. Vim uses only one | |
1578 of these sets for a write command: | |
1579 | |
1580 BufWriteCmd BufWritePre BufWritePost writing the whole buffer | |
1581 FilterWritePre FilterWritePost writing to filter temp file | |
1582 FileAppendCmd FileAppendPre FileAppendPost appending to a file | |
1583 FileWriteCmd FileWritePre FileWritePost any other file write | |
1584 | |
1585 When there is a matching "*Cmd" autocommand, it is assumed it will do the | |
1586 writing. No further writing is done and the other events are not triggered. | |
1587 |Cmd-event| | |
1588 | |
1589 Note that the *WritePost commands should undo any changes to the buffer that | |
1590 were caused by the *WritePre commands; otherwise, writing the file will have | |
1591 the side effect of changing the buffer. | |
1592 | |
1593 Before executing the autocommands, the buffer from which the lines are to be | |
1594 written temporarily becomes the current buffer. Unless the autocommands | |
1595 change the current buffer or delete the previously current buffer, the | |
1596 previously current buffer is made the current buffer again. | |
1597 | |
1598 The *WritePre and *AppendPre autocommands must not delete the buffer from | |
1599 which the lines are to be written. | |
1600 | |
1601 The '[ and '] marks have a special position: | |
1602 - Before the *ReadPre event the '[ mark is set to the line just above where | |
1603 the new lines will be inserted. | |
1604 - Before the *ReadPost event the '[ mark is set to the first line that was | |
1605 just read, the '] mark to the last line. | |
26 | 1606 - Before executing the *WriteCmd, *WritePre and *AppendPre autocommands the '[ |
1607 mark is set to the first line that will be written, the '] mark to the last | |
1608 line. | |
7 | 1609 Careful: '[ and '] change when using commands that change the buffer. |
1610 | |
1611 In commands which expect a file name, you can use "<afile>" for the file name | |
1612 that is being read |:<afile>| (you can also use "%" for the current file | |
1613 name). "<abuf>" can be used for the buffer number of the currently effective | |
14123 | 1614 buffer. This also works for buffers that don't have a name. But it doesn't |
7 | 1615 work for files without a buffer (e.g., with ":r file"). |
1616 | |
1617 *gzip-example* | |
1618 Examples for reading and writing compressed files: > | |
1619 :augroup gzip | |
1620 : autocmd! | |
1621 : autocmd BufReadPre,FileReadPre *.gz set bin | |
1622 : autocmd BufReadPost,FileReadPost *.gz '[,']!gunzip | |
1623 : autocmd BufReadPost,FileReadPost *.gz set nobin | |
1624 : autocmd BufReadPost,FileReadPost *.gz execute ":doautocmd BufReadPost " . expand("%:r") | |
1625 : autocmd BufWritePost,FileWritePost *.gz !mv <afile> <afile>:r | |
1626 : autocmd BufWritePost,FileWritePost *.gz !gzip <afile>:r | |
1627 | |
1628 : autocmd FileAppendPre *.gz !gunzip <afile> | |
1629 : autocmd FileAppendPre *.gz !mv <afile>:r <afile> | |
1630 : autocmd FileAppendPost *.gz !mv <afile> <afile>:r | |
1631 : autocmd FileAppendPost *.gz !gzip <afile>:r | |
1632 :augroup END | |
1633 | |
1634 The "gzip" group is used to be able to delete any existing autocommands with | |
1635 ":autocmd!", for when the file is sourced twice. | |
1636 | |
1637 ("<afile>:r" is the file name without the extension, see |:_%:|) | |
1638 | |
1639 The commands executed for the BufNewFile, BufRead/BufReadPost, BufWritePost, | |
1640 FileAppendPost and VimLeave events do not set or reset the changed flag of the | |
1641 buffer. When you decompress the buffer with the BufReadPost autocommands, you | |
1642 can still exit with ":q". When you use ":undo" in BufWritePost to undo the | |
1643 changes made by BufWritePre commands, you can still do ":q" (this also makes | |
1644 "ZZ" work). If you do want the buffer to be marked as modified, set the | |
1645 'modified' option. | |
1646 | |
1647 To execute Normal mode commands from an autocommand, use the ":normal" | |
1648 command. Use with care! If the Normal mode command is not finished, the user | |
1649 needs to type characters (e.g., after ":normal m" you need to type a mark | |
1650 name). | |
1651 | |
1652 If you want the buffer to be unmodified after changing it, reset the | |
1653 'modified' option. This makes it possible to exit the buffer with ":q" | |
1654 instead of ":q!". | |
1655 | |
1656 *autocmd-nested* *E218* | |
16023 | 1657 By default, autocommands do not nest. For example, if you use ":e" or ":w" in |
1658 an autocommand, Vim does not execute the BufRead and BufWrite autocommands for | |
7 | 1659 those commands. If you do want this, use the "nested" flag for those commands |
1660 in which you want nesting. For example: > | |
16217
81e6940504e8
patch 8.1.1113: making an autocommand trigger once is not so easy
Bram Moolenaar <Bram@vim.org>
parents:
16023
diff
changeset
|
1661 :autocmd FileChangedShell *.c ++nested e! |
7 | 1662 The nesting is limited to 10 levels to get out of recursive loops. |
1663 | |
1664 It's possible to use the ":au" command in an autocommand. This can be a | |
1665 self-modifying command! This can be useful for an autocommand that should | |
1666 execute only once. | |
1667 | |
590 | 1668 If you want to skip autocommands for one command, use the |:noautocmd| command |
1669 modifier or the 'eventignore' option. | |
7 | 1670 |
1671 Note: When reading a file (with ":read file" or with a filter command) and the | |
1672 last line in the file does not have an <EOL>, Vim remembers this. At the next | |
1673 write (with ":write file" or with a filter command), if the same line is | |
1674 written again as the last line in a file AND 'binary' is set, Vim does not | |
1675 supply an <EOL>. This makes a filter command on the just read lines write the | |
1676 same file as was read, and makes a write command on just filtered lines write | |
1677 the same file as was read from the filter. For example, another way to write | |
1678 a compressed file: > | |
1679 | |
1680 :autocmd FileWritePre *.gz set bin|'[,']!gzip | |
1681 :autocmd FileWritePost *.gz undo|set nobin | |
1682 < | |
1683 *autocommand-pattern* | |
1684 You can specify multiple patterns, separated by commas. Here are some | |
1685 examples: > | |
1686 | |
1687 :autocmd BufRead * set tw=79 nocin ic infercase fo=2croq | |
1688 :autocmd BufRead .letter set tw=72 fo=2tcrq | |
1689 :autocmd BufEnter .letter set dict=/usr/lib/dict/words | |
1690 :autocmd BufLeave .letter set dict= | |
1691 :autocmd BufRead,BufNewFile *.c,*.h set tw=0 cin noic | |
1692 :autocmd BufEnter *.c,*.h abbr FOR for (i = 0; i < 3; ++i)<CR>{<CR>}<Esc>O | |
1693 :autocmd BufLeave *.c,*.h unabbr FOR | |
1694 | |
1695 For makefiles (makefile, Makefile, imakefile, makefile.unix, etc.): > | |
1696 | |
1697 :autocmd BufEnter ?akefile* set include=^s\=include | |
1698 :autocmd BufLeave ?akefile* set include& | |
1699 | |
1700 To always start editing C files at the first function: > | |
1701 | |
1702 :autocmd BufRead *.c,*.h 1;/^{ | |
1703 | |
1704 Without the "1;" above, the search would start from wherever the file was | |
1705 entered, rather than from the start of the file. | |
1706 | |
1707 *skeleton* *template* | |
1708 To read a skeleton (template) file when opening a new file: > | |
1709 | |
1710 :autocmd BufNewFile *.c 0r ~/vim/skeleton.c | |
1711 :autocmd BufNewFile *.h 0r ~/vim/skeleton.h | |
1712 :autocmd BufNewFile *.java 0r ~/vim/skeleton.java | |
1713 | |
1714 To insert the current date and time in a *.html file when writing it: > | |
1715 | |
1716 :autocmd BufWritePre,FileWritePre *.html ks|call LastMod()|'s | |
1717 :fun LastMod() | |
1718 : if line("$") > 20 | |
1719 : let l = 20 | |
1720 : else | |
1721 : let l = line("$") | |
1722 : endif | |
1723 : exe "1," . l . "g/Last modified: /s/Last modified: .*/Last modified: " . | |
1724 : \ strftime("%Y %b %d") | |
1725 :endfun | |
1726 | |
1727 You need to have a line "Last modified: <date time>" in the first 20 lines | |
1728 of the file for this to work. Vim replaces <date time> (and anything in the | |
1729 same line after it) with the current date and time. Explanation: | |
1730 ks mark current position with mark 's' | |
1731 call LastMod() call the LastMod() function to do the work | |
1732 's return the cursor to the old position | |
1733 The LastMod() function checks if the file is shorter than 20 lines, and then | |
1734 uses the ":g" command to find lines that contain "Last modified: ". For those | |
1735 lines the ":s" command is executed to replace the existing date with the | |
1736 current one. The ":execute" command is used to be able to use an expression | |
1737 for the ":g" and ":s" commands. The date is obtained with the strftime() | |
1738 function. You can change its argument to get another date string. | |
1739 | |
1740 When entering :autocmd on the command-line, completion of events and command | |
1741 names may be done (with <Tab>, CTRL-D, etc.) where appropriate. | |
1742 | |
1743 Vim executes all matching autocommands in the order that you specify them. | |
1744 It is recommended that your first autocommand be used for all files by using | |
1745 "*" as the file pattern. This means that you can define defaults you like | |
1746 here for any settings, and if there is another matching autocommand it will | |
1747 override these. But if there is no other matching autocommand, then at least | |
1748 your default settings are recovered (if entering this file from another for | |
1749 which autocommands did match). Note that "*" will also match files starting | |
1750 with ".", unlike Unix shells. | |
1751 | |
1752 *autocmd-searchpat* | |
1753 Autocommands do not change the current search patterns. Vim saves the current | |
1754 search patterns before executing autocommands then restores them after the | |
1755 autocommands finish. This means that autocommands do not affect the strings | |
1756 highlighted with the 'hlsearch' option. Within autocommands, you can still | |
1757 use search patterns normally, e.g., with the "n" command. | |
1758 If you want an autocommand to set the search pattern, such that it is used | |
1759 after the autocommand finishes, use the ":let @/ =" command. | |
1760 The search-highlighting cannot be switched off with ":nohlsearch" in an | |
1761 autocommand. Use the 'h' flag in the 'viminfo' option to disable search- | |
1762 highlighting when starting Vim. | |
1763 | |
1764 *Cmd-event* | |
1765 When using one of the "*Cmd" events, the matching autocommands are expected to | |
1061 | 1766 do the file reading, writing or sourcing. This can be used when working with |
1767 a special kind of file, for example on a remote system. | |
7 | 1768 CAREFUL: If you use these events in a wrong way, it may have the effect of |
1769 making it impossible to read or write the matching files! Make sure you test | |
1770 your autocommands properly. Best is to use a pattern that will never match a | |
1771 normal file name, for example "ftp://*". | |
1772 | |
1773 When defining a BufReadCmd it will be difficult for Vim to recover a crashed | |
1774 editing session. When recovering from the original file, Vim reads only those | |
1775 parts of a file that are not found in the swap file. Since that is not | |
1776 possible with a BufReadCmd, use the |:preserve| command to make sure the | |
1777 original file isn't needed for recovery. You might want to do this only when | |
1778 you expect the file to be modified. | |
1779 | |
1061 | 1780 For file read and write commands the |v:cmdarg| variable holds the "++enc=" |
1781 and "++ff=" argument that are effective. These should be used for the command | |
1782 that reads/writes the file. The |v:cmdbang| variable is one when "!" was | |
1783 used, zero otherwise. | |
7 | 1784 |
2377
878562053ba3
Update Fortran indent and syntax file. (Ajit Thakkar)
Bram Moolenaar <bram@vim.org>
parents:
2345
diff
changeset
|
1785 See the $VIMRUNTIME/plugin/netrwPlugin.vim for examples. |
7 | 1786 |
590 | 1787 ============================================================================== |
1788 11. Disabling autocommands *autocmd-disable* | |
1789 | |
1790 To disable autocommands for some time use the 'eventignore' option. Note that | |
1791 this may cause unexpected behavior, make sure you restore 'eventignore' | |
1792 afterwards, using a |:try| block with |:finally|. | |
1793 | |
1794 *:noautocmd* *:noa* | |
1795 To disable autocommands for just one command use the ":noautocmd" command | |
1796 modifier. This will set 'eventignore' to "all" for the duration of the | |
1797 following command. Example: > | |
1798 | |
1799 :noautocmd w fname.gz | |
1800 | |
1801 This will write the file without triggering the autocommands defined by the | |
1802 gzip plugin. | |
1803 | |
16023 | 1804 Note that some autocommands are not triggered right away, but only later. |
1805 This specifically applies to |CursorMoved| and |TextChanged|. | |
1806 | |
40 | 1807 |
14421 | 1808 vim:tw=78:ts=8:noet:ft=help:norl: |