Carlos Pita wrote: > The fact that the hit enter prompt is shown twice sometimes after > :make when an error is found by quickfix was asked a number of times > in the user list and in stackoverflow, but AFAIK it was just > workarounded by making make silent or cmdheight larger. Now I've found > a specific situation when the problem seem to be clearly reproducible: > when the cursor was already on the line containing the first qf valid > error immediately before running the make command (that is, the curaor > was already on the line where make will automatically jump). In this > case the qf error message is echoed as usual, except that the editor > hasn't been redrawn yet and the hit enter prompt is presented again.
What happens here is that when you jump to a quickfix entry it normally echoes the error. Errors are often long and cause the hit-enter prompt. As a compromise the error is shortened when the cursor moves. When you jump to an error in the same line, then the full error is echoed, so that you can read it. I don't think there is a better compromise. -- I wish there was a knob on the TV to turn up the intelligence. There's a knob called "brightness", but it doesn't seem to work. /// 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.
