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
22
33 ----------------
44 Vimball Archiver
@@ -51,7 +51,7 @@ Copyright: (c) 2004-2015 by Charles E. Campbell *Vimball-copyright*
5151 :RmVimball someplugin
5252< This operation is not at all easy for zips and tarballs, for example.
5353
54- Vimball examines the user's | 'runtimepath' | to determine where to put
54+ Vimball examines the user's 'runtimepath' to determine where to put
5555 the scripts. The first directory mentioned on the runtimepath is
5656 usually used if possible. Use >
5757 :echo &rtp
@@ -66,7 +66,7 @@ MAKING A VIMBALL *:MkVimball*
6666
6767 The range is composed of lines holding paths to files to be included
6868 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: >
7070 plugin/something.vim
7171 doc/something.txt
7272< using >
@@ -77,7 +77,7 @@ MAKING A VIMBALL *:MkVimball*
7777 "filename.vba" file already exists, then MkVimball will issue a
7878 warning and not create the file. Note that these paths are relative
7979 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'
8181 directory that exists as a prefix; don't use absolute paths, unless
8282 the user has specified such a path.
8383
@@ -110,7 +110,7 @@ MAKING DIRECTORIES VIA VIMBALLS *g:vimball_mkdir*
110110
111111CONTROLLING THE VIMBALL EXTRACTION DIRECTORY *g:vimball_home*
112112
113- You may override the use of the | 'runtimepath' | by specifying a
113+ You may override the use of the 'runtimepath' by specifying a
114114 variable, g:vimball_home.
115115
116116 *vimball-extract*
@@ -138,16 +138,16 @@ MANUALLY INVOKING VIMBALL EXTRACTION *:UseVimball*
138138 vimball. One may choose to execute it by hand instead of sourcing
139139 the vimball; one may also choose to specify a path for the
140140 installation, thereby overriding the automatic choice of the first
141- existing directory on the | 'runtimepath' | .
141+ existing directory on the 'runtimepath' .
142142
143143REMOVING A VIMBALL *:RmVimball*
144144
145145 :RmVimball vimballfile [path]
146146
147147 This command removes all files generated by the specified vimball
148148 (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' .
151151 To implement this, a file (.VimballRecord) is made in that directory
152152 containing a record of what files need to be removed for all vimballs
153153 used thus far.
@@ -188,7 +188,7 @@ WINDOWS *vimball-windows*
188188 prepending the current directory to it.
189189 33 : Apr 02, 2011 * Gave priority to *.vmb over *.vba
190190 * Changed silent! to sil! (shorter)
191- * Safed | 'swf' | setting (during vimball extraction,
191+ * Safed 'swf' setting (during vimball extraction,
192192 its now turned off)
193193 32 : May 19, 2010 * (Christian Brabrandt) :so someplugin.vba and
194194 :so someplugin.vba.gz (and the other supported
@@ -247,7 +247,7 @@ WINDOWS *vimball-windows*
247247 14 : May 26, 2006 * bugfixes
248248 13 : May 01, 2006 * exists("&acd") used to determine if the acd
249249 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
251251 11 : Apr 27, 2006 * VimballList would create missing subdirectories that
252252 the vimball specified were needed. Fixed.
253253 10 : Apr 27, 2006 * moved all setting saving/restoration to a pair of
0 commit comments