I've just realised I wrote CursorMovedI when I meant CursorHoldI. Sorry about that.
> Would it be sufficient to not trigger CursorMovedI when the user pressed > CTRL-X ? What submode would it be in? Or are you saying that this > depends on whether the completion uses a popup menu or not? Yes, I imagine not triggering CursorHoldI when the user presses CTRL-X would suffice. Here's a demonstration of the problem: 1. Start vim with: vim -u NONE --cmd 'set updatetime=1000' --cmd 'set showmode' --cmd 'autocmd CursorHoldI * 1' 2. Type "i" to enter insert mode. 3. Type CTRL-x to enter the insertion completion submode. 4. Expected: vim stays in insertion completion submode. Actual: after 1 second the mode changes back to insert mode. The motivation for fixing this is when the user has a small updatetime of, say, 100ms, they have to be very quick typists to be able to bring up the insert completion popup before the CursorHoldI autocommand boots them out of insertion completion mode. -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
