-
Notifications
You must be signed in to change notification settings - Fork 6
/
Copy pathunbundle.txt
76 lines (59 loc) · 3.82 KB
/
unbundle.txt
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
*unbundle.vim* Activates Vim scripts (bundles) from isolated directories.
Author: Suraj N. Kurapati <github.com/sunaku>
License: Same terms as Vim itself (see |license|)
Homepage: https://github.com/sunaku/vim-unbundle
------------------------------------------------------------------------------
INTRODUCTION *unbundle-intro*
------------------------------------------------------------------------------
Unbundle activates your |bundles| and |ftbundles| by adding them to Vim's
'runtimepath' and building missing |:helptags| for documentation therein.
*bundles* are Vim scripts that are stored in isolated `bundle/*/` directories
found in the 'runtimepath'. For example, `~/.vim/bundle/*/` would be your
|bundles| by default in |Unix|. However, you can specify an alternate
location by setting |g:unbundle_bundles_glob|.
*ftbundles* are |filetype|-specific |bundles| that are loaded lazily, only
when they are first used, to shorten Vim's |startup| time. Similar to
|bundles|, they are stored in isolated `ftbundle/{filetype}/*/` directories
found in the 'runtimepath'. For example, `~/.vim/ftbundle/{filetype}/*/`
would be your |ftbundles| for {filetype} by default in |Unix|. However, you
can specify an alternate location by setting |g:unbundle_ftbundles_glob|.
------------------------------------------------------------------------------
CONFIGURATION *unbundle-config*
------------------------------------------------------------------------------
g:unbundle_bundles_glob *g:unbundle_bundles_glob*
Defines a |wildcard| glob pattern to match your |bundles|.
The default value of this configuration parameter is: >
let g:unbundle_bundles_glob = 'bundle/*'
<
g:unbundle_ftbundles_glob *g:unbundle_ftbundles_glob*
Defines a |wildcard| glob pattern to match your |ftbundles|.
Inside this pattern, all `'{filetype}'` substrings are treated
as |wildcards|: they are globally replaced with the |filetype|
of the |ftbundles| that we are currently attempting to load.
The default value of this configuration parameter is: >
let g:unbundle_ftbundles_glob = 'ftbundle/{filetype}/*'
<
------------------------------------------------------------------------------
INVOCATION *unbundle-usage*
------------------------------------------------------------------------------
When it is sourced, |unbundle.vim| activates your |bundles| and also registers
an |autocommand| to activate your |ftbundles| as and when they are necessary.
You can manually re-run some of this logic using these commands and functions:
:Unbundle *:Unbundle*
Activates |bundles| that have not already been activated by
passing |g:unbundle_bundles_glob| to |Unbundle()| function.
Unbundle({glob}) *Unbundle()*
Unbundles directories matched by the given {glob}, unless they
have already been unbundled, and returns them in 'path' form.
Any `*.vim` files that have the same basename as directories
matched by the given {glob} will be |:source|d before their
corresponding directories are unbundled. This allows such
`*.vim` files to configure bundles before they are unbundled.
:Unftbundle {filetype} *:Unftbundle*
Unftbundle({filetype}) *Unftbundle()*
Unbundles directories associated with the given {filetype},
unless they have already been unbundled, and returns them in
'path' form. Multiple |filetype|s can be specified as a glob.
For example, to unbundle your "html", "css", and "javascript"
|ftbundles|, pass `'{html,css,javascript}'` to this function.
vim:tw=78:ts=8:ft=help:norl: