runtime(doc): clarify behaviour or :argadd and :argedit
Commit:
https://github.com/vim/vim/commit/3cb2b3776700988e0c9d4ea37d0b05e371e2bbfd
Author: Christian Brabandt <c...@256bit.org>
Date: Thu Apr 11 21:21:51 2024 +0200
runtime(doc): clarify behaviour or :argadd and :argedit
related: https://github.com/vim/vim/issues/14464
Signed-off-by: Christian Brabandt <c...@256bit.org>
diff --git a/runtime/doc/editing.txt b/runtime/doc/editing.txt
index d0f893856..a5d3c2937 100644
--- a/runtime/doc/editing.txt
+++ b/runtime/doc/editing.txt
@@ -1,4 +1,4 @@
-*editing.txt* For Vim version 9.1. Last change: 2024 Jan 14
+*editing.txt* For Vim version 9.1. Last change: 2024 Apr 11
VIM REFERENCE MANUAL by Bram Moolenaar
@@ -660,7 +660,10 @@ list of the current window.
Add {name}s to the argument list and edit it.
When {name} already exists in the argument list, this
entry is edited.
- This is like using |:argadd| and then |:edit|.
+ This is like using |:argadd| and then |:edit| (with
+ the small exception that |:edit| does not change the
+ argument list, so the argument list pointer isn't
+ changed).
Spaces in filenames have to be escaped with "\".
[count] is used like with |:argadd|.
If the current file cannot be |abandon|ed {name}s will
@@ -679,12 +682,12 @@ list of the current window.
If the argument list is "a b c", and "b" is the
current argument, then these commands result in:
command new argument list ~
- :argadd x a b x c
- :0argadd x x a b c
- :1argadd x a x b c
- :$argadd x a b c x
+ :argadd x a [b] x c
+ :0argadd x x a [b] c
+ :1argadd x a x [b] c
+ :$argadd x a [b] c x
And after the last one:
- :+2argadd y a b c x y
+ :+2argadd y a [b] c x y
There is no check for duplicates, it is possible to
add a file to the argument list twice. You can use
|:argdedupe| to fix it afterwards: >
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/vim_dev/E1rv07Y-004hv3-6C%40256bit.org.
