0

I have set , as the leader in vim.
I have a plugin X to move to previous buffer set with key combination ,+h.
There is some plugin Y that has a combination ,+h+some_key.
Now, to actually move to the previous buffer, I have to press ,+h+some_unrelated_key. Basically vim is waiting for input after ,+h to decide if this completes the combination for plugin Y. So if I press some_unrelated_key, it sees there is no such combination and does ,+h for plugin X, followed by whatever some_unrelated_key does.
Question: Is there a way to identify what the plugin Y is?

2
  • Try :verbose map ,h which will show you all normal-mode mappings starting with the ,h prefix and the :verbose part should show you where it's defined. (I'd be happy to turn this into an answer if it does indeed help you fix your problem.) Feel free to edit your question and include relevant output of this command in your specific setup for more suggestions on how to work around or fix the conflict.
    – filbranden
    Jan 28, 2022 at 19:35
  • 1
    @filbranden That worked! Thank you. Please make this an answer. Jan 29, 2022 at 5:03

1 Answer 1

1

You can use the :verbose map ,h command, which will show you all normal-mode mappings starting with the ,h prefix.

The :verbose modifier will have the :map command show you where the specific mappings were originally defined, which might be able to help you trace them back to a specific plug-in.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.