Home/ Questions/Q 8760583
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-13T15:05:00+00:00

After installing vim-ruby-debugger that plugin hijacks several mappings. Like <leader>n , or <leader>t which

  • 0

After installing vim-ruby-debugger that plugin “hijacks” several mappings. Like <leader>n, or <leader>t which I use for respectively NERDTreeToggle and Command-T find.

The culprit is found at the hardcoded mappings in this ruby-debugger.

I’d prefer to have these remapped as <leader>rdX, i.e.: prefixed with *r*uby-*d*ebugger. Obviously, I could simply hack the plugin and change the mappings there. But that seems a bit too hackish (and will probably break on updates).

How can I unmap these mappings, so vim will fallback to my own mappings again? And so that I can remap the commands in my .vimrc (where it should be, IMHO).

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    First, I agree with ZyX’s comments that this is a problem in the plugin that should be fixed. Please ask the plugin author to provide customization.

    There is no easy way to unmap, because Vim does not remember the original mappings when a mapping is overridden. You have to make a note of the original mappings (:map ... when the offending plugin is temporarily disabled, or look in the Vim script for their definitions), then re-execute them after the offending plugin has been loaded (minus any <unique> flags it may have, as these will cause errors on re-execution). This cannot be done in .vimrc, it is sourced first; I would recommend a place like ~/.vim/after/plugin/zzzmappings.vim for this.

    • 0