4 ms·
I switched to vi (vim) a number of years ago after a number of years writing Java with Eclipse (& JBuilder). At first I thought it would be difficult to do wit
by swehner 13y ago
I switched to vi (vim) a number of years ago after a number of years writing Java with Eclipse (& JBuilder).
At first I thought it would be difficult to do without auto-completion. But it's not much of a loss after all. One learns and adapts.
I like that I can work on any host that has vi, which all actually do.
- hrjet 13y agoI love myself some vim whenever I get the chance, but to me, it is not auto-completion that is the killer feature of IDEs; rather, it is the immediate error checking that I get as I type code.
- chrisgw 13y agoThere are a number of auto-completion plugins for vim. So even that isn't a loss. There's also Syntastic for syntax checking. I found the biggest benefit of using vim is the fact that I don't have to switch between different IDEs for different languages. I can use vim for everything.
- jebblue 13y agoI love how in Eclipse when I edit something and it's wrong I get a nice little red X icon even before I hit Ctrl+S so right away I know something is wrong. If that error affects other files, the affected files in the Package View light up too. It's as easy to refactor 1 file as 1000. I use vi for quick edits of files but not my precious Java code.