Skip to main content

Install Command-T on Windows

Command-T is one of the most powerful Vim's plugins but install it on a Windows box could be a bit of pain in the ass little frustrating ;).
Here I'll post a step by step guide on how to install this plugin from scratch.

First of all, you will need a copy of Vim compiled with ruby support (+ruby) which ins't the case of the default version that you get from the official site.
While you can compile Vim by yourself, you can also download an already compiled version from here http://wyw.dcweb.cn/download.asp?path=vim&file=gvim74.zip (ruby 2.0)
Once your download completes, extract vim.exe and gvim.exe and copy them into “C:\Program Files (x86)\Vim\Vim74”

Now, got to your command prompt and run: vim –version. Among a bunch of stuff, you should see +ruby.

In addition to the modified version of Vim, you will also have to install ruby 2.0. If you haven't already, go to http://rubyinstaller.org/downloads/ and download de x86 version of Ruby 2.0 and the according RubyDevKit. (It' s super important that you get the x86 version. I shoot myself on the foot a bunch of times with the x64 version).

Just to make sure we are good so far, open vim and (at the Vim command promp) type :ruby puts RUBY_VERSION. If everything went OK, you should see: 2.0.0.

At this point we are good to go. We have Vim compiled with ruby support and the right version of Ruby installed on our system.

To install the actual plugin, I recommend to use pathogen (https://github.com/tpope/vim-pathogen ) but you can get it by other means too. Using this package manager, you just need to clone the plugin's github repo into /vimfiles/bundle. In the case of Command-T, you will also have to build a native extension. To do so, go to Command-T's home directory and run: rake make.

If at this point you got an error, you probably forgot to init/install RubyDevKit. Just go to DevKit's installation path, and run: dk init, dk install. And then run: devkitvars.bat (this will enhance your path so you can build native extensions). Now back to command-t's installation path and again, run: rake make. This time it should succeed;

Open a fresh instance of the terminal, then open vim and at the vim's command prompt type Command-T and hit [Enter]. If everything went ok, you should see a list of files/directories that you can filter and navigate right from the editor. (By default, command-t it's bound to the <leader> + t shortcut).

Install this plugin on Windows systems is a bit of a hassle, but it well worth it. I can't imagine myself using Vim without Command-T.



If you have any trouble installing Command-T, feel free to contact me, I'll try to help.

Comments

Post a Comment

Popular posts from this blog

Moving to Medium

It's been a long time since I want to give medium a try, and finally, I made some time to do it. To get started on the new platform, I'll be doing series on "Getting programming concepts, languages and tools". If it sounds interesting to you, please take a look at the first post  Getting AWK  and spread the word if you like it. I'm not going to migrate old entries to the new web site. They will remain here safe and sound! As usual, thanks for reading!

Working with unattended reports

In this post I‘ll show you how to create reports that NRapid will execute into an unattended mode. I strongly recommend using this kind of reports in automation scenarios only , and let the user see the print preview dialog in the rest of cases. The only difference between this reports and the standard ones, is that you will cannot make use of dialogs, the runtime will always pass in empty views to the ConfigureReport method. The ConfigureReport method will be executed, but you will have to grab the arguments from somewhere else. The execution pipeline is the same that NRapid uses for standard reports. This is the code to print out the whole list of categories in a dialogless mode. Notice that this report inherits from UnattendedReport class, this class tells to NRapid “run the report unattended”. Also notice that this class comes with a convenience method to configure the report with no arguments. You still can override the one that gets the view data but you will always

How to create MS Word documents from Office templates using C#

The OpenXML SDK allows you to do pretty much anything you want with office files such as Excel, Word, etc… While many people like this library, I found it complex, unintuitive and poorly documented, not to mention the awful xml format that uses under the hood to represent the documents, styles, etc. So I decided not to use it and build my own solution. If you, like me, don’t like that library, you will find in this post an alternative approach to build word documents from templates using c#. A neat trick to work with Office is to use the macro recorder to understand how things work. The macro recorder allows you to start a macro, do something by hand, stop it, and then take a look at the generated VBA code. Once you do this, you are pretty much set. This is how it looks the template I’am going to use. Note: save the file as a Word template (.dotx) This is the code to create Word documents from C#: By running the code, you should get a document that looks