Support ticket #1682: Help with Command-T and Ruby 1.9.2

Comments

1. Greg Hurrell 2010-09-09T05:35:59Z

   What operating system are you running on?

   How did you get Ruby 1.9.2? (via RVM? compiling from source? download from some other source?)

   Where did you get Vim 7.3? (binary download from www.vim.org? MacVim? Cream project? etc)

   What exactly is the error that is shown when you try to use Command-T? And what steps do you have to perform to see the error?

   Take a look at [/issues?product=Command-T the other Command-T tickets]; you might find something there that helps you trouble-shoot the problem.

   In general I don't recommend using Ruby 1.9 with Vim as there I've heard several reports of bugs with it.

2. anonymous 2010-09-09T07:57:27Z

   I'am working on ubuntu10.4,Yes,is Vim7.3,I was building by src and link 1.9.2,but I don't use RVM ,because I have only one version,the CommandT don't close buff widows on select file is over ,and report the "silent is 0" error,but I don't know why? the CommandT is Building don't have any error.

3. Greg Hurrell 2010-09-09T08:01:06Z

   Perhaps you are seeing the same problem that was reported in issue #1617? It appears that on some platforms/builds of Vim 7.3, $curbuf.number is incorrectly returning zero. If that is the case, you can work around it by patching the code as described in that ticket to use $curbuf.name instead, but I am hoping to see a fix go into Vim itself upstream.

4. pfzhao 2010-09-09T08:01:57Z

   and : Counter 0:slient is 0.

5. pfzhao 2010-09-09T08:13:20Z

   Yes,that is my Q!but what can I do?

6. Greg Hurrell 2010-09-09T08:16:29Z

   Either patch the source as described in ticket #1617, or use Ruby 1.8.7. Given that Vim and Ruby 1.9.x is such a buggy combination, I don't recommend that anybody use it.

7. Greg Hurrell 2010-11-04T17:36:05Z

   Closing due to inactivity.

8. Greg Hurrell 2010-11-04T17:36:12Z

   Status changed:

   • From: new
   • To: closed

Add a comment

Comments are now closed for this issue.