zostay/app-colorist

Add color to your plain old outputs

app-colorist's Issues

Piping into stdin does not work

This didn't work during my final testing:

cpanm Test::Pod | colorist -c cpanm

It quit with no output and cpanm did not finish (i.e., it wasn't just that the output was consumed and thrown away). I don't know that I tested this since I create App::Colorist from my original colorizer script, so this is probably something inherent with how I'm messing with the ARGVfile handle.

Sub-command and option variants

A command's output can child greatly with the addition of options and sub-commands. Need a way to identify these variants and cope.

For example, in cpanm, if you add -v, you will see all the build output. At which point, it would be nice to use a ruleset/colorset aimed at handling the make or something.

Another example is git or dzil, which might have different colors based upon the sub-command (git show versus git name-rev, dzil test versus dzil release, etc.) being run. These might also just be cases of having really large rulesets, but there are cases where options might require a different set of rules.

Aliased command flags

Hello,

It seems the aliased cpanm command can't accept command line arguments/flags:

cpanm -v App::Colorist
Unknown option: v
usage: colorist [-?CcEehIR] [long options...]
        -h -? --usage --help   Prints this usage information.
        -c --configuration      
        -R --ruleset            
        -C --colorset           
        -I --include            
        --debug                 
        -e --execute            
        -E --stderr 

Unable to locate rules

Hello,

Just installed App::Colorist (0.142540) from CPAN under perl-5.16.1, but on first run I got this error:

colorist -E cpanm App::Colorist
Unable to locate rules "rules" in paths: /home/arpi/.colorist /etc/colorist at reader App::Colorist::Colorizer::ruleset_file (defined at /home/arpi/.local/opt/perl5/perls/perl-5.16.1/lib/site_perl/5.16.1/App/Colorist/Colorizer.pm line 132) line 7.