Christian wrote:
> I second this PR, because the default qf filetype makes life nice > statusline plugins unnecessarily harder than it actually should be. So the problem happens when a custom statusline is defined, by a plugin or otherwise. Then the best solution is to have the custom statusline by default, but make it easy to disable it. That would mean checking for a variable to disable the quickfix statusline. -- If cars evolved at the same rate as computers have, they'd cost five euro, run for a year on a couple of liters of petrol, and explode once a day. /// 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]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/201907141357.x6EDvKju031515%40masaka.moolenaar.net. For more options, visit https://groups.google.com/d/optout.
