Re:Extreme Productivity with Screen and Vim
by pyre on Friday August 27, 2010 @07:28PM
(#1640638)
At our company, there are a lot of internal bindings for vim and emacs. You can hit a key combo, and have vim/emacs determine the base class of the perl module you're working on, and open in up in a new buffer. You can hit a key combo to open up the test module for the current module. You can hit a key combo to run the unit test that you're working on, etc.
Vim also has the 'gf' (go-to-file) keybinding while goes to the file under the cursor. It does a good job of being language specific when it needs to be. For example, if the 'file' is a perl module or java package/class it will convert "Text::Utils" or "text.utils" to text/utils{.pm,.java} and search for it in the comma separated list of paths in the &path variable (i.e. :set path). Vim auto-magically imports the perl path @INC or java path into &path (though weird local configurations aren't auto-detected, and you'll just have to write something to inject those paths into &path).
Vim also has things like NERDTree and LustyExplorer that make navigating a dev tree pretty easy.
Vim also has the 'gf' (go-to-file) keybinding while goes to the file under the cursor. It does a good job of being language specific when it needs to be. For example, if the 'file' is a perl module or java package/class it will convert "Text::Utils" or "text.utils" to text/utils{.pm,.java} and search for it in the comma separated list of paths in the &path variable (i.e. :set path). Vim auto-magically imports the perl path @INC or java path into &path (though weird local configurations aren't auto-detected, and you'll just have to write something to inject those paths into &path).
Vim also has things like NERDTree and LustyExplorer that make navigating a dev tree pretty easy.