runtime(doc): Fix notation of "Vim script" and "Vim9 script"
closes: #17213 Signed-off-by: Hirohito Higashi <h.east.727@gmail.com> Signed-off-by: Christian Brabandt <cb@256bit.org>
This commit is contained in:
committed by
Christian Brabandt
parent
411ae580a9
commit
fbe4a8f5c0
4
runtime/autoload/dist/vim.vim
vendored
4
runtime/autoload/dist/vim.vim
vendored
@ -1,9 +1,9 @@
|
||||
" Vim runtime support library,
|
||||
" runs the vim9 script version or legacy script version
|
||||
" runs the Vim9 script version or legacy script version
|
||||
" on demand (mostly for Neovim compatability)
|
||||
"
|
||||
" Maintainer: The Vim Project <https://github.com/vim/vim>
|
||||
" Last Change: 2023 Nov 04
|
||||
" Last Change: 2025 Apr 27
|
||||
|
||||
|
||||
" enable the zip and gzip plugin by default, if not set
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
*filetype.txt* For Vim version 9.1. Last change: 2025 Apr 22
|
||||
*filetype.txt* For Vim version 9.1. Last change: 2025 Apr 27
|
||||
|
||||
|
||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||
@ -269,7 +269,7 @@ D. If your filetype can only be detected by inspecting the contents of the
|
||||
item of the 'runtimepath' option. Example for Unix: >
|
||||
:!mkdir ~/.vim
|
||||
<
|
||||
2. Create a vim script file for doing this. Example: >
|
||||
2. Create a Vim script file for doing this. Example: >
|
||||
if did_filetype() " filetype already set..
|
||||
finish " ..don't do these checks
|
||||
endif
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
*if_perl.txt* For Vim version 9.1. Last change: 2023 May 14
|
||||
*if_perl.txt* For Vim version 9.1. Last change: 2025 Apr 27
|
||||
|
||||
|
||||
VIM REFERENCE MANUAL by Sven Verdoolaege
|
||||
@ -74,7 +74,7 @@ The ActiveState one should work, Strawberry Perl is a good alternative.
|
||||
|script-here|.
|
||||
|
||||
|
||||
Example vim script: >
|
||||
Example Vim script: >
|
||||
|
||||
function! WhitePearl()
|
||||
perl << EOF
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
*pi_getscript.txt* For Vim version 9.1. Last change: 2025 Mar 15
|
||||
*pi_getscript.txt* For Vim version 9.1. Last change: 2025 Apr 27
|
||||
>
|
||||
GETSCRIPT REFERENCE MANUAL by Charles E. Campbell
|
||||
<
|
||||
@ -156,7 +156,7 @@ may have. As an example, consider: >
|
||||
|
||||
" GetLatestVimScripts: 884 1 :AutoInstall: AutoAlign.vim
|
||||
|
||||
This comment line tells getscript.vim to check vimscript #884 and that the
|
||||
This comment line tells getscript.vim to check Vim script #884 and that the
|
||||
script is automatically installable. Getscript will also use this line to
|
||||
help build the GetLatestVimScripts.dat file, by including a line such as: >
|
||||
|
||||
|
||||
@ -460,7 +460,7 @@ file using root-relative paths, use the full path:
|
||||
==============================================================================
|
||||
4. Network-Oriented File Transfer *netrw-xfer* {{{1
|
||||
|
||||
Network-oriented file transfer under Vim is implemented by a vim script
|
||||
Network-oriented file transfer under Vim is implemented by a Vim script
|
||||
(<netrw.vim>) using plugin techniques. It currently supports both reading and
|
||||
writing across networks using rcp, scp, ftp or ftp+<.netrc>, scp, fetch,
|
||||
dav/cadaver, rsync, or sftp.
|
||||
|
||||
@ -11383,6 +11383,7 @@ vim-modes-intro intro.txt /*vim-modes-intro*
|
||||
vim-raku ft_raku.txt /*vim-raku*
|
||||
vim-script-intro usr_41.txt /*vim-script-intro*
|
||||
vim-script-library eval.txt /*vim-script-library*
|
||||
vim-script-notation usr_41.txt /*vim-script-notation*
|
||||
vim-security intro.txt /*vim-security*
|
||||
vim-shebang various.txt /*vim-shebang*
|
||||
vim-tutor-create pi_tutor.txt /*vim-tutor-create*
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
*usr_41.txt* For Vim version 9.1. Last change: 2025 Apr 24
|
||||
*usr_41.txt* For Vim version 9.1. Last change: 2025 Apr 27
|
||||
|
||||
VIM USER MANUAL - by Bram Moolenaar
|
||||
|
||||
@ -35,8 +35,10 @@ like for example .vim files or configuration files like .vimrc and .gvimrc.
|
||||
These scripts may define functions, commands and settings that Vim uses to
|
||||
customize and extend its behavior.
|
||||
|
||||
With a slight abuse of nomenclature, we will use "Vim script" to refer to the
|
||||
Vim scripting language throughout this documentation. This shorthand helps to
|
||||
*vim-script-notation*
|
||||
The correct notation is "Vim script" (or "Vim9 script" when refering to the
|
||||
new Vim9 language |Vim9-script|), so we will use "Vim script" to refer to the
|
||||
Vim scripting language throughout this documentation. This shorthand helps to
|
||||
streamline explanations and discussions about scripting with Vim.
|
||||
|
||||
A Vim plugin is a collection of one or more Vim scripts, along with additional
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
*vim9.txt* For Vim version 9.1. Last change: 2025 Apr 18
|
||||
*vim9.txt* For Vim version 9.1. Last change: 2025 Apr 27
|
||||
|
||||
|
||||
VIM REFERENCE MANUAL by Bram Moolenaar
|
||||
@ -2043,7 +2043,7 @@ The script name after `import` can be:
|
||||
|
||||
If the name does not end in ".vim" then the use of "as name" is required.
|
||||
|
||||
Once a vim9 script file has been imported, the result is cached and used the
|
||||
Once a Vim9 script file has been imported, the result is cached and used the
|
||||
next time the same script is imported. It will not be read again.
|
||||
|
||||
It is not allowed to import the same script twice, also when using two
|
||||
@ -2056,7 +2056,7 @@ line, there can be no line break: >
|
||||
echo that
|
||||
.name # Error!
|
||||
< *import-map*
|
||||
When you've imported a function from one script into a vim9 script you can
|
||||
When you've imported a function from one script into a Vim9 script you can
|
||||
refer to the imported function in a mapping by prefixing it with |<SID>|: >
|
||||
noremap <silent> ,a :call <SID>name.Function()<CR>
|
||||
|
||||
|
||||
@ -325,7 +325,7 @@ call s:EditorConfigEnable(1)
|
||||
" UseConfigFiles function for different modes {{{1
|
||||
|
||||
function! s:UseConfigFiles_VimCore(bufnr, target)
|
||||
" Use the vimscript EditorConfig core
|
||||
" Use the Vim script EditorConfig core
|
||||
try
|
||||
let l:config = editorconfig_core#handler#get_configurations(
|
||||
\ { 'target': a:target } )
|
||||
|
||||
@ -2540,7 +2540,7 @@ fun! netrw#NetWrite(...) range
|
||||
endfun
|
||||
|
||||
" ---------------------------------------------------------------------
|
||||
" netrw#NetSource: source a remotely hosted vim script {{{2
|
||||
" netrw#NetSource: source a remotely hosted Vim script {{{2
|
||||
" uses NetRead to get a copy of the file into a temporarily file,
|
||||
" then sources that file,
|
||||
" then removes that file.
|
||||
|
||||
2
runtime/pack/dist/opt/netrw/doc/netrw.txt
vendored
2
runtime/pack/dist/opt/netrw/doc/netrw.txt
vendored
@ -460,7 +460,7 @@ file using root-relative paths, use the full path:
|
||||
==============================================================================
|
||||
4. Network-Oriented File Transfer *netrw-xfer* {{{1
|
||||
|
||||
Network-oriented file transfer under Vim is implemented by a vim script
|
||||
Network-oriented file transfer under Vim is implemented by a Vim script
|
||||
(<netrw.vim>) using plugin techniques. It currently supports both reading and
|
||||
writing across networks using rcp, scp, ftp or ftp+<.netrc>, scp, fetch,
|
||||
dav/cadaver, rsync, or sftp.
|
||||
|
||||
@ -1486,7 +1486,7 @@ syn match vim9SearchDelim '^\s*\zs:[/?]\|[/?]$' contained contains=vimCmdSep
|
||||
syn region vimGlobal matchgroup=Statement start='\<g\%[lobal]!\=/' skip='\\.' end='/' skipwhite nextgroup=vimSubst1
|
||||
syn region vimGlobal matchgroup=Statement start='\<v\%[global]!\=/' skip='\\.' end='/' skipwhite nextgroup=vimSubst1
|
||||
|
||||
" Vim9 Script Regions: {{{2
|
||||
" Vim9 script Regions: {{{2
|
||||
" ==================
|
||||
|
||||
if s:vim9script
|
||||
|
||||
@ -5,10 +5,11 @@
|
||||
" Version: 0.1.18
|
||||
" URL: http://www.vim.org/scripts/script.php?script_id=945
|
||||
" Last Change: 2021 Feb 03
|
||||
" 2025 Apr 27 by Vim Project correct Vim script spelling
|
||||
|
||||
" THE ORIGINAL AUTHOR'S NOTES:
|
||||
"
|
||||
" This is my very first vim script, I hope to have
|
||||
" This is my very first Vim script, I hope to have
|
||||
" done it the right way.
|
||||
"
|
||||
" I must directly or indirectly thank the author of java.vim and ruby.vim:
|
||||
|
||||
@ -149,7 +149,7 @@ def Foo()
|
||||
enddef
|
||||
|
||||
|
||||
# Issue #16227 (Vimscript ternary expression highlighting)
|
||||
# Issue #16227 (Vim script ternary expression highlighting)
|
||||
|
||||
var foo = 'foo' # comment
|
||||
var bar = foo == 'foo' ? 'bar' : 'baz'
|
||||
|
||||
@ -7,7 +7,7 @@ clearmatches()
|
||||
echo "Foo" | clearmatches()
|
||||
|
||||
|
||||
# Issue 16721 (vimscript highlight of builtin function after |)
|
||||
# Issue 16721 (Vim script highlight of builtin function after |)
|
||||
|
||||
&directory = $'{$MYVIMDIR}/.data/swap/'
|
||||
&backupdir = $'{$MYVIMDIR}/.data/backup//'
|
||||
|
||||
@ -99,7 +99,7 @@ def Foo(
|
||||
z: string = "zed")
|
||||
enddef
|
||||
|
||||
" Issue #16243 (vimscript def parameters syntax highlight is wrong)
|
||||
" Issue #16243 (Vim script def parameters syntax highlight is wrong)
|
||||
|
||||
def Test(lines: list<number> = [line('.'), line('.')]): void
|
||||
enddef
|
||||
|
||||
@ -177,7 +177,7 @@ function Foo(...)
|
||||
endfunction
|
||||
|
||||
|
||||
" Issue #16243 (vimscript def parameters syntax highlight is wrong)
|
||||
" Issue #16243 (Vim script def parameters syntax highlight is wrong)
|
||||
|
||||
function Test(lines = [line('.'), line('.')])
|
||||
endfunction
|
||||
|
||||
@ -1546,7 +1546,7 @@ syn match vim9SearchDelim '^\s*\zs:[/?]\|[/?]$' contained contains=vimCmdSep
|
||||
syn region vimGlobal matchgroup=Statement start='\<g\%[lobal]!\=/' skip='\\.' end='/' skipwhite nextgroup=vimSubst1
|
||||
syn region vimGlobal matchgroup=Statement start='\<v\%[global]!\=/' skip='\\.' end='/' skipwhite nextgroup=vimSubst1
|
||||
|
||||
" Vim9 Script Regions: {{{2
|
||||
" Vim9 script Regions: {{{2
|
||||
" ==================
|
||||
|
||||
if s:vim9script
|
||||
|
||||
Reference in New Issue
Block a user