Mercurial > vim

comparison runtime/doc/editing.txt @ 1240:5bed56fce2b5

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
updated for version 7.1
author vimboss
date Sat, 12 May 2007 13:25:01 +0000
parents b7ad1c609161
children 73fe8baea242
comparison
equal deleted inserted replaced
1239:dfc468e0b19d 1240:5bed56fce2b5
1 *editing.txt* For Vim version 7.1b. Last change: 2006 Oct 10 1 *editing.txt* For Vim version 7.1. Last change: 2007 May 11
2 2
3 3
4 VIM REFERENCE MANUAL by Bram Moolenaar 4 VIM REFERENCE MANUAL by Bram Moolenaar
5 5
6 6
747 The wildcards in the argument list are expanded and the file names are sorted. 747 The wildcards in the argument list are expanded and the file names are sorted.
748 Thus you can use the command "vim *.c" to edit all the C files. From within 748 Thus you can use the command "vim *.c" to edit all the C files. From within
749 Vim the command ":n *.c" does the same. 749 Vim the command ":n *.c" does the same.
750 750
751 White space is used to separate file names. Put a backslash before a space or 751 White space is used to separate file names. Put a backslash before a space or
752 Tab to include it in a file name. E.g., to edit the single file "foo bar": > 752 tab to include it in a file name. E.g., to edit the single file "foo bar": >
753 :next foo\ bar 753 :next foo\ bar
754 754
755 On Unix and a few other systems you can also use backticks, for example: > 755 On Unix and a few other systems you can also use backticks, for example: >
756 :next `find . -name \\*.c -print` 756 :next `find . -name \\*.c -print`
757 The backslashes before the star are required to prevent "*.c" to be expanded 757 The backslashes before the star are required to prevent "*.c" to be expanded