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