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: <tab> and <c-i> not distinguished #934

Open
4 tasks done
tummetott opened this issue Jan 23, 2025 · 0 comments
Open
4 tasks done

bug: <tab> and <c-i> not distinguished #934

tummetott opened this issue Jan 23, 2025 · 0 comments
Labels
bug Something isn't working

Comments

@tummetott
Copy link

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.3 Build type: Release LuaJIT 2.1.1736781742

Operating system/version

macOS 15.1

Describe the bug

Newer versions of neovim can distinguish <tab> and <c-i>. However, which-key can not.

Steps To Reproduce

spec = {
    { "<TAB>", desc = "Tab" },
    { "<C-i>", desc = "<C-i>" },
}

creates the following keymap description:

Image

When the order is changed, this keymap description is created:

spec = {
    { "<C-i>", desc = "<C-i>" },
    { "<TAB>", desc = "Tab" },
}
Image

I can use two different mappings for both keys, and Neovim correctly recognizes and distinguishes between the keystrokes, Which-Key treats them as identical.

Expected Behavior

which-key creates two different mappings for <tab> and <C-i>

Health


Log


Repro

@tummetott tummetott added the bug Something isn't working label Jan 23, 2025
@tummetott tummetott changed the title bug: bug: <tab> and <c-i> not distinguished Jan 23, 2025
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