I re-made a patch for VIM which works with Ruby 1.9.
It affects file src/if_ruby.c, src/configure.in src/auto/configure.
This patch provides the following features.
(This patch is for Ruby 1.9, but keeps backword compatibility.
I tested this patch works with ruby 1.8.7.)
(1) check ruby header directory in Ruby 1.9 (and Ruby 1.8).
The header directory in Ruby 1.9 is different from Ruby 1.8.
(2) using Ruby1.9 C API instead of Ruby 1.8, although, this patch
works with ruby 1.8 (keeping backword compatibility.)
(3) setting encoding of Ruby String with Ruby 1.9.
(String encoding is new feature in Ruby 1.9.)
This patch is for Vim 7.2.234(Subversion revision 1577).
Regards,
Masaki Suketa
Will this also work with 1.9.1, which (again) changed Ruby's API/ABI and
where they expect Ruby libraries to reside? If not, it might be good to
modify the patch to support 1.9.1 while changes are being made to the
Ruby code.
--
James
GPG Key: 1024D/61326D40 2003-09-02 James Vega <jame...@jamessan.com>
Sorry, I did not write my ruby environment.
I tested the patch works with:
+ ruby 1.8.7 (2009-06-12 patchlevel 174) [i686-linux]
+ ruby 1.9.1p243 (2009-07-16 revision 24174) [i686-linux]
+ ruby 1.9.2dev (2009-07-26 trunk 24278) [i686-linux]
And I have not tested with Ruby 1.9.0.
I have tested my Linux box only.
Regards,
Masaki Suketa
red-agent wrote:
> Works like a charm.
> Tested it with Ruby 1.9.1_p129-r99 on my Linux (Gentoo) box.
>
> Everything works except for some minor glitches with rubycomplete
> omnicompletion.
> Sometimes this pops up:
> `
> Error detected while processing function rubycomplete#Complete:
> line 22:
> ArgumentError: comparison of Hash with Hash failed
> Press ENTER or type command to continue
> `
>
I need more detail information to fix it.
Could you show me the script when the error message pops up?
Regards,
Masaki Suketa
See the list guidelines:
http://groups.google.com/group/vim_use/web/vim-information
At 07/29/2009 04:57 PM, red-agent wrote:
> Nothing to show, really.
> That mostly happens when trying to complete the constant, like class
> name...
I've not been able to produce the same error in my environment.
I'm not a heavy user of rubycomplete omnicompletion.
So, it seems to me to take a while to solve it.
Anyway, thank you for your reporting.
Regards,
Masaki Suketa