On Wednesday, April 17, 2019 at 6:36:19 PM UTC+2, Bram Moolenaar wrote: > > On Wednesday, April 17, 2019 at 5:46:35 PM UTC+2, Christian Brabandt wrote: > > > That would be useful information for your initial version ;) > > > > I'm sorry for not mentioning version earlier. About that one line, I did > > > > > > > > Can you show a simple test case? So we can fix it and make sure it > > > doesn't regress anymore? Thanks. > > > > 1) $ vim -p file1 file2 > > > > 2) then in vim type ':f' or just initial bottom status message suffices. > > > > 3) switch to other tab > > > > Actual results: > > Message stays there. > > > > Expected results: > > Clean status line. > > That is not the status line, that is the command line, which is also > used for messages.
I was not sure to call it command line since there was only output message at time which IMO it is a bug. > Not clearing that is intentional. Since you used > ":file" the info is outdated, but it could be the output of any command. It happens for initial message too: 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. -- -- 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.
