When I worked for a real estate listing website in ‘99, the language was perl and we were using MKS Tools (so that we could simulate nix over windows) and basically VI was what most people were using. My impression was that thing thing was just “wrong”. I looked at it as the equiv of notepad for windows in the sense, that it was the default editor that was always there for the particular operating system. So I saw it as a painful tool, in the opposite sense of notepad. Too cryptic, too hard to use.. too many hidden powerful things that only someone very android-like could be attracted to.
I hated the fact that I had to remember to type “I”, or else I’d get all of these strange messages at the bottom, like “mark not set”, or “recording”. Drove me up the wall.
But then I worked a contract position at a cool little seattle company selling research material for students a couple of months ago, and VI is was what the owner uses. He had a very “robust” .vimrc. I was pretty impressed by how powerfully you could customize it. And then bought Learning the VI Editor and spent an entire night doing internet VI tutorials.
The primary reason to make the permanent switch: The O.S.-independence-ness of it.
I can now work and accumulate to my .vimrc file that I use at home, and I know that no matter what job I go to (as long as it’s open source, or at least not require a windows IDE), I can use at anywhere.
I’m now using gvim on my XP machine at home, and I use a dos batch file to open up files. Having just switched from UltraEdit, where I had the benefit of projects, and a project menu where I pull open just the files I need,. I had to figure out how to come close to that convenience.
The answer was just to look up in the vi reference, how to do tabs, and how to do automatically open files on the command line.
It’s VI -p file1 file2 fileN.
So I use a dos batch file that opens VIM, and even better, I use slickrun, a Win tsr utility comes up with WindowsKey-Q to run that batch file.
So it’s just win-Q, OJ (a slickrun magicword that runs openjungle.bat, which opens my files for junglehappy.com website), and I have an Instant VI window with tabs.
The ability to do anything I’d need in UltraEdit, JEdit.. is pretty much there. It’s just simply a matter of spending a little extra upfront time for learning. The way it splits windows is so much better than the way that UltraEdit and other MDI-style apps do it.
What’s next is to start mastering scripts so that I can start writing text macros and be able to insert debugging commands, or other frequently needed text strings into my php/python/ruby code.
As far as the links section in this post, instead of trying to give you every vi link that I find helpful.. here is a link that has a healthy number of VI resources at the bottom:
The Vi Lovers Home Page