Bug#797480: duck: Commandline option to enforce color even if output doesn't seem to go to some terminal

[Simon Kainz]

tags 797480 pending
thanks

Hello,

branch v0.8 now handles --color=[always,auto,never] Please give it a
try, eventually.
I will try my best to release v0.8 soon.



All the best,

Simon



Am 2015-08-31 um 01:02 schrieb Axel Beckert:
> Package: duck
> Severity: wishlist
> Version: 0.7
> 
> Hi Simon,
> 
> it would be nice if there would be a way to tell duck it should always
> use colors even if output seems a pipe (similar to "grep
> --color=always").
> 
> I'd like to have that for cases where I call "duck | tee duck.log" but
> still watch it on the terminal.
> 
> Actually I noticed the issue when using duck via debuild's lintian hook
> in ~/.devscripts:
> 
> DEBUILD_LINTIAN_HOOK="if [ -d %p-%u ]; then cd %p-%u; duck; elif [ -d %p ]; 
> then cd %p; duck; else exit 1; fi; true"
> 

Bug#797480: duck: Commandline option to enforce color even if output doesn't seem to go to some terminal

[Axel Beckert]

Package: duck
Severity: wishlist
Version: 0.7

Hi Simon,

it would be nice if there would be a way to tell duck it should always
use colors even if output seems a pipe (similar to grep
--color=always).

I'd like to have that for cases where I call duck | tee duck.log but
still watch it on the terminal.

Actually I noticed the issue when using duck via debuild's lintian hook
in ~/.devscripts:

DEBUILD_LINTIAN_HOOK=if [ -d %p-%u ]; then cd %p-%u; duck; elif [ -d %p ]; 
then cd %p; duck; else exit 1; fi; true