For this current project I’m on, I’ve resolved to give Eclipse a try. This is a major step for me, because my fingers have been typing vi commands for 20 years now, and it’s really hard to get out of the habit of typing “[escape]jjjjj” or “ZZ”. Everybody else here laughs at me because besides etags and the syntax colouring of gvim, I don’t have all the fancy stuff that they have. On the other hand, I can do everything through a ssh connection and can keep my hands on the home row.
Oh well. Welcome to the 21st century. Here’s your kazoo.
I bet you go back to vi in a few weeks. I switched from emacs to eclipse for a brief time and then went running back to emacs.
I got tired of eclipse’s spite in ignoring the perfectly good ant build file and having its own ideas about classpaths, locations of jars and source files and other stupidities.
In doing so I have reduced my eclipse support workload by one third; now I just have to help my two underlings when eclipse bites them on the ass.
There’s a “viplugin” for Eclipse that will give you your vi movement and basic commands, letting you more or less keep your hands on the home row a great deal more than you would otherwise be able to.
I gave eclipse (and the viplugin) a month or so… and I never got to the point of being happy with it.
So I switched to netbeans. Netbeans can use jVi as a plugin, and the vi-ness of jVi is far, far, far better than viPlugin, but still a bit short of (g)vim(m). I was as productive with Netbeans in two days as I was with Eclipse after a month.
(However, I *still* go back to gvim now and again. Netbeans doesn’t mind.)