diff options
author | Bram Moolenaar <Bram@vim.org> | 2018-03-29 18:27:07 +0200 |
---|---|---|
committer | Bram Moolenaar <Bram@vim.org> | 2018-03-29 18:27:07 +0200 |
commit | ab943431d8fcd856008a025b0e5652dd4b8007fc (patch) | |
tree | 105db31f833c8d70ce638bea00e9376258a524b0 /runtime/doc/editing.txt | |
parent | 7b24ce08fe99345cac035215fca29c7e174a6456 (diff) |
Update runtime files
Diffstat (limited to 'runtime/doc/editing.txt')
-rw-r--r-- | runtime/doc/editing.txt | 30 |
1 files changed, 16 insertions, 14 deletions
diff --git a/runtime/doc/editing.txt b/runtime/doc/editing.txt index dc50455312..583d89ccf7 100644 --- a/runtime/doc/editing.txt +++ b/runtime/doc/editing.txt @@ -1,4 +1,4 @@ -*editing.txt* For Vim version 8.0. Last change: 2018 Feb 19 +*editing.txt* For Vim version 8.0. Last change: 2018 Mar 29 VIM REFERENCE MANUAL by Bram Moolenaar @@ -424,6 +424,15 @@ On Unix and a few other systems you can also use backticks for the file name argument, for example: > :next `find . -name ver\\*.c -print` :view `ls -t *.patch \| head -n1` +Vim will run the command in backticks using the 'shell' and use the standard +output as argument for the given Vim command (error messages from the shell +command will be discarded). +To see what shell command Vim is running, set the 'verbose' option to 4. When +the shell command returns a non-zero exit code, an error message will be +displayed and the Vim command will be aborted. To avoid this make the shell +always return zero like so: > + :next `find . -name ver\\*.c -print \|\| true` + The backslashes before the star are required to prevent the shell from expanding "ver*.c" prior to execution of the find program. The backslash before the shell pipe symbol "|" prevents Vim from parsing it as command @@ -650,8 +659,7 @@ list of the current window. There is no check for duplicates, it is possible to add a file to the argument list twice. The currently edited file is not changed. - {not in Vi} {not available when compiled without the - |+listcmds| feature} + {not in Vi} Note: you can also use this method: > :args ## x < This will add the "x" item and sort the new list. @@ -665,8 +673,7 @@ list of the current window. when it's deleted from the argument list. Example: > :argdel *.obj -< {not in Vi} {not available when compiled without the - |+listcmds| feature} +< {not in Vi} :[range]argd[elete] Delete the {range} files from the argument list. Example: > @@ -681,8 +688,7 @@ list of the current window. < Removes all the files from the arglist. When the last number in the range is too high, up to the last argument is deleted. - {not in Vi} {not available when compiled without the - |+listcmds| feature} + {not in Vi} *:argu* *:argument* :[count]argu[ment] [count] [++opt] [+cmd] @@ -691,16 +697,14 @@ list of the current window. when changes have been made and Vim does not want to |abandon| the current buffer. Also see |++opt| and |+cmd|. - {not in Vi} {not available when compiled without the - |+listcmds| feature} + {not in Vi} :[count]argu[ment]! [count] [++opt] [+cmd] Edit file [count] in the argument list, discard any changes to the current buffer. When [count] is omitted the current entry is used. Also see |++opt| and |+cmd|. - {not in Vi} {not available when compiled without the - |+listcmds| feature} + {not in Vi} :[count]n[ext] [++opt] [+cmd] *:n* *:ne* *:next* *E165* *E163* Edit [count] next file. This fails when changes have @@ -823,7 +827,6 @@ fourth file in the argument list. This happens when you do ":e file". LOCAL ARGUMENT LIST {not in Vi} -{not available when compiled without the |+windows| or |+listcmds| features} *:arglocal* :argl[ocal] Make a local copy of the global argument list. @@ -875,8 +878,7 @@ USING THE ARGUMENT LIST autocommand event is disabled by adding it to 'eventignore'. This considerably speeds up editing each file. - {not in Vi} {not available when compiled without the - |+listcmds| feature} + {not in Vi} Also see |:windo|, |:tabdo|, |:bufdo|, |:cdo|, |:ldo|, |:cfdo| and |:lfdo| |