-
|
Please pardon my shorthand, remoteActionFn is not the actual function name, that fn is unnamed. I'm curious if anyone understand why that's wrapped in a vim.schedule. For me the effect is that i have to wait before entering in my 2 leap characters, otherwise nvim just acts as if I'm inputting normal mode keys. I manually removed the vim.schedule and it works the way I'd expect, e.g. i type in 'gsaa' in quick succession and labels pop up wherever 'aa' exists -- just wondering if there's something I'm missing. I have a history of jumping the gun on bug reports so I want to make sure first. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Visual and O-p mode (and thus remote text objects) won't work without scheduling, only Normal mode (try |
Beta Was this translation helpful? Give feedback.
Visual and O-p mode (and thus remote text objects) won't work without scheduling, only Normal mode (try
vgs-vitself will be fed as input for leap). TBH, it was kind of a trial-and-error move, if anyone understands it in depth, enlightening me would be much appreciated.