Command-T 1.3 released
It’s been a while since I cut a release of Command-T, the powerful, open source file and buffer-navigation plug-in inspired by the "Command-T" feature in TextMate, so here it is: version 1.3.
What’s changed since the 1.2.1 release
This release adds the g:CommandTMaxCachedDirectories
option, which means you can use multiple, per-directory caches (useful if you tend to switch around a lot among a set of directories). It also adds a new "jumplist" finder (thanks to Marian Schubert for the patch), accessible using :CommandTJump
(which you can bind to something useful like <Leader>j
). The neat thing about the jumplist is that, Vim settings permitting, it persists across restarts of Vim, making the jumplist finder a great option for moving around frequently edited files, regardless of where they live on disk.
As always, a full change-log appears under HISTORY in the documentation, and you can explore the commits in the release here. (Note: the integrated repository browser that I’m linking to here is still relatively new and doesn’t have a full feature set yet.)
Installation
Command-T is a combination of C, Ruby and Vim’s built-in scripting language, which means that you need not only Ruby and a suitable C compiler on your system, but you also have to make sure you use compatible versions. That is, you can’t link your Vim against Ruby 1.9.2 and Command-T against Ruby 1.8.7 without things going "Boom!". For some reason, people love playing with different Ruby versions, via RVM and other means, and this has generated no small number of tickets in the issue tracker.
Windows is the worst platform of all, unsurprisingly. Getting Ruby, Vim and Command-T working together on Windows is similar in difficulty to transmuting lead into gold; if anything, transmuting may be easier.
So, if you’re unfortunate enough to be using Windows, or if you’re the sort that likes to play with different versions of Ruby, all I can do is encourage you to read the documentation very, very carefully — I’ve done my best to make it accurate and comprehensive — stick to the recommended, known-working versions, and maybe watch the installation screencasts on the Command-T product page.
Pathogen users
$ cd path/to/your/pathogen/bundle # probably ~/.vim/bundle
$ git clone git://git.wincent.dev/command-t.git
$ cd command-t
$ rake make
$ cd path/to/your/pathogen/bundle # probably ~/.vim/bundle
$ git clone git://git.wincent.dev/command-t.git
$ cd command-t
$ rake make
And in Vim:
:call pathogen#helptags()
See the docs for more info on installing (and updating) Command-T via Pathogen.
Everybody else
- Download the vimball from the Command-T product page (or www.vim.org, if you prefer)
- Open the vimball archive in vim, and do
:so %
to unpack it
cd ~/.vim/ruby/command-t && ruby extconf.rb && make
Screencasts, donations and source code
:so %
to unpack itcd ~/.vim/ruby/command-t && ruby extconf.rb && make
If you’re a Vim user check out the screencasts and give the plug-in a try. If you’d like to support development you can use the donations page to make a donation, or consider submitting a patch for the project (the source code can be browsed here).