Paul Jolly wrote:
> > OK, so the feedkeys() causes the safe state to be reset. That is > > correct, since Vim is then busy with processing input, which isn't > > considered safe. > > > > The problem is that with the "xt" argument to feedkeys() the input is > > processed right away, and we don't return to the main loop. I guess > > that we should check for a safe state at the start of feedkeys(), and if > > it's true and the input has been processed, check if it's still safe. > > Honestly, with feedkeys I'm never 100% sure I'm doing the "right" > thing, so please tell me if this is _not_ the right thing to be doing > :) It's better to avoid feedkeys(). ":normal" is a bit better (it saves and restores the typeahead buffer). Please try with patch 8.1.2053. -- Microsoft's definition of a boolean: TRUE, FALSE, MAYBE "Embrace and extend"...? /// 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/201909182005.x8IK5a3C004443%40masaka.moolenaar.net.
