Proposed tip Please edit this page to improve it, or add your comments below (do not use the discussion page).

Please use new tips to discuss whether this page should be a permanent tip, or whether it should be merged to an existing tip.
created August 3, 2013 · complexity basic · author Eugenekorpan · version 7.0

After upgrading Ubuntu to version 13.04, Vim may not work with the command-t plugin.

First I tried an old way

sudo apt-get install vim-gnome

by default it installs Vim version to 7.3 with the patch about 545 when try to use command-t get error

Vim: Caught deadly signal SEGV
Vim: Finished.
Segmentation fault

Found out this is due to bug in Vim.

Tried to build latest Vim version from source according to these instructions.

Got problem when compiling Vim with ruby support (and gvim).

Checked many posts and all of them say to use mercurial (don't know why).


Build Vim 7.4 from source using git mirror. Don't know how and why but with sources from git it worked for me

git clone
./configure --with-features=huge --enable-rubyinterp --enable-gui=gnome2
sudo make install

After that I've got Vim 7.4b, gvim and with ruby support.

Now ready to install command-t.

I installed it with vundle.vim (I think no matter how to install it).

Go to plugin directory and according to installation instructions

cd ~/.vim/ruby/command-t

(in a case with vundle it is in ~/.vim/bundle/Command-T/ruby/command-t)

ruby extconf.rb

Important: Run those with ruby 1.8.7. Didn't play with other versions but with 2.0.0 definitely didn't work for me Could be problems with RVM.

Even if you explicitly set version to 1.8.7 it still uses 2.0.0. Probably due to default version. I tried to change default version bu 1.8.7 but no luck.


rvm uninstall 2.0.0


  • Ubuntu 13.04
  • Build Vim from sources
  • Use Vim 7.4b version
  • Use git repository to fetch sources
  • Compile with ruby support
  • Compile with gnome gui support
  • Use Ruby 1.8.7

Comments[edit | edit source]

"checked many posts and all of them say to use mercurial (don't know why)"

Probably because the official Vim repository is in Mercurial at The Github repository you cloned is only a mirror of the official Mercurial repository. But if you're more familiar with Git, then it should work just as well. It is just not updated as frequently. --Fritzophrenic (talk) 14:58, August 5, 2013 (UTC)

I went through Mercurial, apt-get install vim-nox and vim-rails all of which where having a-lot of problems on ubuntu 13.04. Nerd tree would load the first file as a shared tab with 1 line showing. Also not all of my plugins would load. The repo here worked great thank you.

Guys, the Mercurial repository contains EXACTLY THE SAME STUFF as the Github mirror. If one allowed you to compile and install but not the other, you did the other one WRONG somehow. --Fritzophrenic (talk) 13:58, August 28, 2013 (UTC)
Community content is available under CC-BY-SA unless otherwise noted.