bug: Recursion detected due to too fast keyboard repeat_interval

[fnune]

Did you check docs and existing issues?

• I have read all the which-key.nvim docs
• I have updated the plugin to the latest version before submitting this issue
• I have searched the existing issues of which-key.nvim
• I have searched the existing issues of plugins related to this issue

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:

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

• Set your repeat interval to something fast (30ms)
• Go to a large file
• Keep C-d pressed
• Eventually which-key will throw an error

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]

Looks like I could work around this by doing this: #809 (comment)

I would still consider this a bug?

fnune/home.nix@43ededa

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[fnune]

Can still trigger this today as of 68e37e1

[kimifish]

confirm issue, rather annoying..

version     v3.14.1
branch  main 
commit  9b365a6 

Have some j and k mappings,
also have xset r rate 280 40 in .xinitrc

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[fnune]

Not stale