diff options
Diffstat (limited to 'runtime/doc/usr_41.txt')
| -rw-r--r-- | runtime/doc/usr_41.txt | 16 |
1 files changed, 8 insertions, 8 deletions
diff --git a/runtime/doc/usr_41.txt b/runtime/doc/usr_41.txt index 90b4ba7a9d..705702c083 100644 --- a/runtime/doc/usr_41.txt +++ b/runtime/doc/usr_41.txt @@ -2051,8 +2051,8 @@ Example: > Write this single-line file as "ftdetect/foofoo.vim" in the first directory that appears in 'runtimepath'. For Unix that would be -"~/.vim/ftdetect/foofoo.vim". The convention is to use the name of the -filetype for the script name. +"~/.config/nvim/ftdetect/foofoo.vim". The convention is to use the name of +the filetype for the script name. You can make more complicated checks if you like, for example to inspect the contents of the file to recognize the language. Also see |new-filetype|. @@ -2122,8 +2122,8 @@ you can write the different setting in a script: > Now write this in the "after" directory, so that it gets sourced after the distributed "vim.vim" ftplugin |after-directory|. For Unix this would be -"~/.vim/after/ftplugin/vim.vim". Note that the default plugin will have set -"b:did_ftplugin", but it is ignored here. +"~/.config/nvim/after/ftplugin/vim.vim". Note that the default plugin will +have set "b:did_ftplugin", but it is ignored here. OPTIONS @@ -2289,8 +2289,8 @@ a user to overrule or add to the default file. The default files start with: > :let current_compiler = "mine" When you write a compiler file and put it in your personal runtime directory -(e.g., ~/.vim/compiler for Unix), you set the "current_compiler" variable to -make the default file skip the settings. +(e.g., ~/.config/nvim/compiler for Unix), you set the "current_compiler" +variable to make the default file skip the settings. *:CompilerSet* The second mechanism is to use ":set" for ":compiler!" and ":setlocal" for ":compiler". Vim defines the ":CompilerSet" user command for this. However, @@ -2310,7 +2310,7 @@ runtime directory, use the mechanism mentioned above. When When you write a compiler plugin to overrule settings from a default plugin, don't check "current_compiler". This plugin is supposed to be loaded last, thus it should be in a directory at the end of 'runtimepath'. For Unix -that could be ~/.vim/after/compiler. +that could be ~/.config/nvim/after/compiler. ============================================================================== *41.14* Writing a plugin that loads quickly *write-plugin-quickload* @@ -2428,7 +2428,7 @@ want to use subdirectories. Example: > For Unix the library script used for this could be: - ~/.vim/autoload/netlib/ftp.vim + ~/.config/nvim/autoload/netlib/ftp.vim Where the function is defined like this: > |