Ok, thanks for clarifying that. What you describe is
actually expected behavior; Command-T must always be
compiled and linked against the same version of Ruby that
Vim itself is linked against.
I try to cover this in
the documentation, particularly the "TROUBLE-SHOOTING" section,
although I am going to update it now that 7.3 is officially
out, and at least on Windows, it is now linked against Ruby
According the the output you pasted in from
vim --version, your Vim wasn't compiled with
Ruby support (note the
-ruby in the output, and the lack of
Ruby-related flags in the compilation and linking output.
for a project I want to use Python 2.7 and official Vim7.3
support this python version, but the cream version doesn't.
command-t is one of my favorite vim plugins, I just want it
became better, so I reported this issue. if you have time,
please try to fix this, it would be good, if it get fixed
before vim7.3 get popular. best regards.
Yes, I'd like to fix it. But from what you're suggesting, it
looks to be a bug in Ruby 1.9. It might be possible to work
around it inside Vim itself, or perhaps in Command-T, but
I'm not sure about it.
If you're forced to use Ruby 1.8 but also need Python 2.7,
then I guess compiling your own Vim might be the only
option, and I imagine that might be difficult on Windows.
I did a little research into command-t last night. I don't
think the problem is ruby's fault now. I tested the phrase
of crash and read command-t source code The C extension is
only used for quick match, am I right? but the matcher
works! the result lines can be selected. the highlight line
can be moved
I think the problem is on closing the matcher/prompt window,
I am not familiar with VIM script nor Ruby so I cann't do
more about this. If you have time, you can take some time to
test this issue. thanks.
So, what actually happens when you try to open the
selection? Is anything printed?
It may be related to
"$curbuf.number always returns 0 (zero) instead of
actual buffer number on some platforms/Vim versions",
so take a look at that one. Does
:ruby puts $curbuf.number ouput 0 for you?
BTW, vim7.3's with ruby 191 is really buggy, not only just
with command-t, when you open a ruby file, some errors like
prompt, sometimes when vim crashs when you use aotocomplete
of ruby. Have you notice that? or just I am using windows
BTW, I compiled vim7.3.3 with Python 2.7 and Ruby 187 on
windows, it was not so hard as imagine, vim works well now!
And I noticed command-t ruby extension cann't be compiled
with MS VS compiler, because MS VS doesn't support c99, and
command-t doesn't always declare variable at begining lines
of a function.
No I haven't noticed it as I am not using Ruby 1.9, nor in
Vim nor anywhere. (In fact, I only have it installed under
RVM so that I can test different
versions of my software against it.) I've always been a bit
puzzled by people's desire to start using 1.9
everywhere and as soon as possible; for me
Vim is a tool for getting jobs done, and Ruby too, so
there's no reason why I would ever use anything other than
the system Ruby (which for me right now means 1.8.7).
I totally agree with you. But in open source ecosystem, many
things (software) are linked together just like food chain.
For me, I am not using Ruby, instead, I use python
everywhere ruby may be used, but I like command-t, so I have
to install ruby :), I even thought about to learn the
spirits of your code and rewrite command-t in Python!. Just
because I want to use Python 2.7 and utilize some new
features, vim 7.3 involved and then ruby 19, the food chain
has been established. After the struggling, I think I will
just stay on Ruby 1.8.7 as Long as possible, as my present
requirement is just make command-t work, and it works well
in Ruby 1.8.7.
I had the same problems with gvim 7.3 and Ruby 1.9.1 as
mentioned above. After investigating this a little bit, I
realized it has something to do with the Ruby binding
itself. For example, VIM crashed after accessing a global
variable in Ruby plugin code.
However, I found a solution in installing "Vim without
Cream" from the Cream website, together with Ruby
1.8.7. This combo works like a charm with command-t and
other Ruby plugins, like LustyJuggler for example.