diff options
| author | Bram Moolenaar <Bram@vim.org> | 2007-05-05 18:24:42 +0000 |
|---|---|---|
| committer | Bram Moolenaar <Bram@vim.org> | 2007-05-05 18:24:42 +0000 |
| commit | c81e5e79a0f2f5c2ac1896fa51cbe47e2e2a8d97 (patch) | |
| tree | 5211ea86daed8e43c3dd25458e808c3d32100097 /runtime/doc/filetype.txt | |
| parent | 9aae141a6bcfc26bcce352deb8bf34566a3e1be2 (diff) | |
updated for version 7.1a
Diffstat (limited to 'runtime/doc/filetype.txt')
| -rw-r--r-- | runtime/doc/filetype.txt | 26 |
1 files changed, 16 insertions, 10 deletions
diff --git a/runtime/doc/filetype.txt b/runtime/doc/filetype.txt index 58b33b8899..4b8bfafd12 100644 --- a/runtime/doc/filetype.txt +++ b/runtime/doc/filetype.txt @@ -1,4 +1,4 @@ -*filetype.txt* For Vim version 7.0. Last change: 2006 Apr 28 +*filetype.txt* For Vim version 7.1a. Last change: 2007 Mar 24 VIM REFERENCE MANUAL by Bram Moolenaar @@ -43,6 +43,8 @@ Detail: The ":filetype on" command will load one of these files: BufNewFile and BufRead events. If the file type is not found by the name, the file $VIMRUNTIME/scripts.vim is used to detect it from the contents of the file. + When the GUI is running or will start soon, the menu.vim script is + also sourced. See |'go-M'| about avoiding that. To add your own file types, see |new-filetype| below. To search for help on a filetype prepend "ft-" and optionally append "-syntax", "-indent" or @@ -304,24 +306,28 @@ all loaded. For example, if this command: > set runtimepath -produces this output: > +produces this output: - runtimepath=/etc/vim,~/.vim,/usr/local/share/vim/vim60 + runtimepath=/etc/vim,~/.vim,/usr/local/share/vim/vim60 ~ -then Vim will load all plugins in these directories: > +then Vim will load all plugins in these directories and below: - /etc/vim/plugin/ - ~/.vim/plugin/ - /usr/local/share/vim/vim60/plugin/ + /etc/vim/plugin/ ~ + ~/.vim/plugin/ ~ + /usr/local/share/vim/vim60/plugin/ ~ Note that the last one is the value of $VIMRUNTIME which has been expanded. What if it looks like your plugin is not being loaded? You can find out what happens when Vim starts up by using the |-V| argument: > - vim -V1 + + vim -V2 + You will see a lot of messages, in between them is a remark about loading the -plugins. It starts with: > - Searching for "plugin/*.vim" in +plugins. It starts with: + + Searching for "plugin/**/*.vim" in ~ + There you can see where Vim looks for your plugin scripts. ============================================================================== |