You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If I input y, vim sits in operator-pending mode indefinitely.
From here I can press i and I'm still in operator-pending mode indefinitely.
I can press w whenever to complete my yank.
However, the yirw key sequence behaves differently. It seems that some sort of timer (perhaps updatetime?) starts after i, and we only get to sneaking if the complete text object is input before the timer expires. Otherwise, we get returned to normal mode.
On my machine, I seem to only have a quarter of a second, which makes actually using leap-spooky rather more difficult that it ought to be, as I have to decide ahead of time the exact "yarw", "diMp", or whatever I'm trying to accomplish, and then input it without pauses.
Is there anything we can do about this, or is it perhaps a fundamental limitation?
Thanks!
The text was updated successfully, but these errors were encountered:
I see, thanks! Yeah -- my timeoutlen is 300 because I want reasonably quick help from which-key if I'm struggling to remember a mapping. But here, I kind of want infinite delay :).
Hi, thanks for the plugin!
First an observation about regular old
yiw
:y
, vim sits in operator-pending mode indefinitely.i
and I'm still in operator-pending mode indefinitely.w
whenever to complete my yank.However, the
yirw
key sequence behaves differently. It seems that some sort of timer (perhapsupdatetime
?) starts afteri
, and we only get to sneaking if the complete text object is input before the timer expires. Otherwise, we get returned to normal mode.On my machine, I seem to only have a quarter of a second, which makes actually using
leap-spooky
rather more difficult that it ought to be, as I have to decide ahead of time the exact "yarw", "diMp", or whatever I'm trying to accomplish, and then input it without pauses.Is there anything we can do about this, or is it perhaps a fundamental limitation?
Thanks!
The text was updated successfully, but these errors were encountered: