> The "o" indicates operator-pending. To find out what happens, you could > add an extra ch_log() call in op_pending() to see which of the > conditions is causing this. Because of this the "S" would also appear, > and then the SafeState and SafeStateAgain autocommands won't be > triggered.
Added some logging and bizarrely, op_pending is not being called when I run this test with GVim (at least GVim hangs first). I'm nowhere near close enough to the code to work out what's going on here so hopefully this gives you a clue :) > > Any thoughts on what's going on here? > > Not really. The wait-for-character loop is a bit different, but it > still calls parse_queued_messages(). Adding logging in the VimScript shim for govim, I can see GVim is blocked executing this line: https://github.com/govim/govim/blob/dd90b98557f38dca3785573eab235592b89003c3/plugin/govim.vim#L238 (i.e. a log line added just before appears, a log line after does not) So I don't think this has anything to do with being blocked on receiving/sending messages per se. Thanks -- -- 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/CACoUkn6A%2B2UZO0c550hzHc_qvp742n7iPjCg5eeGAahuryMgDA%40mail.gmail.com.
