On Tuesday, 17 May, 2016 at 16:40:19 BST, Bram Moolenaar wrote:
This is not a bug, this has always worked this way.
The idea is that any :next, :last, :first and similar command always
assume you are switching files, thus will give an error if there are
unsaved changes. Even if you end up in the same file.
Perhaps they should not assume this, but rather result in a no-op?
--
--
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.
