Paul Jolly wrote:

> > 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 "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.

> The log file sequences are here:
> 
> https://gist.github.com/myitcv/05c226d2388a9877317082398f1d9904
> 
> 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().

-- 
   LAUNCELOT leaps into SHOT with a mighty cry and runs the GUARD through and
   hacks him to the floor.  Blood.  Swashbuckling music (perhaps).
   LAUNCELOT races through into the castle screaming.
SECOND SENTRY: Hey!
                 "Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD

 /// 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/201909242042.x8OKg7cu015140%40masaka.moolenaar.net.

Raspunde prin e-mail lui