2016-05-04 17:26 GMT+03:00 Paul <[email protected]>: > On Tuesday, 03 May, 2016 at 17:06:45 BST, Ben Fritz wrote: >> >> On Tuesday, May 3, 2016 at 4:27:40 AM UTC-5, Jan wrote: >>> >>> I start vim with "vim file1 file2". :args shows I'm on file1. I change >>> buffer with :bnext. :args shows I'm still on file1. Is there some setting >>> that will update the argument to be on the same buffer that I change to, or >>> is there some reason why that would be a bad idea? >> >> >> Not a setting, a command. >> >> Instead of :bnext, use :next to switch to the next argument in the list. > > > What I mean is if I change to buffer 2 - by any means, including ":buffer > 2", which happens to also be argument 2 (or argument n), I'd like :arglist > to reflect that.
I am wondering what for do you use arglist so you need this? I would not say that arglist is a very useful thing, if :arg* commands were not (nearly?) the only ones accepting multiple arguments I would even say that it is rather useless. > > > -- > -- > You received this message from the "vim_use" 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_use" 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. -- -- You received this message from the "vim_use" 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_use" 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.
