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

Bug #1859: can't type to filter filenames on Windows 7

Kind bug
Product Command-T
When Created , updated
Status closed
Reporter anonymous
Tags no tags

Description

Hi,

I am using Windows 7, the Cream Vim build without the Cream stuff, linked against Ruby 1.8.7. I also downloaded Ruby 1.8.7 from Ruby Installers, together with the latest devkit.

The extension compiles fine and comes up fine. I can select a file with the arrow keys. But I can't type anything to filter files. When I hit o or i, I get an error saying that I can't make changes because "modifiable" is off.

Any ideas?

Thanks!

Christoph

Comments

  1. Greg Hurrell

    Seems like a mapping issue. Are you using Vim in the terminal (not the GUI) by any chance?

  2. anonymous

    No, it's in the GUI, gvim for Windows. It happens both in the GUI and the terminal.

  3. anonymous

    I just saw that it also happens with LustyExplorer. Same exact problem.

  4. Greg Hurrell

    Unfortunately, not really sure what's going on here. Not something I've seen on the platforms where I'm using Vim and Command-T (Linux and Mac OS X).

  5. anonymous

    I can confirm this bug. I have the same setup with the Cream build of vim (minus the Cream configuration), RubyInstaller 1.8.7, and the devkit. I open the match window and can see everything, but Command-T's remapped keys are not working. The default key mappings are in place, so hitting o and i tried to go into Insert mode, hitting v goes into visual mode, etc...

  6. Greg Hurrell

    Right now I don't really have the time or resources to troubleshoot Windows-specific problems, but I am willing to accept patches from somebody who does have those time and resources.

  7. anonymous

    This is working for me (Christoph) now. As far as I know, the only thing that changed is the Vim version, 7.3 up to patch 289. I also recompiled command-t and made sure it was compiled against 1.8.7 (which I may have done before) and it's working now. I somewhat followed this guide: http://rfbrazier.posterous.com/installing-the-command-t-vim-plugin-on-window but with the newer versions available. I also compiled from cmd.exe and not mingw or anything. Not sure if this is helpful or not, but I am sure happy to have command-t back!

  8. Greg Hurrell

    Glad to hear you got it sorted out.

  9. Greg Hurrell

    Status changed:

    • From: new
    • To: closed
Add a comment

Comments are now closed for this issue.

Menu