comparison runtime/doc/repeat.txt @ 8475:aec051e61547 v7.4.1528

commit https://github.com/vim/vim/commit/af1a0e371e739f8dff337fd31da0ff8ffb347b43 Author: Bram Moolenaar <Bram@vim.org> Date: Wed Mar 9 22:19:26 2016 +0100 patch 7.4.1528 Problem: Using "ever" for packages is confusing. Solution: Use "start", as it's related to startup.
author Christian Brabandt <cb@256bit.org>
date Wed, 09 Mar 2016 22:30:07 +0100
parents 4c6ad81d41fe
children 981cc3bef9f3
comparison
equal deleted inserted replaced
8474:d69a804ff41a 8475:aec051e61547
1 *repeat.txt* For Vim version 7.4. Last change: 2016 Mar 07 1 *repeat.txt* For Vim version 7.4. Last change: 2016 Mar 09
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
439 439
440 The directory name "foo" is arbitrary, you can pick anything you like. 440 The directory name "foo" is arbitrary, you can pick anything you like.
441 441
442 You would now have these files under ~/.vim: 442 You would now have these files under ~/.vim:
443 pack/foo/README.txt 443 pack/foo/README.txt
444 pack/foo/ever/foobar/plugin/foo.vim 444 pack/foo/start/foobar/plugin/foo.vim
445 pack/foo/ever/foobar/syntax/some.vim 445 pack/foo/start/foobar/syntax/some.vim
446 pack/foo/opt/foodebug/plugin/debugger.vim 446 pack/foo/opt/foodebug/plugin/debugger.vim
447 447
448 When Vim starts up, after processing your .vimrc, it scans all directories in 448 When Vim starts up, after processing your .vimrc, it scans all directories in
449 'packpath' for plugins under the "pack/*/ever" directory and loads them. The 449 'packpath' for plugins under the "pack/*/start" directory and loads them. The
450 directory is added to 'runtimepath'. 450 directory is added to 'runtimepath'.
451 451
452 In the example Vim will find "pack/foo/ever/foobar/plugin/foo.vim" and adds 452 In the example Vim will find "pack/foo/start/foobar/plugin/foo.vim" and adds
453 "~/.vim/pack/foo/ever/foobar" to 'runtimepath'. 453 "~/.vim/pack/foo/start/foobar" to 'runtimepath'.
454 454
455 If the "foobar" plugin kicks in and sets the 'filetype' to "some", Vim will 455 If the "foobar" plugin kicks in and sets the 'filetype' to "some", Vim will
456 find the syntax/some.vim file, because its directory is in 'runtimepath'. 456 find the syntax/some.vim file, because its directory is in 'runtimepath'.
457 457
458 Vim will also load ftdetect files, if there are any. 458 Vim will also load ftdetect files, if there are any.
459 459
460 Note that the files under "pack/foo/opt" or not loaded automatically, only the 460 Note that the files under "pack/foo/opt" or not loaded automatically, only the
461 ones under "pack/foo/ever". See |pack-add| below for how the "opt" directory 461 ones under "pack/foo/start". See |pack-add| below for how the "opt" directory
462 is used. 462 is used.
463 463
464 Loading packages will not happen if loading plugins is disabled, see 464 Loading packages will not happen if loading plugins is disabled, see
465 |load-plugins|. 465 |load-plugins|.
466 466
467 467
468 Using a single plugin and loading it automatically ~ 468 Using a single plugin and loading it automatically ~
469 469
470 If you don't have a package but a single plugin, you need to create the extra 470 If you don't have a package but a single plugin, you need to create the extra
471 directory level: 471 directory level:
472 % mkdir -p ~/.vim/pack/foo/ever/foobar 472 % mkdir -p ~/.vim/pack/foo/start/foobar
473 % cd ~/.vim/pack/foo/ever/foobar 473 % cd ~/.vim/pack/foo/start/foobar
474 % unzip /tmp/someplugin.zip 474 % unzip /tmp/someplugin.zip
475 475
476 You would now have these files: 476 You would now have these files:
477 pack/foo/ever/foobar/plugin/foo.vim 477 pack/foo/start/foobar/plugin/foo.vim
478 pack/foo/ever/foobar/syntax/some.vim 478 pack/foo/start/foobar/syntax/some.vim
479 479
480 From here it works like above. 480 From here it works like above.
481 481
482 482
483 Optional plugins ~ 483 Optional plugins ~