1
- *pi_vimball.txt* For Vim version 9.1. Last change: 2016 Apr 11
1
+ *pi_vimball.txt* For Vim version 9.1. Last change: 2025 Aug 06
2
2
3
3
----------------
4
4
Vimball Archiver
@@ -51,7 +51,7 @@ Copyright: (c) 2004-2015 by Charles E. Campbell *Vimball-copyright*
51
51
:RmVimball someplugin
52
52
< This operation is not at all easy for zips and tarballs, for example.
53
53
54
- Vimball examines the user's | 'runtimepath' | to determine where to put
54
+ Vimball examines the user's 'runtimepath' to determine where to put
55
55
the scripts. The first directory mentioned on the runtimepath is
56
56
usually used if possible. Use >
57
57
:echo &rtp
@@ -66,7 +66,7 @@ MAKING A VIMBALL *:MkVimball*
66
66
67
67
The range is composed of lines holding paths to files to be included
68
68
in your new vimball, omitting the portion of the paths that is
69
- normally specified by the runtimepath (| 'rtp' | ). As an example: >
69
+ normally specified by the runtimepath ('rtp' ). As an example: >
70
70
plugin/something.vim
71
71
doc/something.txt
72
72
< using >
@@ -77,7 +77,7 @@ MAKING A VIMBALL *:MkVimball*
77
77
"filename.vba" file already exists, then MkVimball will issue a
78
78
warning and not create the file. Note that these paths are relative
79
79
to your .vim (vimfiles) directory, and the files should be in that
80
- directory. The vimball plugin normally uses the first | 'runtimepath' |
80
+ directory. The vimball plugin normally uses the first 'runtimepath'
81
81
directory that exists as a prefix; don't use absolute paths, unless
82
82
the user has specified such a path.
83
83
@@ -110,7 +110,7 @@ MAKING DIRECTORIES VIA VIMBALLS *g:vimball_mkdir*
110
110
111
111
CONTROLLING THE VIMBALL EXTRACTION DIRECTORY *g:vimball_home*
112
112
113
- You may override the use of the | 'runtimepath' | by specifying a
113
+ You may override the use of the 'runtimepath' by specifying a
114
114
variable, g:vimball_home.
115
115
116
116
*vimball-extract*
@@ -138,16 +138,16 @@ MANUALLY INVOKING VIMBALL EXTRACTION *:UseVimball*
138
138
vimball. One may choose to execute it by hand instead of sourcing
139
139
the vimball; one may also choose to specify a path for the
140
140
installation, thereby overriding the automatic choice of the first
141
- existing directory on the | 'runtimepath' | .
141
+ existing directory on the 'runtimepath' .
142
142
143
143
REMOVING A VIMBALL *:RmVimball*
144
144
145
145
:RmVimball vimballfile [path]
146
146
147
147
This command removes all files generated by the specified vimball
148
148
(but not any directories it may have made). One may choose a path
149
- for de-installation, too (see | 'runtimepath' | ); otherwise, the
150
- default is the first existing directory on the | 'runtimepath' | .
149
+ for de-installation, too (see 'runtimepath' ); otherwise, the default
150
+ is the first existing directory on the 'runtimepath' .
151
151
To implement this, a file (.VimballRecord) is made in that directory
152
152
containing a record of what files need to be removed for all vimballs
153
153
used thus far.
@@ -188,7 +188,7 @@ WINDOWS *vimball-windows*
188
188
prepending the current directory to it.
189
189
33 : Apr 02, 2011 * Gave priority to *.vmb over *.vba
190
190
* Changed silent! to sil! (shorter)
191
- * Safed | 'swf' | setting (during vimball extraction,
191
+ * Safed 'swf' setting (during vimball extraction,
192
192
its now turned off)
193
193
32 : May 19, 2010 * (Christian Brabrandt) :so someplugin.vba and
194
194
:so someplugin.vba.gz (and the other supported
@@ -247,7 +247,7 @@ WINDOWS *vimball-windows*
247
247
14 : May 26, 2006 * bugfixes
248
248
13 : May 01, 2006 * exists("&acd") used to determine if the acd
249
249
option exists
250
- 12 : May 01, 2006 * bugfix - the | 'acd' | option is not always defined
250
+ 12 : May 01, 2006 * bugfix - the 'acd' option is not always defined
251
251
11 : Apr 27, 2006 * VimballList would create missing subdirectories that
252
252
the vimball specified were needed. Fixed.
253
253
10 : Apr 27, 2006 * moved all setting saving/restoration to a pair of
0 commit comments