Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Open
4 tasks done
fnune opened this issue Oct 1, 2024 · 3 comments
Open
4 tasks done

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

fnune opened this issue Oct 1, 2024 · 3 comments
Labels
bug Something isn't working

Comments

@fnune
Copy link

fnune commented Oct 1, 2024

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:

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

  • 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 fnune added the bug Something isn't working label Oct 1, 2024
fnune added a commit to fnune/home.nix that referenced this issue Oct 14, 2024
@fnune
Copy link
Author

fnune commented Oct 14, 2024

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

I would still consider this a bug?

fnune/home.nix@43ededa

Copy link
Contributor

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.

@github-actions github-actions bot added the stale label Nov 14, 2024
@fnune
Copy link
Author

fnune commented Nov 14, 2024

Can still trigger this today as of 68e37e1

@github-actions github-actions bot removed the stale label Nov 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant