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.25k stars 165 forks source link

bug: vim.on_key binded function always receive <80><fd>* characters when which-key setup. #571

Closed gukz closed 2 months ago

gukz commented 8 months ago

Did you check docs and existing issues?

Neovim version (nvim -v)

NVIM v0.10.0-dev-2110+g2fce95ec4

Operating system/version

windows 11

Describe the bug

the which-key add some keys to the vim.on_key binding, I want to avoid this kind of mass.

Steps To Reproduce

write a vim.on_key function, print the key, install which-key.nvim retest the vim.on_key function, will see some <80>* lines, and some input are missing.

Expected Behavior

do not affect the vim.on_key or allow exclude some namespace?

Repro

sorry, I think this issue is very obvious, I can provide some repro script if you need.
github-actions[bot] commented 3 months ago

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.