Hi Bram, > Thanks for checking. I'll write tests for state() and the autocommand > events.
The only issue we're seeing is that things "lock up" with GVim. Taking a simple example test, and running the same govim test in Vim and then GVim: * Vim reports that the state is 'c' * GVim reports that the state is 'oSc' Whether this is significant or not I'm not sure. But on the basis of the above state we immediately schedule work. In Vim everything proceeds just fine, but in GVim things lockup. The log file sequences are here: https://gist.github.com/myitcv/05c226d2388a9877317082398f1d9904 Any thoughts on what's going on here? Thanks, Paul -- -- 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/CACoUkn6xpRFy%3Dy18HHsvsYkG4aaifhXEMeGShH_W2%3DvSB5WQnQ%40mail.gmail.com.
