There is another inconvenient behavior I forgot to mention: c) When there are no valid errors but the output is not empty, make still jumps to the first (non-valid) error (that is, line 1 of quickfix). This is awkward (and affected by issue [1]).
Two remarks: i. this is annoying no matter you want to see the output displayed in the qf window or not, so it's not strictly related to cases 1, 2 and 3 above; ii. make! is no solution, because you may still want to jump to the first valid error when there are valid errors. All in all I feel that quickfix is extremely tailored to cases in which you expect strictly valid error output or nothing at all. For most other cases it's a bit quirky. You can circumvent this writing some vimscript (I've done that indeed), but maybe it would be not that difficult to modify the current behavior a bit in order to acommodate the cases I've described. Nowadays a lot of languages are interpreted and there is no clear boundary between execution, testing, log-debugging and compilation. This dynamic nature of languages also means that errors tend to be in the form of dynamic stack traces, for which context (i.e. non-valid qf entries) is important. Again, I would like to hear your opinions. Cheers -- Carlos [1] https://code.google.com/p/vim/issues/detail?id=378&sort=-id -- -- 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.
