This is my (ongoing) story about Vim in Windows. Yeah! Vim in Windows!
This is going to be question & answer, highlighting those things that I consider important to take into account.
Where should I obtain Vim for Windows?
Of course, the easiest answer is just grabbing the binary from official vim site. This should be fine if you don’t want to have the latest version with all the patches included. In addition, consider that console vim doesn’t include python/ruby/lua bindings (thanks @sudo-bang-bang for your comment!)
Since I want to use the latest version without compiling it, I’m required to search for another Vim binary. To date, I recommend one of the following alternatives:
The main difference is that the former is built using Visual Studio whereas the latter is built using MinGW-w64.
Graphical Vim vs Console Vim
You might be wondering if Console Vim in Windows is possible and has benefits.
For Graphical Vim I’m referring to gvim, nothing new here, just open it and you can use it as you’re accustomed to.
For Console Vim I’m referring to vim. Try opening it in a windows console, you should see something like this:
So, yeah… it works but it doesn’t look quite good! Moreover, if you want to have a fullscreen console window you will have to use weird hacks like this.
We can do better than that. There is a simply and powerful solution and that would be to Get rid of windows console and embrace cmder.
Once you install cmder, just open up vim. Try your favorite colorscheme like badwolf and… voilà!
Isn’t it awesome?
If for any reason this does not work for you, it might be because some settings are missing in your .vimrc (reference)
We’ve seen different Vim distributions available for Windows; we did a comparison between using Graphical vs Console Vim. This is all you need to start using Vim in Windows.
In future posts I’ll surely delve into things like How to efficiently use Vim plugins in Windows, Some tweaks and workarounds in Console Vim, Take advantage of Python support and so on.