folke / which-key.nvim

💥 Create key bindings that stick. WhichKey helps you remember your Neovim keymaps, by showing available keybindings in a popup as you type.
Apache License 2.0
5.31k stars 170 forks source link

bug: Recursion detected due to too fast keyboard repeat_interval #859

Open fnune opened 2 weeks ago

fnune commented 2 weeks ago

Did you check docs and existing issues?

Neovim version (nvim -v)

NVIM v0.10.1 Build type: Release LuaJIT 2.1.1713773202 Run "nvim -V1 -v" for more info

Operating system/version

Linux feanor 6.6.52 #1-NixOS SMP PREEMPT_DYNAMIC Wed Sep 18 17:24:10 UTC 2024 x86_64 GNU/Linux

Describe the bug

If I'm scrolling down or up by keeping C-u or C-d pressed, or just j or k, which-key shows this:

image

This is only happening (I think) because of my quick repeat settings (200ms delay, 30ms repeat interval).

Now, I could get good at vim and use motions more often, but sometimes I just want to scroll down while I'm looking at the file. which-key is wrongly detecting recursion here.

Steps To Reproduce

Expected Behavior

Recursion detection behavior does not mistakenly label continuous key-presses with recursion. No error is shown.

Health

No response

Log

No response

Repro

No response

fnune commented 4 days ago

Looks like I could work around this by doing this: https://github.com/folke/which-key.nvim/issues/809#issuecomment-2380620036

I would still consider this a bug?

https://github.com/fnune/home.nix/commit/43ededa0773a3c72a2cf5eff3abbbab24d2955e0