Problems under MacVim Snapshot 52

I'm using snapshot 52 here so I don't think it's necessarily a problem with that.

You can see which version of Ruby MacVim was linked against by doing:

:ruby p RUBY_VERSION

It should print something like:

"1.8.7"

What do you see when you do:

$ cd ~/.vim/ruby/command-t
$ ruby extconf.rb
$ make

You should see something vaguely like this, and if not, hopefully the output will contain a clue as to why the extension isn't being built or can't be loaded by VIM:

gcc -I. -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0 -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0 -I. -DHAVE_RUBY_H  -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE   -fno-common -arch i386 -arch x86_64 -g -Os -pipe -fno-common -DENABLE_DTRACE  -fno-common  -pipe -fno-common   -std=c99 -Wall -Wextra -Wno-unused-parameter -c ext.c
gcc -I. -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0 -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0 -I. -DHAVE_RUBY_H  -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE   -fno-common -arch i386 -arch x86_64 -g -Os -pipe -fno-common -DENABLE_DTRACE  -fno-common  -pipe -fno-common   -std=c99 -Wall -Wextra -Wno-unused-parameter -c match.c
gcc -I. -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0 -I/System/Library/Frameworks/Ruby.framework/Versions/1.8/usr/lib/ruby/1.8/universal-darwin10.0 -I. -DHAVE_RUBY_H  -D_XOPEN_SOURCE -D_DARWIN_C_SOURCE   -fno-common -arch i386 -arch x86_64 -g -Os -pipe -fno-common -DENABLE_DTRACE  -fno-common  -pipe -fno-common   -std=c99 -Wall -Wextra -Wno-unused-parameter -c matcher.c
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  

Seems that the most likely cause of the crash is the incompatibility between the version of Ruby linked against by VIM and the version used to compile the extension.

I'll bet that if you remove the MacPorts stuff from your PATH temporarily in order to build the extension that it will work.

Not a MacPorts user myself, so not sure how to do that exactly, but basically something like this:

$ echo $PATH
$ OLD_PATH=$PATH
$ export PATH=... # here supply a PATH with all/any "/opt/local" paths removed
$ cd ~/.vim/ruby/command-t
$ ruby extconf.rb
$ make
$ export PATH=$OLD_PATH

If you do it right, you should see /System/Library/Frameworks/Ruby.framework referenced in the build commands, and I expect the plug-in will work fine in VIM.

I think I read that in one of the recent snapshots Björn changed to doing 64-bit builds or something, especially with respect to Snow Leopard or something (can't remember the exact details). It might be worth looking at the snapshot release notes but I have to go away for the weekend so I can't do that right now.

So it might be a 32-bit vs 64-bit thing. What kind of machine you running on? Is it a 64-bit one (eg. recent iMac?) or an older 32-bit one.

Ok, back again.

The three latest release announcements, as far as I can tell:

• 7.3a: http://groups.google.com/group/vim_mac/browse_thread/thread/32ce9ce2e2a2d21b

This build requires an Intel Mac running 10.6 or later. When 7.3 is released I will build another version that runs on earlier versions of OS X and which supports PPC.

• Snapshot 52: http://groups.google.com/group/vim_mac/browse_thread/thread/12f46704b5dfcd53

A warning: it is possible that this release will break Ruby plugins due to a patch to mainline Vim (which changed return types of certain functions from String to Fixnum). For example, the LustyExplorer plugin broke because of this (but has subsequently been patched). At any rate, if you have any problems with Ruby plugins after updating to snapshot 52 you should contact the plugin maintainer.

• Snapshot 51: http://groups.google.com/group/vim_mac/browse_thread/thread/b93c6dd5183bdc5e

(Not really any notes for that snapshot that seem relevant...)

Before you get your hopes up, the comments about changes in the Ruby stuff in 52 aren't an issue for Command-T, as it was fixed way back on 6 March, before Command-T 0.1 had even been released (and the day after the MacVim snapshot release).

So, sadly, the release notes don't really shed any additional light here.

Yeah, sorry I couldn't give you a definitive answer.

I still believe the most likely cause is a mismatch. One last thing you could try is actually building MacVim from source. Might be opening a can of worms, but it would be one way of ensuring that the version of Ruby MacVim links against is the same version that the Command-T extension links against when you compile it.

Made some brief notes on compiling it in "Building MacVim from source".

About the only other thing I can suggest is that perhaps you might find a clue in some of the tickets elsewhere on the site (for example, ticket #1528). Different people on different platforms, and usually the cause is a mismatch which they eventually solve.

But yeah, sticking with the stable release might just be the sanest thing to do.