Home/ Questions/Q 4231160
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-21T01:56:22+00:00

I’m trying to use the command-t fuzzy finder plugin for MacVim. I followed the

  • 0

I’m trying to use the command-t fuzzy finder plugin for MacVim.

I followed the directions but my MacVim no longer works; No window shows, but it still looks like it starts up since the app icon is on the dock. If I remove the command-t folder in ~/.vim/ruby, my MacVim works as normal. I’m thinking it’s an incompatibility with Ruby versions? The one MacVim uses versus the RVM one I use to compile command-t. Has anyone else had this problem?

I’m using RVM with ruby 1.9.2, but when I do :Ruby p RUBY_VERSION, it says 1.8.7. When I try compiling MacVim from source with the ruby-interp setting, the end result is the same.

EDIT: I’ve also tried to just use rvm use system before ruby extconf.rb and make of the command-t plugin, which uses ruby version 1.8.7, the same as :ruby p RUBY_VERSION in macvim, but it still does not work. So I really don’t know what the problem is–the versions match. The output of the make is not ideal:
make cc -arch i386 -arch x86_64 -pipe -bundle -undefined dynamic_lookup -o ext.bundle ext.o match.o matcher.o -L. -L/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib -L. -arch i386 -arch x86_64 -lruby -lpthread -ldl ld: warning: in ext.o, file was built for unsupported file format which is not the architecture being linked (i386) ld: warning: in match.o, file was built for unsupported file format which is not the architecture being linked (i386) ld: warning: in matcher.o, file was built for unsupported file format which is not the architecture being linked (i386)

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I started using janus and it solved all of these kinds of issues for me. Plus, it adds all kinds of other cool vim magic. Highly recommended.

    • 0