runtime(doc): Use correct option-name tags

closes: #17857

Signed-off-by: Hirohito Higashi <h.east.727@gmail.com>
Signed-off-by: Christian Brabandt <cb@256bit.org>
This commit is contained in:
Hirohito Higashi
2025-08-06 12:44:36 +02:00
committed by Christian Brabandt
parent 02bbc8a706
commit 85cd509885
41 changed files with 251 additions and 254 deletions

View File

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