summaryrefslogtreecommitdiff
path: root/runtime/doc/repeat.txt
diff options
context:
space:
mode:
authorBram Moolenaar <Bram@vim.org>2016-03-09 22:19:26 +0100
committerBram Moolenaar <Bram@vim.org>2016-03-09 22:19:26 +0100
commitaf1a0e371e739f8dff337fd31da0ff8ffb347b43 (patch)
tree5b57acb24b0604b274725ebfe14aa24b0cbad7bc /runtime/doc/repeat.txt
parent562ca7142845273bca656aa5aeeda90f001062e0 (diff)
downloadvim-af1a0e371e739f8dff337fd31da0ff8ffb347b43.zip
patch 7.4.1528
Problem: Using "ever" for packages is confusing. Solution: Use "start", as it's related to startup.
Diffstat (limited to 'runtime/doc/repeat.txt')
-rw-r--r--runtime/doc/repeat.txt22
1 files changed, 11 insertions, 11 deletions
diff --git a/runtime/doc/repeat.txt b/runtime/doc/repeat.txt
index 30be59cf4..28a17ae11 100644
--- a/runtime/doc/repeat.txt
+++ b/runtime/doc/repeat.txt
@@ -1,4 +1,4 @@
-*repeat.txt* For Vim version 7.4. Last change: 2016 Mar 07
+*repeat.txt* For Vim version 7.4. Last change: 2016 Mar 09
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -441,16 +441,16 @@ The directory name "foo" is arbitrary, you can pick anything you like.
You would now have these files under ~/.vim:
pack/foo/README.txt
- pack/foo/ever/foobar/plugin/foo.vim
- pack/foo/ever/foobar/syntax/some.vim
+ pack/foo/start/foobar/plugin/foo.vim
+ pack/foo/start/foobar/syntax/some.vim
pack/foo/opt/foodebug/plugin/debugger.vim
When Vim starts up, after processing your .vimrc, it scans all directories in
-'packpath' for plugins under the "pack/*/ever" directory and loads them. The
+'packpath' for plugins under the "pack/*/start" directory and loads them. The
directory is added to 'runtimepath'.
-In the example Vim will find "pack/foo/ever/foobar/plugin/foo.vim" and adds
-"~/.vim/pack/foo/ever/foobar" to 'runtimepath'.
+In the example Vim will find "pack/foo/start/foobar/plugin/foo.vim" and adds
+"~/.vim/pack/foo/start/foobar" to 'runtimepath'.
If the "foobar" plugin kicks in and sets the 'filetype' to "some", Vim will
find the syntax/some.vim file, because its directory is in 'runtimepath'.
@@ -458,7 +458,7 @@ find the syntax/some.vim file, because its directory is in 'runtimepath'.
Vim will also load ftdetect files, if there are any.
Note that the files under "pack/foo/opt" or not loaded automatically, only the
-ones under "pack/foo/ever". See |pack-add| below for how the "opt" directory
+ones under "pack/foo/start". See |pack-add| below for how the "opt" directory
is used.
Loading packages will not happen if loading plugins is disabled, see
@@ -469,13 +469,13 @@ Using a single plugin and loading it automatically ~
If you don't have a package but a single plugin, you need to create the extra
directory level:
- % mkdir -p ~/.vim/pack/foo/ever/foobar
- % cd ~/.vim/pack/foo/ever/foobar
+ % mkdir -p ~/.vim/pack/foo/start/foobar
+ % cd ~/.vim/pack/foo/start/foobar
% unzip /tmp/someplugin.zip
You would now have these files:
- pack/foo/ever/foobar/plugin/foo.vim
- pack/foo/ever/foobar/syntax/some.vim
+ pack/foo/start/foobar/plugin/foo.vim
+ pack/foo/start/foobar/syntax/some.vim
From here it works like above.