comparison runtime/doc/starting.txt @ 9778:4360b2b46125 v7.4.2164

commit https://github.com/vim/vim/commit/66459b7c98c67f8a9d39de8f08e8e8f1fca0e359 Author: Bram Moolenaar <Bram@vim.org> Date: Sat Aug 6 19:01:55 2016 +0200 patch 7.4.2164 Problem: It is not possible to use plugins in an "after" directory to tune the behavior of a package. Solution: First load plugins from non-after directories, then packages and finally plugins in after directories. Reset 'loadplugins' before executing --cmd arguments.
author Christian Brabandt <cb@256bit.org>
date Sat, 06 Aug 2016 19:15:06 +0200
parents 35ce559b8553
children 4da1a3879100
comparison
equal deleted inserted replaced
9777:cbd2d046575d 9778:4360b2b46125
1 *starting.txt* For Vim version 7.4. Last change: 2016 Jul 29 1 *starting.txt* For Vim version 7.4. Last change: 2016 Aug 06
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
856 :runtime! plugin/**/*.vim 856 :runtime! plugin/**/*.vim
857 < The result is that all directories in the 'runtimepath' option will be 857 < The result is that all directories in the 'runtimepath' option will be
858 searched for the "plugin" sub-directory and all files ending in ".vim" 858 searched for the "plugin" sub-directory and all files ending in ".vim"
859 will be sourced (in alphabetical order per directory), also in 859 will be sourced (in alphabetical order per directory), also in
860 subdirectories. 860 subdirectories.
861 However, directories in 'runtimepath' ending in "after" are skipped
862 here and only loaded after packages, see below.
861 Loading plugins won't be done when: 863 Loading plugins won't be done when:
862 - The 'loadplugins' option was reset in a vimrc file. 864 - The 'loadplugins' option was reset in a vimrc file.
863 - The |--noplugin| command line argument is used. 865 - The |--noplugin| command line argument is used.
864 - The "-u NONE" command line argument is used |-u|. 866 - The "-u NONE" command line argument is used |-u|.
865 - When Vim was compiled without the |+eval| feature. 867 - When Vim was compiled without the |+eval| feature.
866 Note that using "-c 'set noloadplugins'" doesn't work, because the 868 Note that using "-c 'set noloadplugins'" doesn't work, because the
867 commands from the command line have not been executed yet. You can 869 commands from the command line have not been executed yet. You can
868 use "--cmd 'set noloadplugins'" |--cmd|. 870 use "--cmd 'set noloadplugins'" or "--cmd 'set loadplugins'" |--cmd|.
869 871
870 Packages are loaded. These are plugins, as above, but found in the 872 Packages are loaded. These are plugins, as above, but found in the
871 "start" directory of each entry in 'packpath'. Every plugin directory 873 "start" directory of each entry in 'packpath'. Every plugin directory
872 found is added in 'runtimepath' and then the plugins are sourced. See 874 found is added in 'runtimepath' and then the plugins are sourced. See
873 |packages|. 875 |packages|.
876
877 The plugins scripts are loaded, as above, but now only the directories
878 ending in "after" are used. Note that 'runtimepath' will have changed
879 if packages have been found, but that should not add a directory
880 ending in "after".
874 881
875 5. Set 'shellpipe' and 'shellredir' 882 5. Set 'shellpipe' and 'shellredir'
876 The 'shellpipe' and 'shellredir' options are set according to the 883 The 'shellpipe' and 'shellredir' options are set according to the
877 value of the 'shell' option, unless they have been set before. 884 value of the 'shell' option, unless they have been set before.
878 This means that Vim will figure out the values of 'shellpipe' and 885 This means that Vim will figure out the values of 'shellpipe' and