Hi, I can confirm that the below reported problems are resolved by patch 7.4.1123.
Thanks, Yegappan On Sun, Jan 17, 2016 at 10:39 AM, Bram Moolenaar <[email protected]> wrote: > > Yegappan Lakshmanan wrote: > >> After adding files to an empty argument list using the ":argadd" command, >> the second file in the argument list becomes the current argument >> entry instead of the first one. >> >> $ vim -u NONE -N >> :args a b c >> :args >> [a] b c >> :%argdelete >> :argadd a b c >> :args >> a [b] c >> >> As can be seen from the output, file 'b' becomes the current entry >> instead of file 'a'. >> >> Another problem with argadd: >> >> $ vim -u NONE -N >> :argadd a >> :args >> a >> :argadd b c d e >> :args >> a b [c] d e >> >> As can be seen from the output, the file 'c' becomes the current entry. > > I don't think something is specified for the current entry when using > :argadd. In the above situation ":argadd a" should have made the one > argument the current one, right? And the second ":argadd" should not > have changed it. And when the current index is after the added ones, it > should stay on the same file: > > :args a b c > :last > :args > a b [c] > :1argadd x > a x b [c] > -- -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
