Hi,

I have installed MacPorts through MacVim, asking for +huge +perl +ruby
+tcl etc...

I was quite surprised to observe that the ports command fetched its
own ruby, tcl etc...

These are by default available in OSx (10.6.5), so I thought this was
a real waste of resources. But MacVim works, so I did not reflect
further on this.

Until I tried to run a console version. That is a different vim all
together. And it does not understand ruby, perl, tcl etc...

That would not be a problem if I would not have any plugins that are
dependent on e.g. ruby. But recently this list drew my attention on
the CommandT, the LustyExplorer and the LustyJuggler scripts which do
need ruby.

So either I manage to keep gui and console versions in sync, or I
somehow prevent these plugins from being loaded for console vim.

I suppose that there will be some solution to achieve the latter, but
wouldn't the former be nice: only one single vim version in the
system!

I would like to hear your advice about how to proceed.

TIA, Guivho

-- 
You received this message from the "vim_mac" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php

Reply via email to