I wrote this piece in February. I didn’t post at the time because I wanted to link to the online Vim help files at vimdoc.sourceforge.net, but it wasn’t working properly. Two months later, it is still not working properly, so I’m posting anyway.
Everybody’s DNS seems to have switched to point to this new server, so this will be the last of “Unseen Alan”.
Vim is my all-time favourite text editor. Productivity wise, I find it better than every IDE I’ve ever used, excepting Eclipse, which I prefer for Java1.
I’m currently working on a C++ project. When we started here, we spent a few days setting up the development environment, including Vim. This is what we did:
Function keys are all set up too:
Some Vim features that have been helpful are:
Would I recommend Vim to every programmer? No. Its vi-derived, modeful, “Look Ma, No Arrow Keys Runs On A VT100, A Mac And Anything In Between interface is daunting for those who haven’t had to use vi at some stage. But for a significant fraction of the development community, Vim is the ant’s pants.
1 Though I haven’t used IDEA. Or Emacs.
My friend David has a way with words. Watch him avoid the saying the big “R”, while explaining how he spent the morning:
“I haven’t added any functionality, I’m just fixing it up, making the code a bit easier to work with.”