Skip to content

Commit 718fc1d

Browse files
committed
Update cmdline.{txt,jax}
1 parent c1484f8 commit 718fc1d

File tree

2 files changed

+16
-13
lines changed

2 files changed

+16
-13
lines changed

doc/cmdline.jax

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
*cmdline.txt* For Vim バージョン 9.1. Last change: 2025 Sep 24
1+
*cmdline.txt* For Vim バージョン 9.1. Last change: 2025 Oct 12
22

33

44
VIMリファレンスマニュアル by Bram Moolenaar

en/cmdline.txt

Lines changed: 15 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
*cmdline.txt* For Vim version 9.1. Last change: 2025 Sep 24
1+
*cmdline.txt* For Vim version 9.1. Last change: 2025 Oct 12
22

33

44
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -162,7 +162,8 @@ CTRL-R {register} *c_CTRL-R* *c_<C-R>*
162162
the last delete or yank
163163
'%' the current file name
164164
'#' the alternate file name
165-
'*' the clipboard contents (X11: primary selection)
165+
'*' the clipboard contents (X11: primary
166+
selection)
166167
'+' the clipboard contents
167168
'/' the last search pattern
168169
':' the last command-line
@@ -440,7 +441,8 @@ CTRL-D List names that match the pattern in front of the cursor.
440441
<S-Tab> does not work everywhere.
441442
*c_CTRL-N*
442443
CTRL-N After using 'wildchar' which got multiple matches, go to next
443-
match. Otherwise recall more recent command-line from history.
444+
match. Otherwise recall more recent command-line from
445+
history.
444446
*c_CTRL-P*
445447
CTRL-P After using 'wildchar' which got multiple matches, go to
446448
previous match. Otherwise recall older command-line from
@@ -728,9 +730,9 @@ See also |`=|.
728730

729731
*:_!*
730732
The '!' (bang) character after an Ex command makes the command behave in a
731-
different way. The '!' should be placed immediately after the command, without
732-
any blanks in between. If you insert blanks the '!' will be seen as an
733-
argument for the command, which has a different meaning. For example:
733+
different way. The '!' should be placed immediately after the command,
734+
without any blanks in between. If you insert blanks the '!' will be seen as
735+
an argument for the command, which has a different meaning. For example:
734736
:w! name write the current buffer to file "name", overwriting
735737
any existing file
736738
:w !name send the current buffer as standard input to command
@@ -1105,8 +1107,9 @@ Note: these are typed literally, they are not special keys!
11051107
*filename-modifiers*
11061108
*:_%:* *::8* *::p* *::.* *::~* *::h* *::t* *::r* *::e* *::s* *::gs* *::S*
11071109
*%:8* *%:p* *%:.* *%:~* *%:h* *%:t* *%:r* *%:e* *%:s* *%:gs* *%:S*
1108-
The file name modifiers can be used after "%", "#", "#n", "<cfile>", "<sfile>",
1109-
"<afile>" or "<abuf>". They are also used with the |fnamemodify()| function.
1110+
The file name modifiers can be used after "%", "#", "#n", "<cfile>",
1111+
"<sfile>", "<afile>" or "<abuf>". They are also used with the |fnamemodify()|
1112+
function.
11101113

11111114
These modifiers can be given, in this order:
11121115
:p Make file name a full path. Must be the first modifier. Also
@@ -1159,7 +1162,7 @@ These modifiers can be given, in this order:
11591162
Substitute all occurrences of "pat" with "sub". Otherwise
11601163
this works like ":s".
11611164
:S Escape special characters for use with a shell command (see
1162-
|shellescape()|). Must be the last one. Examples: >
1165+
|shellescape()|). Must be the last one. Examples: >
11631166
:!dir <cfile>:S
11641167
:call system('chmod +w -- ' .. expand('%:S'))
11651168
@@ -1240,9 +1243,9 @@ Therefore "\file\foo" is a valid file name, you don't have to type the
12401243
backslash twice.
12411244

12421245
An exception is the '$' sign. It is a valid character in a file name. But
1243-
to avoid a file name like "$home" to be interpreted as an environment variable,
1244-
it needs to be preceded by a backslash. Therefore you need to use "/\$home"
1245-
for the file "$home" in the root directory. A few examples:
1246+
to avoid a file name like "$home" to be interpreted as an environment
1247+
variable, it needs to be preceded by a backslash. Therefore you need to use
1248+
"/\$home" for the file "$home" in the root directory. A few examples:
12461249

12471250
FILE NAME INTERPRETED AS ~
12481251
$home expanded to value of environment var $home

0 commit comments

Comments
 (0)