vim安裝command-t插件

commnad-t是一個很好的vim插件 

安裝的步驟似乎很簡單，下載下傳最新版本的commnad-t，進入到.vim目錄 

一次執行： 

1. vim command-t-1.4.vba
2. :so %
3. cd ~/.vim/ruby/command-t
4. ruby extconf.rb
5. make

但是我這裡編譯出現了問題 

問題一 

1. /usr/include/ruby/intern.h:412:1: error: unknown type name ‘fd_set’
2. DEPRECATED(int rb_thread_select(int, fd_set *, fd_set *, fd_set *, struct timeval *));
3. ^
4. make: *** [ext.o] Error 1

問題原因是編譯中依賴的一些c庫，有問題，在網上查了很多資料，最後更新ruby版本解決 

1. rvm upgrade 1.9.2-p136 1.9.2-p180

問題二 

1. command-t.vim requires Vim to be compiled with Ruby support

通過 vim --version 

可以看到 字元串中赫然顯示着 -ruby 這說明vim沒有ruby的安裝依賴 

引用

One of my favourite plugins for Vim is Command-T: 

an extremely fast, intuitive mechanism for opening files with a minimal number of keystrokes. It’s named “Command-T” because it is inspired by the “Go to File” window bound to Command-T in TextMate. 

Sadly, the default installation of Vim on Snow Leopard does not have support for the ruby interpreter compiled in, which is a pre-requisite for using the plugin. Luckily, that’s easy enough to remedy, and in the process we’ll learn a thing or two about compiling your own custom Vim binary. 

Let’s start off by getting the source code from the official Mercurial repository: 

1. $ hg clone https://vim.googlecode.com/hg/ vim
2. $ cd vim

(Note: You don’t need to use the Mercurial repository – there are mirror sources for Subversion, CVS, as well as good ol’ tarballs with patches.) 

The default branch for the mercurial repository contains the code for Vim 7.2 at the time of this writing. There is also a vim73 branch available for those feeling a bit more adventurous and wishing to compile the beta release of the next version. For this article, we’ll be sticking to the stable 7.2 release in the default branch. 

Now, let’s take a look at the possible configuration options: 

1. $ ./configure --help

There are quite a few, and I suggest that you take the time to read through them – most are quite self-explanatory. For Command-T, the one that we are interested in is the 

--enable-rubyinterp 

option. 

So let’s take a shot at the simplest installation for terminal-based Vim usage, one without the GUI interface and (Linux) mouse daemon support: 

1. $ ./configure --prefix=/my/install/prefix --enable-rubyinterp --enable-gui=no --disable-gpm
2. $ make

After the compilation process finishes (presumably with no errors), the first thing you’ll want to do is ensure that the binary you just built functions as expected: 

1. $ ./src/vim --version | grep ruby
2. # you should see a `+ruby` line entry
3. $ ./src/vim

If you see the +ruby entry in the –version output and the binary launches without any errors, rejoice in your own awesomeness. That’s all there is to it. 

If, however, you see something similar to this: 

Vim: Caught deadly signal SEGV 

Vim: Finished. 

zsh: segmentation fault  ./src/vim 

you’ve probably fallen prey to a (currently) not very well documented issue: Vim 7.2 does not support the integration of Ruby 1.9.x on Snow Leopard. 

This means that if you’ve used a package manager such as Homebrew, MacPorts or Fink (shudder) to install the latest version of Ruby, Vim will link to that latest version instead of the system default installation of ruby 1.8.7. 

Let’s fix that. 

We’re going to edit the src/auto/config.mk generated by configure that was run earlier. Note that if you re-run configure at a later time, your changes to config.mk will be lost. 

Find the lines that look like this: 

1. RUBY            = /usr/local/bin/ruby
2. RUBY_SRC        = if_ruby.c
3. RUBY_OBJ        = objects/if_ruby.o
4. RUBY_PRO        = if_ruby.pro
5. RUBY_CFLAGS     = -I/usr/local/Cellar/ruby/1.9.1-p378/include/ruby-1.9.1 -I/usr/local/Cellar/ruby/1.9.1-p378/include/ruby-1.9.1/i386-darwin10.4.0 -DRUBY_VERSION=19
6. RUBY_LIBS       = -lruby -lpthread -ldl -lobjc

(Note: Your specific paths and/or versions may differ depending on the package manager that you are using. The above paths are actually not important, however, since we actually want to reset them to the system defaults.) 

and replace them with the following: 

1. RUBY            = /usr/bin/ruby
2. RUBY_SRC        = if_ruby.c
3. RUBY_OBJ        = objects/if_ruby.o
4. RUBY_PRO        = if_ruby.pro
5. RUBY_CFLAGS     = -I/System/Library/Frameworks/Ruby.framework/Versions/1.8 -I/usr/lib/ruby/1.8/universal-darwin10.0
6. RUBY_LIBS       = -framework Ruby

Alright, let’s see if this worked. 

1. $ make clean && make

Before we check the binary as we did before, let’s see if we linked to the correct ruby libraries: 

1. $ otool -L src/vim
2. src/vim:
3. 1.0.0, current version 125.2.0)
4. 5.4.dylib (compatibility version 5.4.0, current version 5.4.0)
5. 1.8/usr/lib/libruby.1.dylib (compatibility version 1.8.0, current version 1.8.7)
6. 1.0.0, current version 44.0.0)
7. 150.0.0, current version 550.29.0)

Looking good so far – the binary is linked to the framework version of Ruby that comes as a default on Snow Leopard. 

Let’s do a version check: 

1. $ ./src/vim --version | grep ruby
2. # you should see a `+ruby` line entry
3. $ ./src/vim

And voilà: A custom-built Vim with ruby integration that will happily run the Command-T plugin. 

All that’s left is to install it: 

1. $ make install