On Thu, Nov 2, 2017 at 9:54 AM, Christian Brabandt <[email protected]> wrote: > Okay, could finally reproduce it. This is really a subtle bug popping up. > This happens, because when executing your function, the command will be put > on the commandline, which causes a scroll. Vim then get's into the hit-enter > prompt and expects a character from the user. Now by coincidence the next > character in the typebuf is g which is a character that is accepted by the > hit-enter prompt and thus that character will be consumed and not available > for the normal mode command gv anymore. > > I think using the <silent> flag should work around it, I think. > > Here is a patch, that basically skips putting the character on the > commandline, if they come from a mapping. I think we do not need to put the > characters to be executed on the commandline if they come from a mapping > (which should also save a redraw).
Isn't ":silent" enough? Or maybe a slight increase in 'cmdheight'? I have several mappings which execute short ex-commands, and I _like_ seeing them echoed on the command-line. Best regards, Tony. -- -- 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.
