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