Tips for using Vim as a Java IDE? [closed]

I'm addicted to Vim, it's now my de facto way of editing text files.

Being that it's mainly a text editor and not an IDE, has anyone got tricks for me to make it easier when developing Java apps?

Some questions I have:

• How do I invoke a maven task without leaving vi?
• Can I get code completion?
• How's the syntax highlighting?

Anything else (other than "Don't do it!") that I should know about?

Some tips:

• Make sure you use vim (vi improved). Linux and some versions of UNIX symlink vi to vim.
• You can get code completion with eclim
• Or you can get vi functionality within Eclipse with viPlugin
• Syntax highlighting is great with vim
• Vim has good support for writing little macros like running ant/maven builds

Have fun :-)

I've been a Vim user for years. I'm starting to find myself starting up Eclipse occasionally (using the vi plugin, which, I have to say, has a variety of issues). The main reason is that Java builds take quite a while...and they are just getting slower and slower with the addition of highly componentized build-frameworks like maven. So validating your changes tends to take quite a while, which for me seems to often lead to stacking up a bunch of compile issues I have to resolve later, and filtering through the commit messages takes a while.

When I get too big of a queue of compile issues, I fire up Eclipse. It lets me make cake-work of the changes. It's slow, brutal to use, and not nearly as nice of an editor as Vim is (I've been using Vim for nearly a decade, so it's second nature to me). I find for precision editing—needing to fix a specific bug, needing to refactor some specific bit of logic, or something else...I simply can't be as efficient at editing in Eclipse as I can in Vim.

Also a tip:

:set path=**
:chdir your/project/root

This makes ^wf on a classname a very nice feature for navigating a large project.

So anyway, the skinny is, when I need to add a lot of new code, Vim seems to slow me down simply due to the time spent chasing down compilation issues and similar stuff. When I need to find and edit specific sources, though, Eclipse feels like a sledge hammer. I'm still waiting for the magical IDE for Vim. There's been three major attempts I know of. There's a pure viml IDE-type plugin which adds a lot of features but seems impossible to use. There's eclim, which I've had a lot of trouble with. And there's a plugin for Eclipse which actually embeds Vim. The last one seems the most promising for real serious Java EE work, but it doesn't seem to work very well or really integrate all of Eclipse's features with the embedded Vim.

Things like add a missing import with a keystroke, hilight code with typing issues, etc, seems to be invaluable from your IDE when working on a large Java project.

• How do I invoke a maven task without leaving vi?

  Maven is no different than any other shell command:

  :!mvn

  You can :set makeprg=mvn if you already have a favourite key mapping for :make.

• Can I get code completion?

  Yes, eclim is great, a bridge between vim's editing efficiency and Eclipse's Java language-specific awareness.

  <C-n> and <C-p> are not-so-great, but amazingly helpful.

• How's the syntax highlighting?

  More than good enough for a regex-based highligher.

You may want to consider tools for other vim+java purposes, like code templates (snippetEmu—default snippets suck, but customizability shines), searching for usages and going to declarations (eclim, grep, ctags), generating getters and setters (java_getset, or eclim), automatic imports (eclim). You might also need a java shell for quick experiments (the BeanShell, a.k.a. bsh).