Christian Brabandt wrote:
> Bram,
> if in a test we do this:
> call feedkeys('d1', 'x!')
> call feedkeys('2l', 'x')
>
> Vim will stay in the first feedkeys() call and wait for input.
>
> I'd like to have feedkeys() return after CursorHold triggered, but have
> it not finished/aborted the first call, so that in the end this command
> is executed:
> d12l where a cursorhold command triggered after the 1
>
> Does that sound possible or should we not worry about those special case
> (see normal.c:602)
I suppose there are cases where we want for something to happen, be it a
CursorHold event or a timer. And then continue. But that is not
possible with two feedkeys() calls, because after the second you can't
go back to the code where it was waiting for the next character.
I haven't tried this, but could you call feedkeys() in the CursorHold
command? So it feeds the next characters to read? Could try the same
in a timer callback.
--
hundred-and-one symptoms of being an internet addict:
180. You maintain more than six e-mail addresses.
/// 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].
For more options, visit https://groups.google.com/d/optout.
