curtis_ovid_poe at yahoo.com
Mon Jan 20 09:01:27 GMT 2014
This is the downside of vim compared to Eclipse: I'm an old-school vim user from long before plugins were so popular and easy to install. Thus, I have scripted vim to do exactly what *I* do on a regular basis. ',tb', all tests in all of my buffers are run. ',gg' (GoGo): goes to the module's tests or, if in a test, goes to the module it's testing. ',r': rebuild my project. And so on.
What this means, unfortunately, is the same problem many people have when using these tools: it's hard to sit down at someone else's editor and get stuff done. Plus, it's hard to share my setup because it's "accreted" over the years ("grown" is too kind of a word). I need to clean it up and put it out there.
IT consulting, training, international recruiting
Buy my book! - http://bit.ly/beginning_perl
Live and work overseas - http://www.overseas-exile.com/
On Monday, 20 January 2014, 9:48, Peter Sergeant <pete at clueball.com> wrote:
On Mon, Jan 20, 2014 at 7:38 AM, Ovid <curtis_ovid_poe at yahoo.com> wrote:
>I would almost claim that I get most of the common benefits of an IDE out of my vim setup (completion, debugging, testing, refactoring tools, rebuilding the project, and so on)
>Google suggests these as good starting points:
> * https://github.com/vim-perl/vim-perl
> * http://www.vim.org/scripts/script.php?script_id=556
> * http://stackoverflow.com/questions/1573782/what-are-your-suggestions-for-an-ideal-vim-configuration-for-perl-development
>Anything else you'd recommend?
More information about the london.pm