Christian wrote:
> On Mi, 17 Apr 2019, [email protected] wrote: > > > 1)$ vim -u NONE -U NONE -N -i NONE -p a b > > 2)now you can see ""b" [New File]" in vim command line - but you are > > actually in file "a" (as you can see by :f or in upper tab) > > 3) try to switch to "b" by 'gt' - previous message stays in command line... > > > > IMHO it does not seem like logic behavior - you are in "a" file, but Vim > > reports you 'b [new file]'? Either it should be 'a [New file]' or nothing > > at all, as it was before. And when I switch to other tab, I would expect > > clearing of command line. > > > > If you want more info, please tell me - this change can really confuse > > users. > > That is indeed confusing. However I don't think we should revert to > clear the screen on switching buffers. > > How about the following patch: I don't like this solution, if there is an error then some part of the information has gone missing. A better solution would be to load the buffer in what will be the current tab last. -- Microsoft's definition of a boolean: TRUE, FALSE, MAYBE "Embrace and extend"...? /// Bram Moolenaar -- [email protected] -- 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_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.
