|
856
|
1 *filetype.txt* For Vim version 7.0g. Last change: 2006 Apr 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 {Vi does not have any of these commands}
|
|
|
16
|
|
|
17 ==============================================================================
|
|
|
18 1. Filetypes *filetypes* *file-types*
|
|
|
19
|
|
|
20 Vim can detect the type of file that is edited. This is done by checking the
|
|
|
21 file name and sometimes by inspecting the contents of the file for specific
|
|
|
22 text.
|
|
|
23
|
|
|
24 *:filetype* *:filet*
|
|
|
25 To enable file type detection, use this command in your vimrc: >
|
|
|
26 :filetype on
|
|
|
27 Each time a new or existing file is edited, Vim will try to recognize the type
|
|
|
28 of the file and set the 'filetype' option. This will trigger the FileType
|
|
|
29 event, which can be used to set the syntax highlighting, set options, etc.
|
|
|
30
|
|
|
31 NOTE: Filetypes and 'compatible' don't work together well, since being Vi
|
|
|
32 compatible means options are global. Resetting 'compatible' is recommended,
|
|
|
33 if you didn't do that already.
|
|
|
34
|
|
|
35 Detail: The ":filetype on" command will load one of these files:
|
|
|
36 Amiga $VIMRUNTIME/filetype.vim
|
|
|
37 Mac $VIMRUNTIME:filetype.vim
|
|
|
38 MS-DOS $VIMRUNTIME\filetype.vim
|
|
|
39 RiscOS Vim:Filetype
|
|
|
40 Unix $VIMRUNTIME/filetype.vim
|
|
|
41 VMS $VIMRUNTIME/filetype.vim
|
|
|
42 This file is a Vim script that defines autocommands for the
|
|
|
43 BufNewFile and BufRead events. If the file type is not found by the
|
|
|
44 name, the file $VIMRUNTIME/scripts.vim is used to detect it from the
|
|
|
45 contents of the file.
|
|
|
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
|
|
|
56 file. Example, for in an IDL file use the command: >
|
|
|
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
|
|
|
123 To disable one of the file types, add a line in the your filetype file, see
|
|
|
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
|
|
|
166 means there can be many files. The advantage is that you can simply drop
|
|
|
167 this 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*
|
|
|
271 On operating systems which support storing a file type with the file, you can
|
|
|
272 specify that an autocommand should only be executed if the file is of a
|
|
|
273 certain type.
|
|
|
274
|
|
|
275 The actual type checking depends on which platform you are running Vim
|
|
|
276 on; see your system's documentation for details.
|
|
|
277
|
|
|
278 To use osfiletype checking in an autocommand you should put a list of types to
|
|
|
279 match in angle brackets in place of a pattern, like this: >
|
|
|
280
|
|
|
281 :au BufRead *.html,<&faf;HTML> runtime! syntax/html.vim
|
|
|
282
|
|
|
283 This will match:
|
|
|
284
|
|
|
285 - Any file whose name ends in `.html'
|
|
|
286 - Any file whose type is `&faf' or 'HTML', where the meaning of these types
|
|
|
287 depends on which version of Vim you are using.
|
|
|
288 Unknown types are considered NOT to match.
|
|
|
289
|
|
|
290 You can also specify a type and a pattern at the same time (in which case they
|
|
|
291 must both match): >
|
|
|
292
|
|
|
293 :au BufRead <&fff>diff*
|
|
|
294
|
|
|
295 This will match files of type `&fff' whose names start with `diff'.
|
|
|
296
|
|
|
297 Note that osfiletype checking is skipped if Vim is compiled without the
|
|
|
298 |+osfiletype| feature.
|
|
|
299
|
|
|
300 *plugin-details*
|
|
|
301 The "plugin" directory can be in any of the directories in the 'runtimepath'
|
|
|
302 option. All of these directories will be searched for plugins and they are
|
|
|
303 all loaded. For example, if this command: >
|
|
|
304
|
|
|
305 set runtimepath
|
|
|
306
|
|
|
307 produces this output: >
|
|
|
308
|
|
|
309 runtimepath=/etc/vim,~/.vim,/usr/local/share/vim/vim60
|
|
|
310
|
|
|
311 then Vim will load all plugins in these directories: >
|
|
|
312
|
|
|
313 /etc/vim/plugin/
|
|
|
314 ~/.vim/plugin/
|
|
|
315 /usr/local/share/vim/vim60/plugin/
|
|
|
316
|
|
|
317 Note that the last one is the value of $VIMRUNTIME which has been expanded.
|
|
|
318
|
|
|
319 What if it looks like your plugin is not being loaded? You can find out what
|
|
|
320 happens when Vim starts up by using the |-V| argument: >
|
|
|
321 vim -V1
|
|
|
322 You will see a lot of messages, in between them is a remark about loading the
|
|
|
323 plugins. It starts with: >
|
|
|
324 Searching for "plugin/*.vim" in
|
|
|
325 There you can see where Vim looks for your plugin scripts.
|
|
|
326
|
|
|
327 ==============================================================================
|
|
|
328 2. Filetype plugin *filetype-plugins*
|
|
|
329
|
|
|
330 When loading filetype plugins has been enabled |:filetype-plugin-on|, options
|
|
|
331 will be set and mappings defined. These are all local to the buffer, they
|
|
|
332 will not be used for other files.
|
|
|
333
|
|
|
334 Defining mappings for a filetype may get in the way of the mappings you
|
|
|
335 define yourself. There are a few ways to avoid this:
|
|
|
336 1. Set the "maplocalleader" variable to the key sequence you want the mappings
|
|
|
337 to start with. Example: >
|
|
|
338 :let maplocalleader = ","
|
|
|
339 < All mappings will then start with a comma instead of the default, which
|
|
|
340 is a backslash. Also see |<LocalLeader>|.
|
|
|
341
|
|
|
342 2. Define your own mapping. Example: >
|
|
|
343 :map ,p <Plug>MailQuote
|
|
|
344 < You need to check the description of the plugin file below for the
|
|
|
345 functionality it offers and the string to map to.
|
|
|
346 You need to define your own mapping before the plugin is loaded (before
|
|
|
347 editing a file of that type). The plugin will then skip installing the
|
|
|
348 default mapping.
|
|
|
349
|
|
|
350 3. Disable defining mappings for a specific filetype by setting a variable,
|
|
|
351 which contains the name of the filetype. For the "mail" filetype this
|
|
|
352 would be: >
|
|
|
353 :let no_mail_maps = 1
|
|
|
354
|
|
|
355 4. Disable defining mappings for all filetypes by setting a variable: >
|
|
|
356 :let no_plugin_maps = 1
|
|
|
357 <
|
|
|
358
|
|
|
359 *ftplugin-overrule*
|
|
|
360 If a global filetype plugin does not do exactly what you want, there are three
|
|
|
361 ways to change this:
|
|
|
362
|
|
|
363 1. Add a few settings.
|
|
|
364 You must create a new filetype plugin in a directory early in
|
|
|
365 'runtimepath'. For Unix, for example you could use this file: >
|
|
|
366 vim ~/.vim/ftplugin/fortran.vim
|
|
|
367 < You can set those settings and mappings that you would like to add. Note
|
|
|
368 that the global plugin will be loaded after this, it may overrule the
|
|
|
369 settings that you do here. If this is the case, you need to use one of the
|
|
|
370 following two methods.
|
|
|
371
|
|
|
372 2. Make a copy of the plugin and change it.
|
|
|
373 You must put the copy in a directory early in 'runtimepath'. For Unix, for
|
|
|
374 example, you could do this: >
|
|
|
375 cp $VIMRUNTIME/ftplugin/fortran.vim ~/.vim/ftplugin/fortran.vim
|
|
|
376 < Then you can edit the copied file to your liking. Since the b:did_ftplugin
|
|
|
377 variable will be set, the global plugin will not be loaded.
|
|
|
378 A disadvantage of this method is that when the distributed plugin gets
|
|
|
379 improved, you will have to copy and modify it again.
|
|
|
380
|
|
|
381 3. Overrule the settings after loading the global plugin.
|
|
|
382 You must create a new filetype plugin in a directory from the end of
|
|
|
383 'runtimepath'. For Unix, for example, you could use this file: >
|
|
|
384 vim ~/.vim/after/ftplugin/fortran.vim
|
|
|
385 < In this file you can change just those settings that you want to change.
|
|
|
386
|
|
|
387 ==============================================================================
|
|
|
388 3. Docs for the default filetype plugins. *ftplugin-docs*
|
|
|
389
|
|
|
390
|
|
501
|
391 CHANGELOG *ft-changelog-plugin*
|
|
7
|
392
|
|
237
|
393 Allows for easy entrance of Changelog entries in Changelog files. There are
|
|
7
|
394 some commands, mappings, and variables worth exploring:
|
|
|
395
|
|
|
396 Options:
|
|
|
397 'comments' is made empty to not mess up formatting.
|
|
|
398 'textwidth' is set to 78, which is standard.
|
|
|
399 'formatoptions' the 't' flag is added to wrap when inserting text.
|
|
|
400
|
|
|
401 Commands:
|
|
|
402 NewChangelogEntry Adds a new Changelog entry in an intelligent fashion
|
|
|
403 (see below).
|
|
|
404
|
|
|
405 Local mappings:
|
|
|
406 <Leader>o Starts a new Changelog entry in an equally intelligent
|
|
|
407 fashion (see below).
|
|
|
408
|
|
|
409 Global mappings:
|
|
|
410 NOTE: The global mappings are accessed by sourcing the
|
|
|
411 ftplugin/changelog.vim file first, e.g. with >
|
|
497
|
412 runtime ftplugin/changelog.vim
|
|
7
|
413 < in your |.vimrc|.
|
|
|
414 <Leader>o Switches to the ChangeLog buffer opened for the
|
|
|
415 current directory, or opens it in a new buffer if it
|
|
|
416 exists in the current directory. Then it does the
|
|
|
417 same as the local <Leader>o described above.
|
|
|
418
|
|
|
419 Variables:
|
|
|
420 g:changelog_timeformat The date (and time) format used in ChangeLog entries.
|
|
|
421 The format accepted is the same as for the
|
|
|
422 |strftime()| function.
|
|
|
423 The default is "%Y-%m-%d" which is the standard format
|
|
|
424 for many ChangeLog layouts.
|
|
|
425 g:changelog_username The name and email address of the user.
|
|
|
426 The default is deduced from environment variables and
|
|
|
427 system files. It searches /etc/passwd for the comment
|
|
|
428 part of the current user, which informally contains
|
|
|
429 the real name of the user up to the first separating
|
|
|
430 comma. then it checks the $NAME environment variable
|
|
|
431 and finally runs `whoami` and `hostname` to build an
|
|
|
432 email address. The final form is >
|
|
|
433 Full Name <user@host>
|
|
|
434 <
|
|
|
435 g:changelog_new_date_format
|
|
|
436 The format to use when creating a new date-entry.
|
|
|
437 The following table describes special tokens in the
|
|
|
438 string:
|
|
|
439 %% insert a single '%' character
|
|
|
440 %d insert the date from above
|
|
|
441 %u insert the user from above
|
|
|
442 %c where to position cursor when done
|
|
|
443 The default is "%d %u\n\n\t* %c\n\n", which produces
|
|
|
444 something like (| is where cursor will be, unless at
|
|
|
445 the start of the line where it denotes the beginning
|
|
|
446 of the line) >
|
|
|
447 |2003-01-14 Full Name <user@host>
|
|
|
448 |
|
|
|
449 | * |
|
|
|
450 <
|
|
|
451 g:changelog_new_entry_format
|
|
|
452 The format used when creating a new entry.
|
|
|
453 The following table describes special tokens in the
|
|
|
454 string:
|
|
|
455 %c where to position cursor when done
|
|
|
456 The default is "\t*%c", which produces something
|
|
|
457 similar to >
|
|
|
458 | * |
|
|
|
459 <
|
|
|
460 g:changelog_date_entry_search
|
|
|
461 The search pattern to use when searching for a
|
|
|
462 date-entry.
|
|
|
463 The same tokens that can be used for
|
|
|
464 g:changelog_new_date_format can be used here as well.
|
|
|
465 The default is '^\s*%d\_s*%u' which finds lines
|
|
|
466 matching the form >
|
|
|
467 |2003-01-14 Full Name <user@host>
|
|
|
468 < and some similar formats.
|
|
|
469
|
|
|
470 The Changelog entries are inserted where they add the least amount of text.
|
|
|
471 After figuring out the current date and user, the file is searched for an
|
|
|
472 entry beginning with the current date and user and if found adds another item
|
|
237
|
473 under it. If not found, a new entry and item is prepended to the beginning of
|
|
7
|
474 the Changelog.
|
|
|
475
|
|
|
476
|
|
501
|
477 FORTRAN *ft-fortran-plugin*
|
|
7
|
478
|
|
|
479 Options:
|
|
|
480 'expandtab' is switched on to avoid tabs as required by the Fortran
|
|
|
481 standards unless the user has set fortran_have_tabs in .vimrc.
|
|
|
482 'textwidth' is set to 72 for fixed source format as required by the
|
|
|
483 Fortran standards and to 80 for free source format.
|
|
|
484 'formatoptions' is set to break code and comment lines and to preserve long
|
|
237
|
485 lines. You can format comments with |gq|.
|
|
7
|
486 For further discussion of fortran_have_tabs and the method used for the
|
|
501
|
487 detection of source format see |ft-fortran-syntax|.
|
|
7
|
488
|
|
|
489
|
|
501
|
490 MAIL *ft-mail-plugin*
|
|
7
|
491
|
|
|
492 Options:
|
|
|
493 'modeline' is switched off to avoid the danger of trojan horses, and to
|
|
|
494 avoid that a Subject line with "Vim:" in it will cause an
|
|
|
495 error message.
|
|
|
496 'textwidth' is set to 72. This is often recommended for e-mail.
|
|
|
497 'formatoptions' is set to break text lines and to repeat the comment leader
|
|
|
498 in new lines, so that a leading ">" for quotes is repeated.
|
|
|
499 You can also format quoted text with |gq|.
|
|
|
500
|
|
|
501 Local mappings:
|
|
|
502 <LocalLeader>q or \\MailQuote
|
|
|
503 Quotes the text selected in Visual mode, or from the cursor position
|
|
|
504 to the end of the file in Normal mode. This means "> " is inserted in
|
|
|
505 each line.
|
|
|
506
|
|
501
|
507 MAN *ft-man-plugin* *:Man*
|
|
7
|
508
|
|
|
509 Displays a manual page in a nice way. Also see the user manual
|
|
|
510 |find-manpage|.
|
|
|
511
|
|
|
512 To start using the ":Man" command before any manual page was loaded, source
|
|
|
513 this script from your startup vimrc file: >
|
|
|
514
|
|
|
515 runtime ftplugin/man.vim
|
|
|
516
|
|
|
517 Options:
|
|
|
518 'iskeyword' the '.' character is added to be able to use CTRL-] on the
|
|
|
519 manual page name.
|
|
|
520
|
|
|
521 Commands:
|
|
|
522 Man {name} Display the manual page for {name} in a window.
|
|
|
523 Man {number} {name}
|
|
|
524 Display the manual page for {name} in a section {number}.
|
|
|
525
|
|
|
526 Global mapping:
|
|
|
527 <Leader>K Displays the manual page for the word under the cursor.
|
|
|
528
|
|
|
529 Local mappings:
|
|
|
530 CTRL-] Jump to the manual page for the word under the cursor.
|
|
|
531 CTRL-T Jump back to the previous manual page.
|
|
|
532
|
|
|
533
|
|
501
|
534 RPM SPEC *ft-spec-plugin*
|
|
7
|
535
|
|
|
536 Since the text for this plugin is rather long it has been put in a separate
|
|
|
537 file: |pi_spec.txt|.
|
|
|
538
|
|
|
539
|
|
720
|
540 SQL *ft-sql*
|
|
|
541
|
|
|
542 Since the text for this plugin is rather long it has been put in a separate
|
|
|
543 file: |sql.txt|.
|
|
|
544
|
|
|
545
|
|
798
|
546 TEX *ft-tex-plugin*
|
|
|
547
|
|
|
548 If the first line of a *.tex file has the form >
|
|
|
549 %&<format>
|
|
|
550 then this determined the file type: plaintex (for plain TeX), context (for
|
|
|
551 ConTeXt), or tex (for LaTeX). Otherwise, the file is searched for keywords to
|
|
800
|
552 choose context or tex. If no keywords are found, it defaults to plaintex.
|
|
|
553 You can change the default by defining the variable g:tex_flavor to the format
|
|
851
|
554 (not the file type) you use most. Use one of these: >
|
|
|
555 let g:tex_flavor = "plain"
|
|
|
556 let g:tex_flavor = "context"
|
|
|
557 let g:tex_flavor = "latex"
|
|
|
558 Currently no other formats are recognized.
|
|
798
|
559
|
|
|
560
|
|
7
|
561 vim:tw=78:ts=8:ft=help:norl:
|
