Hirohito Higashi wrote: > Hi Jan, > > 2016-5-17(Tue) 21:49:39 UTC+9 Jan: > > 1. Edit two new files: "vim -u NONE 1 2" > > 2. ":set hidden" > > 3. ":next" to file 2 > > 4. Modify file (but don't save) > > 5. ":last" > > > > Why does it complain with "E37: No write since last change (add ! to > > override)"? I'm not actually changing away from the buffer, and even if I > > were, "hidden" is set. > > Yeah, This is obviously a bug. > I'll begin an investigation to correct from now.
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. -- DENNIS: Oh, very nice. King, eh! I expect you've got a palace and fine clothes and courtiers and plenty of food. And how d'you get that? By exploiting the workers! By hanging on to outdated imperialist dogma which perpetuates the social and economic differences in our society! "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD /// Bram Moolenaar -- b...@moolenaar.net -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ an exciting new programming language -- http://www.Zimbu.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org /// -- -- 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 vim_use+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.