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] Keymap keep existing even after removing plugin #13

Closed
Peeeaje opened this issue Dec 19, 2024 · 2 comments
Closed

[BUG] Keymap keep existing even after removing plugin #13

Peeeaje opened this issue Dec 19, 2024 · 2 comments

Comments

@Peeeaje
Copy link

Peeeaje commented Dec 19, 2024

Describe the bug
Even after removing elin plugin, set keymaps by enabling elin_enable_default_key_mappings continues to exist...

To Reproduce

  1. use neovim and lazy.nvim
  2. install elin with enabling elin_enable_default_key_mappings
  3. remove the plugin
  4. see keymaps by :map

Expected behavior
keymap removed when disabled or deleted

Environemnt (please complete the following information):

  • Editor: Neovim
  • Editor version: 0.10.2
  • Babashka version: 1.12.195

Additional context
I often use neovim plugin rather vim plugin so such keymap remaining can be normal or maybe your expected behavior. If so please close this. :)
Also I have not fully investigated the situation so it might not be reproduced by above, if so I will find minimum config/steps to reproduce. Thank you.

@liquidz
Copy link
Owner

liquidz commented Dec 19, 2024

@Peeeaje
The keymap will not be registered unless the plugin remains in neovim's runtimepath.
So I suspect lazy.nvim is caching something.

Please try checking the current runtimepath with :set rtp.
If there is anything related to elin left, could you clear the cache on the lazy.nvim side.

cf. folke/lazy.nvim#29

@liquidz
Copy link
Owner

liquidz commented Dec 29, 2024

Feel free to reopen if you have any other problems :)

@liquidz liquidz closed this as completed Dec 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants