Closed GoogleCodeExporter closed 9 years ago
Related? : http://superuser.com/q/553601
See also: https://groups.google.com/d/msg/vim_dev/Tbk8ZXxOIVA/uPXfhHb_3AYJ
Original comment by akej...@gmail.com
on 22 Oct 2014 at 10:52
Can you reproduce the problem with the latest version? There were some fixes
(e.g. 7.4.389)
Original comment by chrisbr...@googlemail.com
on 22 Oct 2014 at 3:33
This problem has disappeared for some time on my laptop, and I guess that fix
works for this issue. Thank you!
Original comment by wanghong...@gmail.com
on 22 Oct 2014 at 3:55
Fixed (probably by 7.4.389)
Original comment by chrisbr...@googlemail.com
on 22 Oct 2014 at 3:58
It looks like 7.4+ isn't yet available on an official Debian *stable* repo (not
even backports)...
Wang, did you end up installing from source or from testing/unstable?
Original comment by akej...@gmail.com
on 22 Oct 2014 at 4:28
Yes, unfortunately, there does not seem to be more recent versions for stable
Debian.
I also use Debian but since I like the most recent vim versions, I usually
self-compile into ~/local
It is not hard and there are plenty of instructions how to do so.
Original comment by chrisbr...@googlemail.com
on 22 Oct 2014 at 4:51
Yes, I'm using Debian testing, but seems that the vim package in Debian repo is
not compiled with ruby support. So I end up installing it from source.
Original comment by wanghong...@gmail.com
on 23 Oct 2014 at 3:03
There are plenty of vim packages in Debian which have ruby support.
$ sudo apt-get install vim-ruby
[sudo] password for jamessan:
Reading package lists... Done
Building dependency tree
Reading state information... Done
Package vim-ruby is a virtual package provided by:
vim-nox 2:7.4.481-1
vim-gtk 2:7.4.481-1
vim-gnome 2:7.4.481-1
vim-athena 2:7.4.481-1
You should explicitly select one to install.
E: Package 'vim-ruby' has no installation candidate
I just uploaded 7.4.488 tonight, so it should hit testing in 10 days (if
nothing delays it). I'll try to get around to uploading that to backports at
that point, too.
Original comment by vega.james@gmail.com
on 23 Oct 2014 at 3:18
Thank you for the information!
Original comment by wanghong...@gmail.com
on 24 Oct 2014 at 1:43
Original issue reported on code.google.com by
wanghong...@gmail.com
on 12 Sep 2013 at 8:44