Open teocns opened 5 months ago
Lazy's keys
can cause problems (https://github.com/ggandor/leap.nvim/issues/191), and it's unnecessary, Leap lazy-loads itself, so as a very first step, I'd remove that from the config.
Lazy's
keys
can cause problems (#191), and it's unnecessary, Leap lazy-loads itself, so as a very first step, I'd remove that from the config.
Will give a try with event = "VeryLazy"
, though this slightly increases startup time. Keep you posted
Hey @ggandor! Seems that did not change much, the issue persists occasionally and I still could not figure the cause.
One important note: once the issue presents, doesn't matter the direction (bk/fwd), repeating the leap motion in the opposite direction won't work.
Repeating the motion does work; just not in the right direction
For example, I could be leaping forward s{a}{b} <CR> <CR>
and then intend to return at the starting position with <S-CR> <S-CR>
: under the buggy circumstance it will leap forward twice instead. A fresh motion with S{a}{b} <CR>
will begin leaping backwards, but <S-CR>
won't leap forward instead, as you'd expect. The functionality is permanently disrupted and restarting neovim is inevitable at this point.
Pasting here current configuration of what I suspect might be interfering.
Okay, next one: use set_repeat_keys
instead of add_repeat_mappings
(the latter is deprecated, and the former is heavily refactored, doesn't use autocommands at all, so there is some chance it will fix the bug). (Btw add_default_mappings
is also deprecated, but that's irrelevant for now.)
Also, what are your settings for opts.special_keys
?
Seems it started working with the porposed changed, at least for now! I haven't touched opts.special_keys
so it has to be defualt.
Thanks!
Sorry, unfortunately after further usage I've found out that the issue still occurs. What additional info could help you narrow down the scope of the issue?
@ggandor do we have any news on this?
I cannot reproduce, and I have no further idea about what could be the cause. My hunch is that this is not a Leap problem, but Shift-Enter
is somehow not recognized anymore as separate from Enter
. It's simple to confirm this, try another key (like backspace) for a while.
Repeat mappings are bound to
Enter
andShift-Enter
and work as expected, howeverShift-Enter
will stop working (under mysterious circumstances) and behave likeEnter
, the forward movement.It usually occurs after intensive buffer / window / tab switching, and will never regain functionality on any buffer unless restarting vim.
Any ideas what could be causing this? Any debugging logs you recommend
Output of
Redir map <s-enter>
after the functionality broke: