vim +ruby problem

[Ryan Schmidt]

On Feb 20, 2012, at 23:48, S.M. Protsman wrote:

> 
> On Feb 20, 2012, at 9:41 PM, Ryan Schmidt wrote:
> 
>> 
>> On Feb 20, 2012, at 23:21, S.M. Protsman wrote:
>> 
>>> The 'provides' option shows that it comes from ruby19. Any idea why this isn't libruby.1.9.3.dylib and libruby.1.9.3-static.a?
>> 
>> There's no reason why the library version number should match the program version number. Usually they don't match. 
>> 
> 
> Okay. I wonder if this problem would vanish if the vim and MacVim ports allowed for variants according to the different ruby versions. They do this for python, but not for ruby.
> 
> 

Maybe. All I know is that based on the output you showed, ruby and ruby19 appear to conflict at this time, so you can only have one or the other active. You should not force the activation; that will just confuse and break things.

To fix things now, force-deactivate both ruby and ruby19, then activate the one you want to keep.