Mercurial > vim
annotate runtime/doc/filetype.txt @ 23047:29c5f168c6fd
Update runtime files
Commit: https://github.com/vim/vim/commit/23515b4ef7580af8b9d3b964a558ab2007cacda5
Author: Bram Moolenaar <Bram@vim.org>
Date: Sun Nov 29 14:36:24 2020 +0100
Update runtime files
| author | Bram Moolenaar <Bram@vim.org> |
|---|---|
| date | Sun, 29 Nov 2020 14:45:04 +0100 |
| parents | a3bb84cd0f59 |
| children | 96206643bd9f |
| rev | line source |
|---|---|
| 22441 | 1 *filetype.txt* For Vim version 8.2. Last change: 2020 Sep 28 |
| 7 | 2 |
| 3 | |
| 4 VIM REFERENCE MANUAL by Bram Moolenaar | |
| 5 | |
| 6 | |
| 7 Filetypes *filetype* *file-type* | |
| 8 | |
| 9 1. Filetypes |filetypes| | |
| 10 2. Filetype plugin |filetype-plugins| | |
| 11 3. Docs for the default filetype plugins. |ftplugin-docs| | |
| 12 | |
| 13 Also see |autocmd.txt|. | |
| 14 | |
| 15 | |
| 16 ============================================================================== | |
| 17 1. Filetypes *filetypes* *file-types* | |
| 18 | |
| 19 Vim can detect the type of file that is edited. This is done by checking the | |
| 20 file name and sometimes by inspecting the contents of the file for specific | |
| 21 text. | |
| 22 | |
| 23 *:filetype* *:filet* | |
| 24 To enable file type detection, use this command in your vimrc: > | |
| 25 :filetype on | |
| 26 Each time a new or existing file is edited, Vim will try to recognize the type | |
| 27 of the file and set the 'filetype' option. This will trigger the FileType | |
| 28 event, which can be used to set the syntax highlighting, set options, etc. | |
| 29 | |
| 30 NOTE: Filetypes and 'compatible' don't work together well, since being Vi | |
| 31 compatible means options are global. Resetting 'compatible' is recommended, | |
| 32 if you didn't do that already. | |
| 33 | |
| 34 Detail: The ":filetype on" command will load one of these files: | |
| 35 Amiga $VIMRUNTIME/filetype.vim | |
| 36 Mac $VIMRUNTIME:filetype.vim | |
| 18972 | 37 MS-Windows $VIMRUNTIME\filetype.vim |
| 7 | 38 Unix $VIMRUNTIME/filetype.vim |
| 39 VMS $VIMRUNTIME/filetype.vim | |
| 40 This file is a Vim script that defines autocommands for the | |
| 41 BufNewFile and BufRead events. If the file type is not found by the | |
| 42 name, the file $VIMRUNTIME/scripts.vim is used to detect it from the | |
| 43 contents of the file. | |
|
12756
3b26420fc639
Long overdue runtime update.
Christian Brabandt <cb@256bit.org>
parents:
11262
diff
changeset
|
44 When the GUI is running or will start soon, the |menu.vim| script is |
| 1125 | 45 also sourced. See |'go-M'| about avoiding that. |
| 7 | 46 |
| 501 | 47 To add your own file types, see |new-filetype| below. To search for help on a |
| 48 filetype prepend "ft-" and optionally append "-syntax", "-indent" or | |
| 49 "-plugin". For example: > | |
| 50 :help ft-vim-indent | |
| 51 :help ft-vim-syntax | |
| 52 :help ft-man-plugin | |
| 7 | 53 |
| 54 If the file type is not detected automatically, or it finds the wrong type, | |
| 55 you can either set the 'filetype' option manually, or add a modeline to your | |
| 1668 | 56 file. Example, for an IDL file use the command: > |
| 7 | 57 :set filetype=idl |
| 501 | 58 |
| 59 or add this |modeline| to the file: | |
| 60 /* vim: set filetype=idl : */ ~ | |
| 61 | |
| 7 | 62 *:filetype-plugin-on* |
| 63 You can enable loading the plugin files for specific file types with: > | |
| 64 :filetype plugin on | |
| 65 If filetype detection was not switched on yet, it will be as well. | |
| 66 This actually loads the file "ftplugin.vim" in 'runtimepath'. | |
| 67 The result is that when a file is edited its plugin file is loaded (if there | |
| 68 is one for the detected filetype). |filetype-plugin| | |
| 69 | |
| 70 *:filetype-plugin-off* | |
| 71 You can disable it again with: > | |
| 72 :filetype plugin off | |
| 73 The filetype detection is not switched off then. But if you do switch off | |
| 74 filetype detection, the plugins will not be loaded either. | |
| 75 This actually loads the file "ftplugof.vim" in 'runtimepath'. | |
| 76 | |
| 77 *:filetype-indent-on* | |
| 78 You can enable loading the indent file for specific file types with: > | |
| 79 :filetype indent on | |
| 80 If filetype detection was not switched on yet, it will be as well. | |
| 81 This actually loads the file "indent.vim" in 'runtimepath'. | |
| 82 The result is that when a file is edited its indent file is loaded (if there | |
| 83 is one for the detected filetype). |indent-expression| | |
| 84 | |
| 85 *:filetype-indent-off* | |
| 86 You can disable it again with: > | |
| 87 :filetype indent off | |
| 88 The filetype detection is not switched off then. But if you do switch off | |
| 89 filetype detection, the indent files will not be loaded either. | |
| 90 This actually loads the file "indoff.vim" in 'runtimepath'. | |
| 22 | 91 This disables auto-indenting for files you will open. It will keep working in |
| 92 already opened files. Reset 'autoindent', 'cindent', 'smartindent' and/or | |
| 93 'indentexpr' to disable indenting in an opened file. | |
| 7 | 94 |
| 95 *:filetype-off* | |
| 96 To disable file type detection, use this command: > | |
| 97 :filetype off | |
| 98 This will keep the flags for "plugin" and "indent", but since no file types | |
| 99 are being detected, they won't work until the next ":filetype on". | |
| 100 | |
| 101 | |
| 102 Overview: *:filetype-overview* | |
| 103 | |
| 104 command detection plugin indent ~ | |
| 105 :filetype on on unchanged unchanged | |
| 106 :filetype off off unchanged unchanged | |
| 107 :filetype plugin on on on unchanged | |
| 108 :filetype plugin off unchanged off unchanged | |
| 109 :filetype indent on on unchanged on | |
| 110 :filetype indent off unchanged unchanged off | |
| 111 :filetype plugin indent on on on on | |
| 112 :filetype plugin indent off unchanged off off | |
| 113 | |
| 114 To see the current status, type: > | |
| 115 :filetype | |
| 116 The output looks something like this: > | |
| 117 filetype detection:ON plugin:ON indent:OFF | |
| 118 | |
| 119 The file types are also used for syntax highlighting. If the ":syntax on" | |
| 120 command is used, the file type detection is installed too. There is no need | |
| 121 to do ":filetype on" after ":syntax on". | |
| 122 | |
| 1624 | 123 To disable one of the file types, add a line in your filetype file, see |
| 7 | 124 |remove-filetype|. |
| 125 | |
| 126 *filetype-detect* | |
| 127 To detect the file type again: > | |
| 128 :filetype detect | |
| 129 Use this if you started with an empty file and typed text that makes it | |
| 130 possible to detect the file type. For example, when you entered this in a | |
| 131 shell script: "#!/bin/csh". | |
| 132 When filetype detection was off, it will be enabled first, like the "on" | |
| 133 argument was used. | |
| 134 | |
| 135 *filetype-overrule* | |
| 136 When the same extension is used for two filetypes, Vim tries to guess what | |
| 137 kind of file it is. This doesn't always work. A number of global variables | |
| 138 can be used to overrule the filetype used for certain extensions: | |
| 139 | |
| 140 file name variable ~ | |
| 501 | 141 *.asa g:filetype_asa |ft-aspvbs-syntax| |ft-aspperl-syntax| |
| 142 *.asp g:filetype_asp |ft-aspvbs-syntax| |ft-aspperl-syntax| | |
| 143 *.asm g:asmsyntax |ft-asm-syntax| | |
| 7 | 144 *.prg g:filetype_prg |
| 145 *.pl g:filetype_pl | |
| 146 *.inc g:filetype_inc | |
| 501 | 147 *.w g:filetype_w |ft-cweb-syntax| |
| 148 *.i g:filetype_i |ft-progress-syntax| | |
| 149 *.p g:filetype_p |ft-pascal-syntax| | |
| 150 *.sh g:bash_is_sh |ft-sh-syntax| | |
| 798 | 151 *.tex g:tex_flavor |ft-tex-plugin| |
| 7 | 152 |
| 153 *filetype-ignore* | |
| 154 To avoid that certain files are being inspected, the g:ft_ignore_pat variable | |
| 155 is used. The default value is set like this: > | |
| 156 :let g:ft_ignore_pat = '\.\(Z\|gz\|bz2\|zip\|tgz\)$' | |
| 157 This means that the contents of compressed files are not inspected. | |
| 158 | |
| 159 *new-filetype* | |
| 22 | 160 If a file type that you want to use is not detected yet, there are four ways |
| 10 | 161 to add it. In any way, it's better not to modify the $VIMRUNTIME/filetype.vim |
| 7 | 162 file. It will be overwritten when installing a new version of Vim. |
| 163 | |
| 164 A. If you want to overrule all default file type checks. | |
| 165 This works by writing one file for each filetype. The disadvantage is that | |
| 21825 | 166 there can be many files. The advantage is that you can simply drop this |
| 167 file in the right directory to make it work. | |
| 22 | 168 *ftdetect* |
| 7 | 169 1. Create your user runtime directory. You would normally use the first |
| 170 item of the 'runtimepath' option. Then create the directory "ftdetect" | |
| 171 inside it. Example for Unix: > | |
| 172 :!mkdir ~/.vim | |
| 173 :!mkdir ~/.vim/ftdetect | |
| 174 < | |
| 175 2. Create a file that contains an autocommand to detect the file type. | |
| 176 Example: > | |
| 177 au BufRead,BufNewFile *.mine set filetype=mine | |
| 178 < Note that there is no "augroup" command, this has already been done | |
| 179 when sourcing your file. You could also use the pattern "*" and then | |
| 180 check the contents of the file to recognize it. | |
| 181 Write this file as "mine.vim" in the "ftdetect" directory in your user | |
| 182 runtime directory. For example, for Unix: > | |
| 183 :w ~/.vim/ftdetect/mine.vim | |
| 184 | |
| 185 < 3. To use the new filetype detection you must restart Vim. | |
| 186 | |
| 187 The files in the "ftdetect" directory are used after all the default | |
| 530 | 188 checks, thus they can overrule a previously detected file type. But you |
| 189 can also use |:setfiletype| to keep a previously detected filetype. | |
| 7 | 190 |
| 191 B. If you want to detect your file after the default file type checks. | |
| 192 | |
| 193 This works like A above, but instead of setting 'filetype' unconditionally | |
| 194 use ":setfiletype". This will only set 'filetype' if no file type was | |
| 195 detected yet. Example: > | |
| 196 au BufRead,BufNewFile *.txt setfiletype text | |
| 197 < | |
| 198 You can also use the already detected file type in your command. For | |
| 199 example, to use the file type "mypascal" when "pascal" has been detected: > | |
| 200 au BufRead,BufNewFile * if &ft == 'pascal' | set ft=mypascal | |
| 201 | endif | |
| 202 | |
| 203 C. If your file type can be detected by the file name. | |
| 204 1. Create your user runtime directory. You would normally use the first | |
| 205 item of the 'runtimepath' option. Example for Unix: > | |
| 206 :!mkdir ~/.vim | |
| 207 < | |
| 208 2. Create a file that contains autocommands to detect the file type. | |
| 209 Example: > | |
| 210 " my filetype file | |
| 211 if exists("did_load_filetypes") | |
| 212 finish | |
| 213 endif | |
| 214 augroup filetypedetect | |
| 215 au! BufRead,BufNewFile *.mine setfiletype mine | |
| 216 au! BufRead,BufNewFile *.xyz setfiletype drawing | |
| 217 augroup END | |
| 218 < Write this file as "filetype.vim" in your user runtime directory. For | |
| 219 example, for Unix: > | |
| 220 :w ~/.vim/filetype.vim | |
| 221 | |
| 222 < 3. To use the new filetype detection you must restart Vim. | |
| 223 | |
| 224 Your filetype.vim will be sourced before the default FileType autocommands | |
| 225 have been installed. Your autocommands will match first, and the | |
| 226 ":setfiletype" command will make sure that no other autocommands will set | |
| 227 'filetype' after this. | |
| 228 *new-filetype-scripts* | |
| 229 D. If your filetype can only be detected by inspecting the contents of the | |
| 230 file. | |
| 231 | |
| 232 1. Create your user runtime directory. You would normally use the first | |
| 233 item of the 'runtimepath' option. Example for Unix: > | |
| 234 :!mkdir ~/.vim | |
| 235 < | |
| 236 2. Create a vim script file for doing this. Example: > | |
| 237 if did_filetype() " filetype already set.. | |
| 238 finish " ..don't do these checks | |
| 239 endif | |
| 240 if getline(1) =~ '^#!.*\<mine\>' | |
| 241 setfiletype mine | |
| 242 elseif getline(1) =~? '\<drawing\>' | |
| 243 setfiletype drawing | |
| 244 endif | |
| 245 < See $VIMRUNTIME/scripts.vim for more examples. | |
| 246 Write this file as "scripts.vim" in your user runtime directory. For | |
| 247 example, for Unix: > | |
| 248 :w ~/.vim/scripts.vim | |
| 249 < | |
| 250 3. The detection will work right away, no need to restart Vim. | |
| 251 | |
| 252 Your scripts.vim is loaded before the default checks for file types, which | |
| 253 means that your rules override the default rules in | |
| 254 $VIMRUNTIME/scripts.vim. | |
| 255 | |
| 256 *remove-filetype* | |
| 257 If a file type is detected that is wrong for you, install a filetype.vim or | |
| 258 scripts.vim to catch it (see above). You can set 'filetype' to a non-existing | |
| 259 name to avoid that it will be set later anyway: > | |
| 260 :set filetype=ignored | |
| 261 | |
| 262 If you are setting up a system with many users, and you don't want each user | |
| 263 to add/remove the same filetypes, consider writing the filetype.vim and | |
| 264 scripts.vim files in a runtime directory that is used for everybody. Check | |
| 265 the 'runtimepath' for a directory to use. If there isn't one, set | |
| 266 'runtimepath' in the |system-vimrc|. Be careful to keep the default | |
| 267 directories! | |
| 268 | |
| 269 | |
| 270 *autocmd-osfiletypes* | |
| 2908 | 271 NOTE: this code is currently disabled, as the RISC OS implementation was |
| 272 removed. In the future this will use the 'filetype' option. | |
| 273 | |
| 7 | 274 On operating systems which support storing a file type with the file, you can |
| 275 specify that an autocommand should only be executed if the file is of a | |
| 276 certain type. | |
| 277 | |
| 278 The actual type checking depends on which platform you are running Vim | |
| 279 on; see your system's documentation for details. | |
| 280 | |
| 281 To use osfiletype checking in an autocommand you should put a list of types to | |
| 282 match in angle brackets in place of a pattern, like this: > | |
| 283 | |
| 284 :au BufRead *.html,<&faf;HTML> runtime! syntax/html.vim | |
| 285 | |
| 286 This will match: | |
| 287 | |
| 1668 | 288 - Any file whose name ends in ".html" |
| 289 - Any file whose type is "&faf" or "HTML", where the meaning of these types | |
| 7 | 290 depends on which version of Vim you are using. |
| 291 Unknown types are considered NOT to match. | |
| 292 | |
| 293 You can also specify a type and a pattern at the same time (in which case they | |
| 294 must both match): > | |
| 295 | |
| 296 :au BufRead <&fff>diff* | |
| 297 | |
| 1668 | 298 This will match files of type "&fff" whose names start with "diff". |
| 7 | 299 |
| 300 | |
| 301 *plugin-details* | |
| 302 The "plugin" directory can be in any of the directories in the 'runtimepath' | |
| 303 option. All of these directories will be searched for plugins and they are | |
| 304 all loaded. For example, if this command: > | |
| 305 | |
| 306 set runtimepath | |
| 307 | |
| 1125 | 308 produces this output: |
| 7 | 309 |
| 19116 | 310 runtimepath=/etc/vim,~/.vim,/usr/local/share/vim/vim82 ~ |
| 7 | 311 |
| 1125 | 312 then Vim will load all plugins in these directories and below: |
| 7 | 313 |
| 1125 | 314 /etc/vim/plugin/ ~ |
| 315 ~/.vim/plugin/ ~ | |
| 19116 | 316 /usr/local/share/vim/vim82/plugin/ ~ |
| 7 | 317 |
| 318 Note that the last one is the value of $VIMRUNTIME which has been expanded. | |
| 319 | |
| 13735 | 320 Note that when using a plugin manager or |packages| many directories will be |
|
14249
4543777545a3
Updated runtime and language files.
Christian Brabandt <cb@256bit.org>
parents:
13963
diff
changeset
|
321 added to 'runtimepath'. These plugins each require their own directory, don't |
|
4543777545a3
Updated runtime and language files.
Christian Brabandt <cb@256bit.org>
parents:
13963
diff
changeset
|
322 put them directly in ~/.vim/plugin. |
| 13735 | 323 |
| 7 | 324 What if it looks like your plugin is not being loaded? You can find out what |
| 325 happens when Vim starts up by using the |-V| argument: > | |
| 1125 | 326 |
| 327 vim -V2 | |
| 328 | |
| 7 | 329 You will see a lot of messages, in between them is a remark about loading the |
| 1125 | 330 plugins. It starts with: |
| 331 | |
| 332 Searching for "plugin/**/*.vim" in ~ | |
| 333 | |
| 7 | 334 There you can see where Vim looks for your plugin scripts. |
| 335 | |
| 336 ============================================================================== | |
| 337 2. Filetype plugin *filetype-plugins* | |
| 338 | |
| 339 When loading filetype plugins has been enabled |:filetype-plugin-on|, options | |
| 340 will be set and mappings defined. These are all local to the buffer, they | |
| 341 will not be used for other files. | |
| 342 | |
| 343 Defining mappings for a filetype may get in the way of the mappings you | |
| 344 define yourself. There are a few ways to avoid this: | |
| 345 1. Set the "maplocalleader" variable to the key sequence you want the mappings | |
| 346 to start with. Example: > | |
| 347 :let maplocalleader = "," | |
| 348 < All mappings will then start with a comma instead of the default, which | |
| 349 is a backslash. Also see |<LocalLeader>|. | |
| 350 | |
| 351 2. Define your own mapping. Example: > | |
| 352 :map ,p <Plug>MailQuote | |
| 353 < You need to check the description of the plugin file below for the | |
| 354 functionality it offers and the string to map to. | |
| 355 You need to define your own mapping before the plugin is loaded (before | |
| 356 editing a file of that type). The plugin will then skip installing the | |
| 357 default mapping. | |
| 11262 | 358 *no_mail_maps* |
| 7 | 359 3. Disable defining mappings for a specific filetype by setting a variable, |
| 360 which contains the name of the filetype. For the "mail" filetype this | |
| 361 would be: > | |
| 362 :let no_mail_maps = 1 | |
| 11262 | 363 < *no_plugin_maps* |
| 7 | 364 4. Disable defining mappings for all filetypes by setting a variable: > |
| 365 :let no_plugin_maps = 1 | |
| 366 < | |
| 367 | |
| 368 *ftplugin-overrule* | |
| 369 If a global filetype plugin does not do exactly what you want, there are three | |
| 370 ways to change this: | |
| 371 | |
| 372 1. Add a few settings. | |
| 373 You must create a new filetype plugin in a directory early in | |
| 374 'runtimepath'. For Unix, for example you could use this file: > | |
| 375 vim ~/.vim/ftplugin/fortran.vim | |
| 376 < You can set those settings and mappings that you would like to add. Note | |
| 377 that the global plugin will be loaded after this, it may overrule the | |
| 378 settings that you do here. If this is the case, you need to use one of the | |
| 379 following two methods. | |
| 380 | |
| 381 2. Make a copy of the plugin and change it. | |
| 382 You must put the copy in a directory early in 'runtimepath'. For Unix, for | |
| 383 example, you could do this: > | |
| 384 cp $VIMRUNTIME/ftplugin/fortran.vim ~/.vim/ftplugin/fortran.vim | |
| 385 < Then you can edit the copied file to your liking. Since the b:did_ftplugin | |
| 386 variable will be set, the global plugin will not be loaded. | |
| 387 A disadvantage of this method is that when the distributed plugin gets | |
| 388 improved, you will have to copy and modify it again. | |
| 389 | |
| 390 3. Overrule the settings after loading the global plugin. | |
| 391 You must create a new filetype plugin in a directory from the end of | |
| 392 'runtimepath'. For Unix, for example, you could use this file: > | |
| 393 vim ~/.vim/after/ftplugin/fortran.vim | |
| 394 < In this file you can change just those settings that you want to change. | |
| 395 | |
| 396 ============================================================================== | |
| 397 3. Docs for the default filetype plugins. *ftplugin-docs* | |
| 398 | |
| 399 | |
| 22441 | 400 AWK *ft-awk-plugin* |
| 401 | |
| 402 Support for features specific to GNU Awk, like @include, can be enabled by | |
| 403 setting: > | |
| 404 let g:awk_is_gawk = 1 | |
| 405 | |
| 406 | |
| 501 | 407 CHANGELOG *ft-changelog-plugin* |
| 7 | 408 |
| 237 | 409 Allows for easy entrance of Changelog entries in Changelog files. There are |
| 7 | 410 some commands, mappings, and variables worth exploring: |
| 411 | |
| 412 Options: | |
| 413 'comments' is made empty to not mess up formatting. | |
| 414 'textwidth' is set to 78, which is standard. | |
| 415 'formatoptions' the 't' flag is added to wrap when inserting text. | |
| 416 | |
| 417 Commands: | |
| 418 NewChangelogEntry Adds a new Changelog entry in an intelligent fashion | |
| 419 (see below). | |
| 420 | |
| 421 Local mappings: | |
| 422 <Leader>o Starts a new Changelog entry in an equally intelligent | |
| 423 fashion (see below). | |
| 424 | |
| 425 Global mappings: | |
| 426 NOTE: The global mappings are accessed by sourcing the | |
| 427 ftplugin/changelog.vim file first, e.g. with > | |
| 497 | 428 runtime ftplugin/changelog.vim |
| 7 | 429 < in your |.vimrc|. |
| 430 <Leader>o Switches to the ChangeLog buffer opened for the | |
| 431 current directory, or opens it in a new buffer if it | |
| 432 exists in the current directory. Then it does the | |
| 433 same as the local <Leader>o described above. | |
| 434 | |
| 435 Variables: | |
| 1226 | 436 g:changelog_timeformat Deprecated; use g:changelog_dateformat instead. |
| 437 g:changelog_dateformat The date (and time) format used in ChangeLog entries. | |
| 7 | 438 The format accepted is the same as for the |
| 439 |strftime()| function. | |
| 440 The default is "%Y-%m-%d" which is the standard format | |
| 441 for many ChangeLog layouts. | |
| 442 g:changelog_username The name and email address of the user. | |
| 443 The default is deduced from environment variables and | |
| 444 system files. It searches /etc/passwd for the comment | |
| 445 part of the current user, which informally contains | |
| 446 the real name of the user up to the first separating | |
| 447 comma. then it checks the $NAME environment variable | |
| 448 and finally runs `whoami` and `hostname` to build an | |
| 449 email address. The final form is > | |
| 450 Full Name <user@host> | |
| 451 < | |
| 452 g:changelog_new_date_format | |
| 453 The format to use when creating a new date-entry. | |
| 454 The following table describes special tokens in the | |
| 455 string: | |
| 456 %% insert a single '%' character | |
| 457 %d insert the date from above | |
| 458 %u insert the user from above | |
| 5568 | 459 %p insert result of b:changelog_entry_prefix |
| 7 | 460 %c where to position cursor when done |
| 5568 | 461 The default is "%d %u\n\n\t* %p%c\n\n", which produces |
| 7 | 462 something like (| is where cursor will be, unless at |
| 463 the start of the line where it denotes the beginning | |
| 464 of the line) > | |
| 465 |2003-01-14 Full Name <user@host> | |
| 466 | | |
| 5568 | 467 | * prefix| |
| 7 | 468 < |
| 469 g:changelog_new_entry_format | |
| 470 The format used when creating a new entry. | |
| 471 The following table describes special tokens in the | |
| 472 string: | |
| 5568 | 473 %p insert result of b:changelog_entry_prefix |
| 7 | 474 %c where to position cursor when done |
| 475 The default is "\t*%c", which produces something | |
| 476 similar to > | |
| 5568 | 477 | * prefix| |
| 7 | 478 < |
| 479 g:changelog_date_entry_search | |
| 480 The search pattern to use when searching for a | |
| 481 date-entry. | |
| 482 The same tokens that can be used for | |
| 483 g:changelog_new_date_format can be used here as well. | |
| 484 The default is '^\s*%d\_s*%u' which finds lines | |
| 485 matching the form > | |
| 486 |2003-01-14 Full Name <user@host> | |
| 487 < and some similar formats. | |
| 488 | |
| 1226 | 489 g:changelog_date_end_entry_search |
| 490 The search pattern to use when searching for the end | |
| 491 of a date-entry. | |
| 492 The same tokens that can be used for | |
| 493 g:changelog_new_date_format can be used here as well. | |
| 494 The default is '^\s*$' which finds lines that contain | |
| 495 only whitespace or are completely empty. | |
| 496 | |
| 1698 | 497 b:changelog_name *b:changelog_name* |
| 498 Name of the ChangeLog file to look for. | |
| 499 The default is 'ChangeLog'. | |
| 500 | |
| 501 b:changelog_path | |
| 502 Path of the ChangeLog to use for the current buffer. | |
| 503 The default is empty, thus looking for a file named | |
| 504 |b:changelog_name| in the same directory as the | |
| 505 current buffer. If not found, the parent directory of | |
| 506 the current buffer is searched. This continues | |
| 507 recursively until a file is found or there are no more | |
| 508 parent directories to search. | |
| 509 | |
| 510 b:changelog_entry_prefix | |
| 511 Name of a function to call to generate a prefix to a | |
| 512 new entry. This function takes no arguments and | |
| 513 should return a string containing the prefix. | |
| 514 Returning an empty prefix is fine. | |
| 515 The default generates the shortest path between the | |
| 516 ChangeLog's pathname and the current buffers pathname. | |
| 517 In the future, it will also be possible to use other | |
| 518 variable contexts for this variable, for example, g:. | |
| 519 | |
| 7 | 520 The Changelog entries are inserted where they add the least amount of text. |
| 521 After figuring out the current date and user, the file is searched for an | |
| 522 entry beginning with the current date and user and if found adds another item | |
| 237 | 523 under it. If not found, a new entry and item is prepended to the beginning of |
| 7 | 524 the Changelog. |
| 525 | |
| 526 | |
| 501 | 527 FORTRAN *ft-fortran-plugin* |
| 7 | 528 |
| 529 Options: | |
| 530 'expandtab' is switched on to avoid tabs as required by the Fortran | |
| 531 standards unless the user has set fortran_have_tabs in .vimrc. | |
| 532 'textwidth' is set to 72 for fixed source format as required by the | |
| 533 Fortran standards and to 80 for free source format. | |
| 534 'formatoptions' is set to break code and comment lines and to preserve long | |
| 237 | 535 lines. You can format comments with |gq|. |
| 7 | 536 For further discussion of fortran_have_tabs and the method used for the |
| 501 | 537 detection of source format see |ft-fortran-syntax|. |
| 7 | 538 |
| 539 | |
| 1624 | 540 GIT COMMIT *ft-gitcommit-plugin* |
| 541 | |
| 542 One command, :DiffGitCached, is provided to show a diff of the current commit | |
| 543 in the preview window. It is equivalent to calling "git diff --cached" plus | |
| 544 any arguments given to the command. | |
| 545 | |
| 546 | |
| 501 | 547 MAIL *ft-mail-plugin* |
| 7 | 548 |
| 549 Options: | |
| 550 'modeline' is switched off to avoid the danger of trojan horses, and to | |
| 551 avoid that a Subject line with "Vim:" in it will cause an | |
| 552 error message. | |
| 553 'textwidth' is set to 72. This is often recommended for e-mail. | |
| 554 'formatoptions' is set to break text lines and to repeat the comment leader | |
| 555 in new lines, so that a leading ">" for quotes is repeated. | |
| 556 You can also format quoted text with |gq|. | |
| 557 | |
| 558 Local mappings: | |
| 559 <LocalLeader>q or \\MailQuote | |
| 560 Quotes the text selected in Visual mode, or from the cursor position | |
| 561 to the end of the file in Normal mode. This means "> " is inserted in | |
| 562 each line. | |
| 563 | |
|
7315
444efa5f5015
commit https://github.com/vim/vim/commit/2c5e8e80eacf491d4f266983f534a77776c7ae83
Christian Brabandt <cb@256bit.org>
parents:
7272
diff
changeset
|
564 MAN *ft-man-plugin* *:Man* *man.vim* |
| 7 | 565 |
| 23047 | 566 This plugin displays a manual page in a nice way. See |find-manpage| in the |
| 567 user manual for more information. | |
| 7 | 568 |
| 23047 | 569 To start using the |:Man| command before any manual page has been loaded, |
| 570 source this script from your startup |vimrc| file: > | |
| 7 | 571 runtime ftplugin/man.vim |
| 572 | |
| 573 Options: | |
| 23047 | 574 'iskeyword' The '.' character is added to support the use of CTRL-] on the |
| 7 | 575 manual page name. |
| 576 | |
| 577 Commands: | |
| 578 Man {name} Display the manual page for {name} in a window. | |
| 579 Man {number} {name} | |
| 580 Display the manual page for {name} in a section {number}. | |
| 581 | |
| 582 Global mapping: | |
| 583 <Leader>K Displays the manual page for the word under the cursor. | |
| 23047 | 584 <Plug>ManPreGetPage |
| 585 idem, allows for using a mapping: > | |
| 586 nmap <F1> <Plug>ManPreGetPage | |
| 7 | 587 |
| 588 Local mappings: | |
| 589 CTRL-] Jump to the manual page for the word under the cursor. | |
| 590 CTRL-T Jump back to the previous manual page. | |
| 23047 | 591 q Same as the |:quit| command. |
|
7272
17333ebd2bbd
commit https://github.com/vim/vim/commit/d042dc825c9b97dacd84d4728f88300da4d5b6b9
Christian Brabandt <cb@256bit.org>
parents:
5568
diff
changeset
|
592 |
|
9344
33c1b85d408c
commit https://github.com/vim/vim/commit/802a0d902fca423acb15f835d7b09183883d79a0
Christian Brabandt <cb@256bit.org>
parents:
9116
diff
changeset
|
593 To use a vertical split instead of horizontal: > |
|
33c1b85d408c
commit https://github.com/vim/vim/commit/802a0d902fca423acb15f835d7b09183883d79a0
Christian Brabandt <cb@256bit.org>
parents:
9116
diff
changeset
|
594 let g:ft_man_open_mode = 'vert' |
|
33c1b85d408c
commit https://github.com/vim/vim/commit/802a0d902fca423acb15f835d7b09183883d79a0
Christian Brabandt <cb@256bit.org>
parents:
9116
diff
changeset
|
595 To use a new tab: > |
|
33c1b85d408c
commit https://github.com/vim/vim/commit/802a0d902fca423acb15f835d7b09183883d79a0
Christian Brabandt <cb@256bit.org>
parents:
9116
diff
changeset
|
596 let g:ft_man_open_mode = 'tab' |
|
33c1b85d408c
commit https://github.com/vim/vim/commit/802a0d902fca423acb15f835d7b09183883d79a0
Christian Brabandt <cb@256bit.org>
parents:
9116
diff
changeset
|
597 |
| 23047 | 598 To enable |folding|, use this: > |
| 599 let g:ft_man_folding_enable = 1 | |
| 600 If you do not like the default folding, use an |autocommand| to add your desired | |
|
7384
aea5ebf352c4
commit https://github.com/vim/vim/commit/256972a9849b5d575b62a6a71be5b6934b5b0e8b
Christian Brabandt <cb@256bit.org>
parents:
7315
diff
changeset
|
601 folding style instead. For example: > |
| 23047 | 602 autocmd FileType man setlocal foldmethod=indent foldenable |
| 7 | 603 |
| 18186 | 604 If you would like :Man {number} {name} to behave like man {number} {name} by |
| 605 not running man {name} if no page is found, then use this: > | |
| 606 let g:ft_man_no_sect_fallback = 1 | |
| 607 | |
|
9116
bc38030aec7d
commit https://github.com/vim/vim/commit/26852128a2b713ef49341a0c18daba928444e7eb
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
608 You may also want to set 'keywordprg' to make the |K| command open a manual |
|
bc38030aec7d
commit https://github.com/vim/vim/commit/26852128a2b713ef49341a0c18daba928444e7eb
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
609 page in a Vim window: > |
|
bc38030aec7d
commit https://github.com/vim/vim/commit/26852128a2b713ef49341a0c18daba928444e7eb
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
610 set keywordprg=:Man |
|
bc38030aec7d
commit https://github.com/vim/vim/commit/26852128a2b713ef49341a0c18daba928444e7eb
Christian Brabandt <cb@256bit.org>
parents:
9041
diff
changeset
|
611 |
| 7 | 612 |
|
9041
34c45ee4210d
commit https://github.com/vim/vim/commit/06481427005a9dae39721087df94855f7d4d1feb
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
613 MANPAGER *manpager.vim* |
|
34c45ee4210d
commit https://github.com/vim/vim/commit/06481427005a9dae39721087df94855f7d4d1feb
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
614 |
| 23047 | 615 The |:Man| command allows you to turn Vim into a manpager (that syntax highlights |
|
9041
34c45ee4210d
commit https://github.com/vim/vim/commit/06481427005a9dae39721087df94855f7d4d1feb
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
616 manpages and follows linked manpages on hitting CTRL-]). |
|
34c45ee4210d
commit https://github.com/vim/vim/commit/06481427005a9dae39721087df94855f7d4d1feb
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
617 |
| 12826 | 618 For bash,zsh,ksh or dash, add to the config file (.bashrc,.zshrc, ...) |
|
9041
34c45ee4210d
commit https://github.com/vim/vim/commit/06481427005a9dae39721087df94855f7d4d1feb
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
619 |
| 13231 | 620 export MANPAGER="vim -M +MANPAGER -" |
|
9041
34c45ee4210d
commit https://github.com/vim/vim/commit/06481427005a9dae39721087df94855f7d4d1feb
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
621 |
| 12826 | 622 For (t)csh, add to the config file |
| 623 | |
| 13231 | 624 setenv MANPAGER "vim -M +MANPAGER -" |
| 12826 | 625 |
| 626 For fish, add to the config file | |
| 627 | |
| 13231 | 628 set -x MANPAGER "vim -M +MANPAGER -" |
|
9041
34c45ee4210d
commit https://github.com/vim/vim/commit/06481427005a9dae39721087df94855f7d4d1feb
Christian Brabandt <cb@256bit.org>
parents:
7384
diff
changeset
|
629 |
| 1624 | 630 PDF *ft-pdf-plugin* |
| 631 | |
| 632 Two maps, <C-]> and <C-T>, are provided to simulate a tag stack for navigating | |
| 633 the PDF. The following are treated as tags: | |
| 634 | |
| 635 - The byte offset after "startxref" to the xref table | |
| 636 - The byte offset after the /Prev key in the trailer to an earlier xref table | |
| 637 - A line of the form "0123456789 00000 n" in the xref table | |
| 638 - An object reference like "1 0 R" anywhere in the PDF | |
| 639 | |
| 640 These maps can be disabled with > | |
| 641 :let g:no_pdf_maps = 1 | |
| 642 < | |
| 643 | |
|
10186
a5ef9968638c
commit https://github.com/vim/vim/commit/7e1479b86c590a66b63a274c079b7f18907d45a4
Christian Brabandt <cb@256bit.org>
parents:
9344
diff
changeset
|
644 PYTHON *ft-python-plugin* *PEP8* |
|
a5ef9968638c
commit https://github.com/vim/vim/commit/7e1479b86c590a66b63a274c079b7f18907d45a4
Christian Brabandt <cb@256bit.org>
parents:
9344
diff
changeset
|
645 |
|
a5ef9968638c
commit https://github.com/vim/vim/commit/7e1479b86c590a66b63a274c079b7f18907d45a4
Christian Brabandt <cb@256bit.org>
parents:
9344
diff
changeset
|
646 By default the following options are set, in accordance with PEP8: > |
|
a5ef9968638c
commit https://github.com/vim/vim/commit/7e1479b86c590a66b63a274c079b7f18907d45a4
Christian Brabandt <cb@256bit.org>
parents:
9344
diff
changeset
|
647 |
|
a5ef9968638c
commit https://github.com/vim/vim/commit/7e1479b86c590a66b63a274c079b7f18907d45a4
Christian Brabandt <cb@256bit.org>
parents:
9344
diff
changeset
|
648 setlocal expandtab shiftwidth=4 softtabstop=4 tabstop=8 |
|
a5ef9968638c
commit https://github.com/vim/vim/commit/7e1479b86c590a66b63a274c079b7f18907d45a4
Christian Brabandt <cb@256bit.org>
parents:
9344
diff
changeset
|
649 |
| 14637 | 650 To disable this behavior, set the following variable in your vimrc: > |
| 13231 | 651 |
|
10186
a5ef9968638c
commit https://github.com/vim/vim/commit/7e1479b86c590a66b63a274c079b7f18907d45a4
Christian Brabandt <cb@256bit.org>
parents:
9344
diff
changeset
|
652 let g:python_recommended_style = 0 |
|
a5ef9968638c
commit https://github.com/vim/vim/commit/7e1479b86c590a66b63a274c079b7f18907d45a4
Christian Brabandt <cb@256bit.org>
parents:
9344
diff
changeset
|
653 |
|
a5ef9968638c
commit https://github.com/vim/vim/commit/7e1479b86c590a66b63a274c079b7f18907d45a4
Christian Brabandt <cb@256bit.org>
parents:
9344
diff
changeset
|
654 |
| 17433 | 655 QF QUICKFIX *qf.vim* *ft-qf-plugin* |
| 656 | |
| 657 The "qf" filetype is used for the quickfix window, see |quickfix-window|. | |
| 658 | |
| 659 The quickfix filetype plugin includes configuration for displaying the command | |
| 660 that produced the quickfix list in the |status-line|. To disable this setting, | |
| 661 configure as follows: > | |
| 662 :let g:qf_disable_statusline = 1 | |
| 663 | |
| 664 | |
| 14637 | 665 R MARKDOWN *ft-rmd-plugin* |
| 666 | |
| 667 By default ftplugin/html.vim is not sourced. If you want it sourced, add to | |
| 668 your |vimrc|: > | |
| 669 let rmd_include_html = 1 | |
| 670 | |
| 671 The 'formatexpr' option is set dynamically with different values for R code | |
| 672 and for Markdown code. If you prefer that 'formatexpr' is not set, add to your | |
| 673 |vimrc|: > | |
| 674 let rmd_dynamic_comments = 0 | |
| 675 | |
| 676 | |
| 677 R RESTRUCTURED TEXT *ft-rrst-plugin* | |
| 678 | |
| 679 The 'formatexpr' option is set dynamically with different values for R code | |
| 680 and for ReStructured text. If you prefer that 'formatexpr' is not set, add to | |
| 681 your |vimrc|: > | |
| 682 let rrst_dynamic_comments = 0 | |
| 683 | |
| 684 | |
| 15878 | 685 RESTRUCTUREDTEXT *ft-rst-plugin* |
| 686 | |
| 687 The following formatting setting are optionally available: > | |
| 688 setlocal expandtab shiftwidth=3 softtabstop=3 tabstop=8 | |
| 689 | |
| 690 To enable this behavior, set the following variable in your vimrc: > | |
| 691 let g:rst_style = 1 | |
| 692 | |
| 693 | |
| 501 | 694 RPM SPEC *ft-spec-plugin* |
| 7 | 695 |
| 696 Since the text for this plugin is rather long it has been put in a separate | |
| 697 file: |pi_spec.txt|. | |
| 698 | |
| 699 | |
|
11229
146a1e213b60
Update runtime files. Add Rust support.
Christian Brabandt <cb@256bit.org>
parents:
10548
diff
changeset
|
700 RUST *ft-rust* |
|
146a1e213b60
Update runtime files. Add Rust support.
Christian Brabandt <cb@256bit.org>
parents:
10548
diff
changeset
|
701 |
|
146a1e213b60
Update runtime files. Add Rust support.
Christian Brabandt <cb@256bit.org>
parents:
10548
diff
changeset
|
702 Since the text for this plugin is rather long it has been put in a separate |
|
146a1e213b60
Update runtime files. Add Rust support.
Christian Brabandt <cb@256bit.org>
parents:
10548
diff
changeset
|
703 file: |ft_rust.txt|. |
|
146a1e213b60
Update runtime files. Add Rust support.
Christian Brabandt <cb@256bit.org>
parents:
10548
diff
changeset
|
704 |
|
146a1e213b60
Update runtime files. Add Rust support.
Christian Brabandt <cb@256bit.org>
parents:
10548
diff
changeset
|
705 |
| 720 | 706 SQL *ft-sql* |
| 707 | |
| 708 Since the text for this plugin is rather long it has been put in a separate | |
| 1624 | 709 file: |ft_sql.txt|. |
| 720 | 710 |
| 711 | |
|
4681
2eb30f341e8d
Updated runtime files and translations.
Bram Moolenaar <bram@vim.org>
parents:
2908
diff
changeset
|
712 TEX *ft-tex-plugin* *g:tex_flavor* |
| 798 | 713 |
| 714 If the first line of a *.tex file has the form > | |
| 715 %&<format> | |
| 716 then this determined the file type: plaintex (for plain TeX), context (for | |
| 717 ConTeXt), or tex (for LaTeX). Otherwise, the file is searched for keywords to | |
| 800 | 718 choose context or tex. If no keywords are found, it defaults to plaintex. |
| 719 You can change the default by defining the variable g:tex_flavor to the format | |
| 851 | 720 (not the file type) you use most. Use one of these: > |
| 721 let g:tex_flavor = "plain" | |
| 722 let g:tex_flavor = "context" | |
| 723 let g:tex_flavor = "latex" | |
| 724 Currently no other formats are recognized. | |
| 798 | 725 |
| 726 | |
| 13051 | 727 VIM *ft-vim-plugin* |
| 728 | |
| 729 The Vim filetype plugin defines mappings to move to the start and end of | |
| 730 functions with [[ and ]]. Move around comments with ]" and [". | |
| 731 | |
| 732 The mappings can be disabled with: > | |
| 733 let g:no_vim_maps = 1 | |
| 734 | |
| 735 | |
| 736 ZIMBU *ft-zimbu-plugin* | |
| 737 | |
| 738 The Zimbu filetype plugin defines mappings to move to the start and end of | |
| 739 functions with [[ and ]]. | |
| 740 | |
| 741 The mappings can be disabled with: > | |
| 742 let g:no_zimbu_maps = 1 | |
| 743 < | |
| 744 | |
| 745 | |
| 14421 | 746 vim:tw=78:ts=8:noet:ft=help:norl: |