Bram, > Perhaps using :argadd works to create the buffers without actually > opening them or any other side effects. Then later reset the > argument list.
I think it's even trickier than using :argadd. For example... vim --clean :argadd test.txt :e test.txt Notice that you're now editing buffer #2. This breaks the previous patch I submitted to avoid extra empty buffers when loading a session. Also, consider the case where several buffers are open and the user opens a session with :so Session.vim. Then, cycling through the buffers won't work anyway because there will be several buffers open from before the session was loaded. I'm unable to come up with perfect solutions to these issues at this time. However, the patch under discussion here seems obviously correct to me. The test here does a nice job of proving that the fix works, and should pass in all future changes to the session code to fix any of the other issues named here. -- Jason -- -- 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/b2eac877-ed07-48fa-88d6-b300eb58655b%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
