On Tue, Oct 11, 2011 at 2:36 PM, Nali Toja wrote:
> Zhihao Yuan writes:
>
> >> Zhihao Yuan wrote on 11.10.2011 17:56:
> >>
> >> Hi,
> >>>
> >>> I specified RUBY_DEFAULT_VER=1.9 in /etc/make.conf, and rebuild
> everything
> >>> relates to ruby, and I found the successfully built Vim lacks of the
Zhihao Yuan writes:
>> Zhihao Yuan wrote on 11.10.2011 17:56:
>>
>> Hi,
>>>
>>> I specified RUBY_DEFAULT_VER=1.9 in /etc/make.conf, and rebuild everything
>>> relates to ruby, and I found the successfully built Vim lacks of the ruby
>>> support.
>>>
>>> By default, vim requires the 'ruby' comman
On Tue, Oct 11, 2011 at 1:36 PM, Ruslan Mahmatkhanov wrote:
> Zhihao Yuan wrote on 11.10.2011 17:56:
>
> Hi,
>>
>> I specified RUBY_DEFAULT_VER=1.9 in /etc/make.conf, and rebuild everything
>> relates to ruby, and I found the successfully built Vim lacks of the ruby
>> support.
>>
>> By default,
Zhihao Yuan wrote on 11.10.2011 17:56:
Hi,
I specified RUBY_DEFAULT_VER=1.9 in /etc/make.conf, and rebuild everything
relates to ruby, and I found the successfully built Vim lacks of the ruby
support.
By default, vim requires the 'ruby' command when building WITH_RUBY=1, but
ruby19 does not ins
Hi,
I specified RUBY_DEFAULT_VER=1.9 in /etc/make.conf, and rebuild everything
relates to ruby, and I found the successfully built Vim lacks of the ruby
support.
By default, vim requires the 'ruby' command when building WITH_RUBY=1, but
ruby19 does not install the command.
One solution is that t