Mercurial > vim
comparison runtime/doc/cmdline.txt @ 6951:b2673982c625
Updated and new runtime files.
author | Bram Moolenaar <bram@vim.org> |
---|---|
date | Tue, 21 Jul 2015 19:19:13 +0200 |
parents | 37c24033b260 |
children | 349e6c01f35d |
comparison
equal
deleted
inserted
replaced
6950:21cbf1529a71 | 6951:b2673982c625 |
---|---|
1 *cmdline.txt* For Vim version 7.4. Last change: 2014 Sep 06 | 1 *cmdline.txt* For Vim version 7.4. Last change: 2015 Jul 21 |
2 | 2 |
3 | 3 |
4 VIM REFERENCE MANUAL by Bram Moolenaar | 4 VIM REFERENCE MANUAL by Bram Moolenaar |
5 | 5 |
6 | 6 |
595 starts editing the three files "foo bar", "goes to" and "school ". | 595 starts editing the three files "foo bar", "goes to" and "school ". |
596 | 596 |
597 When you want to use the special characters '"' or '|' in a command, or want | 597 When you want to use the special characters '"' or '|' in a command, or want |
598 to use '%' or '#' in a file name, precede them with a backslash. The | 598 to use '%' or '#' in a file name, precede them with a backslash. The |
599 backslash is not required in a range and in the ":substitute" command. | 599 backslash is not required in a range and in the ":substitute" command. |
600 See also |`=|. | |
600 | 601 |
601 *:_!* | 602 *:_!* |
602 The '!' (bang) character after an Ex command makes the command behave in a | 603 The '!' (bang) character after an Ex command makes the command behave in a |
603 different way. The '!' should be placed immediately after the command, without | 604 different way. The '!' should be placed immediately after the command, without |
604 any blanks in between. If you insert blanks the '!' will be seen as an | 605 any blanks in between. If you insert blanks the '!' will be seen as an |
748 to insert special things while typing you can use the CTRL-R command. For | 749 to insert special things while typing you can use the CTRL-R command. For |
749 example, "%" stands for the current file name, while CTRL-R % inserts the | 750 example, "%" stands for the current file name, while CTRL-R % inserts the |
750 current file name right away. See |c_CTRL-R|. | 751 current file name right away. See |c_CTRL-R|. |
751 | 752 |
752 Note: If you want to avoid the special characters in a Vim script you may want | 753 Note: If you want to avoid the special characters in a Vim script you may want |
753 to use |fnameescape()|. | 754 to use |fnameescape()|. Also see |`=|. |
754 | 755 |
755 | 756 |
756 In Ex commands, at places where a file name can be used, the following | 757 In Ex commands, at places where a file name can be used, the following |
757 characters have a special meaning. These can also be used in the expression | 758 characters have a special meaning. These can also be used in the expression |
758 function expand() |expand()|. | 759 function expand() |expand()|. |
788 it, no matter how many backslashes. | 789 it, no matter how many backslashes. |
789 you type: result ~ | 790 you type: result ~ |
790 # alternate.file | 791 # alternate.file |
791 \# # | 792 \# # |
792 \\# \# | 793 \\# \# |
793 | 794 Also see |`=|. |
794 *:<cword>* *:<cWORD>* *:<cfile>* *<cfile>* | 795 *:<cword>* *:<cWORD>* *:<cfile>* *<cfile>* |
795 *:<sfile>* *<sfile>* *:<afile>* *<afile>* | 796 *:<sfile>* *<sfile>* *:<afile>* *<afile>* |
796 *:<abuf>* *<abuf>* *:<amatch>* *<amatch>* | 797 *:<abuf>* *<abuf>* *:<amatch>* *<amatch>* |
797 *<slnum>* *E495* *E496* *E497* *E499* *E500* | 798 *<slnum>* *E495* *E496* *E497* *E499* *E500* |
798 Note: these are typed literally, they are not special keys! | 799 Note: these are typed literally, they are not special keys! |
944 :e # :e ?readme? | 945 :e # :e ?readme? |
945 :e `ls #` :e {files matching "?readme?"} | 946 :e `ls #` :e {files matching "?readme?"} |
946 :e #.* :e {files matching "?readme?.*"} | 947 :e #.* :e {files matching "?readme?.*"} |
947 :cd <cfile> :cd {file name under cursor} | 948 :cd <cfile> :cd {file name under cursor} |
948 :cd <cfile>* :cd {file name under cursor plus "*" and then expanded} | 949 :cd <cfile>* :cd {file name under cursor plus "*" and then expanded} |
950 Also see |`=|. | |
949 | 951 |
950 When the expanded argument contains a "!" and it is used for a shell command | 952 When the expanded argument contains a "!" and it is used for a shell command |
951 (":!cmd", ":r !cmd" or ":w !cmd"), the "!" is escaped with a backslash to | 953 (":!cmd", ":r !cmd" or ":w !cmd"), the "!" is escaped with a backslash to |
952 avoid it being expanded into a previously used command. When the 'shell' | 954 avoid it being expanded into a previously used command. When the 'shell' |
953 option contains "sh", this is done twice, to avoid the shell trying to expand | 955 option contains "sh", this is done twice, to avoid the shell trying to expand |
969 FILE NAME INTERPRETED AS ~ | 971 FILE NAME INTERPRETED AS ~ |
970 $home expanded to value of environment var $home | 972 $home expanded to value of environment var $home |
971 \$home file "$home" in current directory | 973 \$home file "$home" in current directory |
972 /\$home file "$home" in root directory | 974 /\$home file "$home" in root directory |
973 \\$home file "\\", followed by expanded $home | 975 \\$home file "\\", followed by expanded $home |
976 Also see |`=|. | |
974 | 977 |
975 ============================================================================== | 978 ============================================================================== |
976 7. Command-line window *cmdline-window* *cmdwin* | 979 7. Command-line window *cmdline-window* *cmdwin* |
977 *command-line-window* | 980 *command-line-window* |
978 In the command-line window the command line can be edited just like editing | 981 In the command-line window the command line can be edited just like editing |