Good point about taint mode. And -l
can't hurt either, so I'm adding it too, though in all my new projects I've stopped with the (h2xs
-originated, I think) legacy of putting everything under lib/
. Well, actually if it's a web project I *do* use lib/
etc); but otherwise it's just snappier to use the main directory as the root for libraries.
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.