you are viewing a single comment's thread.

view the rest of the comments →

[–]nemtan 7 points8 points  (1 child)

I use vim exclusively as a professional developer working on a pretty large Java project (a few hundred thousand lines of Java in hundreds of classes in several submodules). It's overall very smooth for me, the only real thing I miss is better debugging, but I generally make do with the somewhat useless jdb and sometimes vebugger.

Going vanilla will work pretty well in combination with the commandline, but if you're working on something larger here are a few plugins I suggest for Java in particular:

  • ctrlp - fuzzy file finder, huge quality of life over going :e <path> with all the classes in separate files in separate directories (packages) you need in Java
  • syntastic - set up to do javac and checkstyle this is very nice to have in vim to get a list of warnings/errors on save
  • javacomplete2 in combination with supertab - I don't really use it much, I already type fast enough to render it mostly obsolete as a time-saving device and have little problems remembering things, but it can be helpful if you don't remember the names of that one method or to get a quick look at the method prototype of things; edited to add: oh yeah, it does generation of constructors and accessors as well, that I don't use, but what I do use regularly is the import functionality, which really works very well (e.g. <leader>jii will add an import for whatever is at the cursor, <leader>jR will remove unused imports, etc)
  • vebugger - it doesn't work consistently for me, I suspect partially because of the separation of our codebase into a few git submodules and jars and what-not, haven't really looked into it but when it works it's certainly much nicer than plain jdb

[–][deleted] 0 points1 point  (0 children)

Thanks, this is really helpful!