/
usr
/
share
/
vim
/
vim80
/
doc
/
/usr/share/vim/vim80/doc
mkdir
upload
Name
Size
Mode
Actions
arabic.txt
11936
0644
edit
dl
rm
autocmd.txt
65402
0644
edit
dl
rm
change.txt
74877
0644
edit
dl
rm
channel.txt
30819
0644
edit
dl
rm
cmdline.txt
47283
0644
edit
dl
rm
debug.txt
7182
0644
edit
dl
rm
debugger.txt
5744
0644
edit
dl
rm
develop.txt
22344
0644
edit
dl
rm
diff.txt
16525
0644
edit
dl
rm
digraph.txt
62123
0644
edit
dl
rm
editing.txt
73176
0644
edit
dl
rm
eval.txt
444462
0644
edit
dl
rm
farsi.txt
9703
0644
edit
dl
rm
filetype.txt
26647
0644
edit
dl
rm
fold.txt
23694
0644
edit
dl
rm
ft_ada.txt
18247
0644
edit
dl
rm
ft_rust.txt
9526
0644
edit
dl
rm
ft_sql.txt
30694
0644
edit
dl
rm
gui.txt
45592
0644
edit
dl
rm
gui_w32.txt
18916
0644
edit
dl
rm
gui_x11.txt
29480
0644
edit
dl
rm
hangulin.txt
3291
0644
edit
dl
rm
hebrew.txt
5714
0644
edit
dl
rm
help.txt
8578
0644
edit
dl
rm
helphelp.txt
14338
0644
edit
dl
rm
howto.txt
2911
0644
edit
dl
rm
if_cscop.txt
19361
0644
edit
dl
rm
if_lua.txt
14642
0644
edit
dl
rm
if_mzsch.txt
11823
0644
edit
dl
rm
if_ole.txt
7405
0644
edit
dl
rm
if_perl.txt
11149
0644
edit
dl
rm
if_pyth.txt
37944
0644
edit
dl
rm
if_ruby.txt
8014
0644
edit
dl
rm
if_sniff.txt
266
0644
edit
dl
rm
if_tcl.txt
23026
0644
edit
dl
rm
indent.txt
39427
0644
edit
dl
rm
index.txt
76443
0644
edit
dl
rm
insert.txt
83156
0644
edit
dl
rm
intro.txt
39226
0644
edit
dl
rm
map.txt
64668
0644
edit
dl
rm
mbyte.txt
59306
0644
edit
dl
rm
message.txt
31230
0644
edit
dl
rm
mlang.txt
7850
0644
edit
dl
rm
motion.txt
51602
0644
edit
dl
rm
netbeans.txt
36998
0644
edit
dl
rm
options.txt
389116
0644
edit
dl
rm
os_390.txt
4753
0644
edit
dl
rm
os_amiga.txt
5461
0644
edit
dl
rm
os_beos.txt
10983
0644
edit
dl
rm
os_dos.txt
12021
0644
edit
dl
rm
os_mac.txt
6851
0644
edit
dl
rm
os_mint.txt
1402
0644
edit
dl
rm
os_msdos.txt
518
0644
edit
dl
rm
os_os2.txt
294
0644
edit
dl
rm
os_qnx.txt
4071
0644
edit
dl
rm
os_risc.txt
323
0644
edit
dl
rm
os_unix.txt
2595
0644
edit
dl
rm
os_vms.txt
32100
0644
edit
dl
rm
os_win32.txt
13348
0644
edit
dl
rm
pattern.txt
59321
0644
edit
dl
rm
pi_getscript.txt
21078
0644
edit
dl
rm
pi_gzip.txt
1321
0644
edit
dl
rm
pi_logipat.txt
4186
0644
edit
dl
rm
pi_netrw.txt
175550
0644
edit
dl
rm
pi_paren.txt
2269
0644
edit
dl
rm
pi_spec.txt
4122
0644
edit
dl
rm
pi_tar.txt
6223
0644
edit
dl
rm
pi_vimball.txt
11853
0644
edit
dl
rm
pi_zip.txt
7229
0644
edit
dl
rm
print.txt
31158
0644
edit
dl
rm
quickfix.txt
69021
0644
edit
dl
rm
quickref.txt
71256
0644
edit
dl
rm
quotes.txt
12743
0644
edit
dl
rm
recover.txt
10694
0644
edit
dl
rm
remote.txt
8420
0644
edit
dl
rm
repeat.txt
39573
0644
edit
dl
rm
rileft.txt
4976
0644
edit
dl
rm
russian.txt
3090
0644
edit
dl
rm
scroll.txt
14071
0644
edit
dl
rm
sign.txt
6891
0644
edit
dl
rm
spell.txt
62781
0644
edit
dl
rm
sponsor.txt
7198
0644
edit
dl
rm
starting.txt
73622
0644
edit
dl
rm
syntax.txt
217471
0644
edit
dl
rm
tabpage.txt
16720
0644
edit
dl
rm
tags
328832
0644
edit
dl
rm
tagsrch.txt
36636
0644
edit
dl
rm
term.txt
45416
0644
edit
dl
rm
terminal.txt
33567
0644
edit
dl
rm
tips.txt
20556
0644
edit
dl
rm
todo.txt
296268
0644
edit
dl
rm
uganda.txt
14024
0644
edit
dl
rm
undo.txt
16539
0644
edit
dl
rm
usr_01.txt
7090
0644
edit
dl
rm
usr_02.txt
24339
0644
edit
dl
rm
usr_03.txt
23605
0644
edit
dl
rm
usr_04.txt
19082
0644
edit
dl
rm
usr_05.txt
23824
0644
edit
dl
rm
usr_06.txt
9587
0644
edit
dl
rm
usr_07.txt
15984
0644
edit
dl
rm
usr_08.txt
19374
0644
edit
dl
rm
usr_09.txt
11450
0644
edit
dl
rm
usr_10.txt
29180
0644
edit
dl
rm
usr_11.txt
12611
0644
edit
dl
rm
usr_12.txt
13424
0644
edit
dl
rm
usr_20.txt
13703
0644
edit
dl
rm
usr_21.txt
18373
0644
edit
dl
rm
usr_22.txt
14297
0644
edit
dl
rm
usr_23.txt
12588
0644
edit
dl
rm
usr_24.txt
20869
0644
edit
dl
rm
usr_25.txt
19114
0644
edit
dl
rm
usr_26.txt
8254
0644
edit
dl
rm
usr_27.txt
17723
0644
edit
dl
rm
usr_28.txt
16015
0644
edit
dl
rm
usr_29.txt
20116
0644
edit
dl
rm
usr_30.txt
22656
0644
edit
dl
rm
usr_31.txt
10394
0644
edit
dl
rm
usr_32.txt
5373
0644
edit
dl
rm
usr_40.txt
23184
0644
edit
dl
rm
usr_41.txt
89301
0644
edit
dl
rm
usr_42.txt
13798
0644
edit
dl
rm
usr_43.txt
7404
0644
edit
dl
rm
usr_44.txt
29211
0644
edit
dl
rm
usr_45.txt
17912
0644
edit
dl
rm
usr_90.txt
17661
0644
edit
dl
rm
usr_toc.txt
9218
0644
edit
dl
rm
various.txt
28852
0644
edit
dl
rm
version4.txt
13906
0644
edit
dl
rm
version5.txt
308543
0644
edit
dl
rm
version6.txt
577052
0644
edit
dl
rm
version7.txt
674766
0644
edit
dl
rm
version8.txt
684252
0644
edit
dl
rm
visual.txt
21843
0644
edit
dl
rm
vi_diff.txt
42812
0644
edit
dl
rm
windows.txt
53030
0644
edit
dl
rm
workshop.txt
4631
0644
edit
dl
rm
Edit:
/usr/share/vim/vim80/doc/usr_43.txt
(7404B)
*usr_43.txt* For Vim version 8.0. Last change: 2015 Oct 23 VIM USER MANUAL - by Bram Moolenaar Using filetypes When you are editing a file of a certain type, for example a C program or a shell script, you often use the same option settings and mappings. You quickly get tired of manually setting these each time. This chapter explains how to do it automatically. |43.1| Plugins for a filetype |43.2| Adding a filetype Next chapter: |usr_44.txt| Your own syntax highlighted Previous chapter: |usr_42.txt| Add new menus Table of contents: |usr_toc.txt| ============================================================================== *43.1* Plugins for a filetype *filetype-plugin* How to start using filetype plugins has already been discussed here: |add-filetype-plugin|. But you probably are not satisfied with the default settings, because they have been kept minimal. Suppose that for C files you want to set the 'softtabstop' option to 4 and define a mapping to insert a three-line comment. You do this with only two steps: *your-runtime-dir* 1. Create your own runtime directory. On Unix this usually is "~/.vim". In this directory create the "ftplugin" directory: > mkdir ~/.vim mkdir ~/.vim/ftplugin < When you are not on Unix, check the value of the 'runtimepath' option to see where Vim will look for the "ftplugin" directory: > set runtimepath < You would normally use the first directory name (before the first comma). You might want to prepend a directory name to the 'runtimepath' option in your |vimrc| file if you don't like the default value. 2. Create the file "~/.vim/ftplugin/c.vim", with the contents: > setlocal softtabstop=4 noremap <buffer> <LocalLeader>c o/**************<CR><CR>/<Esc> let b:undo_ftplugin = "setl softtabstop< | unmap <buffer> <LocalLeader>c" Try editing a C file. You should notice that the 'softtabstop' option is set to 4. But when you edit another file it's reset to the default zero. That is because the ":setlocal" command was used. This sets the 'softtabstop' option only locally to the buffer. As soon as you edit another buffer, it will be set to the value set for that buffer. For a new buffer it will get the default value or the value from the last ":set" command. Likewise, the mapping for "\c" will disappear when editing another buffer. The ":map <buffer>" command creates a mapping that is local to the current buffer. This works with any mapping command: ":map!", ":vmap", etc. The |<LocalLeader>| in the mapping is replaced with the value of the "maplocalleader" variable. The line to set b:undo_ftplugin is for when the filetype is set to another value. In that case you will want to undo your preferences. The b:undo_ftplugin variable is executed as a command. Watch out for characters with a special meaning inside a string, such as a backslash. You can find examples for filetype plugins in this directory: > $VIMRUNTIME/ftplugin/ More details about writing a filetype plugin can be found here: |write-plugin|. ============================================================================== *43.2* Adding a filetype If you are using a type of file that is not recognized by Vim, this is how to get it recognized. You need a runtime directory of your own. See |your-runtime-dir| above. Create a file "filetype.vim" which contains an autocommand for your filetype. (Autocommands were explained in section |40.3|.) Example: > augroup filetypedetect au BufNewFile,BufRead *.xyz setf xyz augroup END This will recognize all files that end in ".xyz" as the "xyz" filetype. The ":augroup" commands put this autocommand in the "filetypedetect" group. This allows removing all autocommands for filetype detection when doing ":filetype off". The "setf" command will set the 'filetype' option to its argument, unless it was set already. This will make sure that 'filetype' isn't set twice. You can use many different patterns to match the name of your file. Directory names can also be included. See |autocmd-patterns|. For example, the files under "/usr/share/scripts/" are all "ruby" files, but don't have the expected file name extension. Adding this to the example above: > augroup filetypedetect au BufNewFile,BufRead *.xyz setf xyz au BufNewFile,BufRead /usr/share/scripts/* setf ruby augroup END However, if you now edit a file /usr/share/scripts/README.txt, this is not a ruby file. The danger of a pattern ending in "*" is that it quickly matches too many files. To avoid trouble with this, put the filetype.vim file in another directory, one that is at the end of 'runtimepath'. For Unix for example, you could use "~/.vim/after/filetype.vim". You now put the detection of text files in ~/.vim/filetype.vim: > augroup filetypedetect au BufNewFile,BufRead *.txt setf text augroup END That file is found in 'runtimepath' first. Then use this in ~/.vim/after/filetype.vim, which is found last: > augroup filetypedetect au BufNewFile,BufRead /usr/share/scripts/* setf ruby augroup END What will happen now is that Vim searches for "filetype.vim" files in each directory in 'runtimepath'. First ~/.vim/filetype.vim is found. The autocommand to catch *.txt files is defined there. Then Vim finds the filetype.vim file in $VIMRUNTIME, which is halfway 'runtimepath'. Finally ~/.vim/after/filetype.vim is found and the autocommand for detecting ruby files in /usr/share/scripts is added. When you now edit /usr/share/scripts/README.txt, the autocommands are checked in the order in which they were defined. The *.txt pattern matches, thus "setf text" is executed to set the filetype to "text". The pattern for ruby matches too, and the "setf ruby" is executed. But since 'filetype' was already set to "text", nothing happens here. When you edit the file /usr/share/scripts/foobar the same autocommands are checked. Only the one for ruby matches and "setf ruby" sets 'filetype' to ruby. RECOGNIZING BY CONTENTS If your file cannot be recognized by its file name, you might be able to recognize it by its contents. For example, many script files start with a line like: #!/bin/xyz ~ To recognize this script create a file "scripts.vim" in your runtime directory (same place where filetype.vim goes). It might look like this: > if did_filetype() finish endif if getline(1) =~ '^#!.*[/\\]xyz\>' setf xyz endif The first check with did_filetype() is to avoid that you will check the contents of files for which the filetype was already detected by the file name. That avoids wasting time on checking the file when the "setf" command won't do anything. The scripts.vim file is sourced by an autocommand in the default filetype.vim file. Therefore, the order of checks is: 1. filetype.vim files before $VIMRUNTIME in 'runtimepath' 2. first part of $VIMRUNTIME/filetype.vim 3. all scripts.vim files in 'runtimepath' 4. remainder of $VIMRUNTIME/filetype.vim 5. filetype.vim files after $VIMRUNTIME in 'runtimepath' If this is not sufficient for you, add an autocommand that matches all files and sources a script or executes a function to check the contents of the file. ============================================================================== Next chapter: |usr_44.txt| Your own syntax highlighted Copyright: see |manual-copyright| vim:tw=78:ts=8:ft=help:norl:
Save
cmd:
run