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