neovim

commit 1685c44dd463217db01643a97163420ed9f5b177
parent d591275db736ddac68c07b49432bc23ad37f2d6a
Author: zeertzjq <zeertzjq@outlook.com>
Date:   Wed, 23 Jul 2025 06:57:37 +0800

Merge pull request #35032 from zeertzjq/vim-61cec2e

vim-patch: doc updates
Diffstat:
M
runtime/doc/usr_02.txt
 | 
2
+-
M
runtime/doc/usr_23.txt
 | 
2
+-
M
runtime/doc/vimeval.txt
 | 
2
+-
M
runtime/doc/vimfn.txt
 | 
2
+-
M
runtime/lua/vim/_meta/vimfn.lua
 | 
2
+-
M
src/nvim/eval.lua
 | 
2
+-

6 files changed, 6 insertions(+), 6 deletions(-)
diff --git a/runtime/doc/usr_02.txt b/runtime/doc/usr_02.txt
@@ -590,7 +590,7 @@ Summary:					*help-summary*  >
 <    for how the '|' is handled in mappings.
 
 15) Command definitions are talked about :h command-topic, so use >
-	:help command-bar
+	:help command-bang
 <    to find out about the '!' argument for custom commands.
 
 16) Window management commands always start with CTRL-W, so you find the
diff --git a/runtime/doc/usr_23.txt b/runtime/doc/usr_23.txt
@@ -116,7 +116,7 @@ Someone sends you an e-mail message, which refers to a file by its URL.  For
 example:
 
 	You can find the information here: ~
-		ftp://ftp.vim.org/pub/vim/README ~
+		https://ftp.nluug.nl/pub/vim/README
 
 You could start a program to download the file, save it on your local disk and
 then start Vim to edit it.
diff --git a/runtime/doc/vimeval.txt b/runtime/doc/vimeval.txt
@@ -2099,7 +2099,7 @@ text...
 				CODE
 <
 								*E121*
-:let {var-name}	..	List the value of variable {var-name}.  Multiple
+:let {var-name}	...	List the value of variable {var-name}.  Multiple
 			variable names may be given.  Special names recognized
 			here:				*E738*
 			  g:	global variables
diff --git a/runtime/doc/vimfn.txt b/runtime/doc/vimfn.txt
@@ -11890,7 +11890,7 @@ wildtrigger()                                                    *wildtrigger()*
 		produce a beep when no matches are found and generally
 		operates more quietly.  This makes it suitable for triggering
 		completion automatically, such as from an |:autocmd|.
-							*cmdline-autocompletion*
+						*cmdline-autocompletion*
 		Example: To make the completion menu pop up automatically as
 		you type on the command line, use: >vim
 			autocmd CmdlineChanged [:/?] call wildtrigger()
diff --git a/runtime/lua/vim/_meta/vimfn.lua b/runtime/lua/vim/_meta/vimfn.lua
@@ -10824,7 +10824,7 @@ function vim.fn.wildmenumode() end
 --- produce a beep when no matches are found and generally
 --- operates more quietly.  This makes it suitable for triggering
 --- completion automatically, such as from an |:autocmd|.
----           *cmdline-autocompletion*
+---         *cmdline-autocompletion*
 --- Example: To make the completion menu pop up automatically as
 --- you type on the command line, use: >vim
 ---   autocmd CmdlineChanged [:/?] call wildtrigger()
diff --git a/src/nvim/eval.lua b/src/nvim/eval.lua
@@ -13082,7 +13082,7 @@ M.funcs = {
       produce a beep when no matches are found and generally
       operates more quietly.  This makes it suitable for triggering
       completion automatically, such as from an |:autocmd|.
-      					*cmdline-autocompletion*
+      				*cmdline-autocompletion*
       Example: To make the completion menu pop up automatically as
       you type on the command line, use: >vim
       	autocmd CmdlineChanged [:/?] call wildtrigger()