Stuff with the Perl Foundation. A couple of patches in the Perl core. A few CPAN modules. That about sums it up.
Now that I've returned to a "normal" development environment, I've found that I miss many of the tools that were available in my previous place of employment. Three of the most useful are represented by the following vim mappings.
map
,t :!prove -lv %<CR>
map,T :!prove -lv % \| less<CR>
map,d :!perl -d -Ilib/ %<CR>
I think, perhaps, I should start a project to build custom vim tools to make standard Perl testing easier. I miss many of the things I had, but we had a vary standardized development environment. Right now, my tools work only because I ensure that I fire up vim from the proper directory. That's an awful limitation.
I particularly miss the tool that allowed us to be dumped directly into the debugger at a given test. Maybe Test::Harness should offer support for this which prove can exploit? (Though I'm not sure if Test::Harness is the best place for this.)
color me interested... (Score:1)
Just don't expect rapid turnarounds, not much of my time is my own in the current present.
standard directories (Score:2)
Pardon the lengthy introduction, but I hope the context will be of use.... At work, when I start working with a checkout, I do
The ww means 'work with' (the directory name is subsystem, ticket description, ticket number, and ticket status... so I can spot my trees in QA status easily).
ww is responsible for setting $ENV{CVSWORK} and replacing a few standard symlinks. This lets me refer to sections of the checkout in a standard way regardless
Re:standard directories (Score:2)
These are some interesting thoughts. I particularly like having vim consider the directory of the current buffer as the current dir. This could solve some problems. I'll have to think about how useful the rest would be, though. I think dictating a particular style of work would frustrate people.
Re:standard directories (Score:1)