You are viewing an historical archive of past issues. Please report new issues to the appropriate project issue tracker on GitHub.

Bug #1762: Mapping :CommandTFlush breaks existing :CommandT mapping

Kind bug
Product Command-T
When
Status closed
Reporter Greg Hurrell
Tags no tags

Description

Pasted from GitHub message:

Hello, I wanted to point out a small problem I was having with your awesome plugin.

Whenever I tried to map a shortcut to :CommandTFlush the commandT plugin would stop working.

To fix this I had to map :CommandTFlush AND the :CommandT commands in my .vimrc file. You can see the details here http://stackoverflow.com/questions/4523710/problem-remapping-a-key-while-using-vims-commandt-plugin

I'm not sure why it works but just incase others have this same problem this is the solution.

-Daniel

Comments

  1. Greg Hurrell

    Here's what I replied:

    Thanks for the message. I hadn't heard about this one before.

    My guess is that commit 70a8f9c9 is responsible. Specifically the "hasmapto()" function, which the Vim help describes as: 

    The result is a Number, which is 1 if there is a mapping that
contains {what} in somewhere in the rhs (what it is mapped to)
and this mapping exists in one of the modes indicated by
{mode}.

    So it sees a mapping for CommandTFlush, and so hasmapto() returns 1 and CommandT doesn't get its mapping any more. Will see if I can find a fix.

  2. Greg Hurrell

    Fixed in commit dfc4e191604. Will mark this one as closed.

  3. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu