in reply to Re^3: Test driven development with Perl and vim
in thread Test driven development with Perl and vim
I'm not sure why you need the separate binding for compilation at all? I actually see it as a feature that Prove() does the Right Thing depending on whether the file is a test or not. (After all, if your test fails compile, quickfix will put you in the right place even if the compilation error happened when you tried to run the test.) Think of it as polymorphism at keybinding time :)
Thanks for the comments!
Update: Interesting thinko on my part, taking "verbose" for "taint". Well, I suppose they both tend to produce mode output than the regular checks :) I'm not convinced a verbose launch deserves a keybinding of its own — how often do you alternate? — maybe it's better to make both taint and verbose modes global options and keep the keys simple.
|
---|
Replies are listed 'Best First'. | |
---|---|
Re^5: Test driven development with Perl and vim
by dragonchild (Archbishop) on Mar 02, 2005 at 13:21 UTC | |
by gaal (Parson) on Mar 02, 2005 at 13:46 UTC |