Many cli go programs use https://github.com/mattn/go-isatty ( used by https://github.com/fatih/color ) to determine if they should print colored output. If there is some way to "fool" that from, that could work.
It seems silly to ask each cli program to check a env var to see if they are running inside a taskfile.
PTY redirection could work too. That way we should natively pass the "isatty" check.
Any other thoughts here?
I'd really like to use task _ exclusively but I like my colors too much (e.g.. for golangci-lint).
Many cli go programs use https://github.com/mattn/go-isatty ( used by https://github.com/fatih/color ) to determine if they should print colored output. If there is some way to "fool" that from, that could work.
It seems silly to ask each cli program to check a env var to see if they are running inside a taskfile.
PTY redirection could work too. That way we should natively pass the "isatty" check.
Any other thoughts here?
I'd really like to use
task _exclusively but I like my colors too much (e.g.. for golangci-lint).