color VS urfave/cli

So i have a cli tool thats outputting some text to the cli stdout, i would like the output to be colored, so i used a library called color (github.com/fatih/color), basically the problem is when i output to stdout its fine but when i do something like ./tool | tee -a file.txt the colors disappear from terminal and also not in the output file, why is that and how do i prevent that ?

printer.go - Handles printing (showing) information to the user. This is where fatih/color is being used, so we can print pretty information with colors.

Note, you also need to handle piping to other programs or sending output to a file. See the logic in https://github.com/fatih/color/blob/master/color.go, https://github.com/mattn/go-colorable and https://github.com/mattn/go-isatty.

The platform I'm using is Windows, and I found that prior to Win10 there was no support for ANSI escape codes in the command line, but I have Win10 and am pretty sure my version is up-to-date enough to have this support. I have also been successfully using Fatih's color package, so I had assumed that the escape codes were working. But they are not working when I do it manually, so fmt.Print("\033[F") does not work.

same person that wrote this module i use all the time. https://github.com/fatih/color ???

I am using github.com/fatih/color as an example because it is a very simple library to test this problem out with.

I would use bytes.Contains instead of string.Contains and I would use github.com/fatih/color for ansi colours rather than re-implienting it yourself. Best not to call log.Fatal in functions other than main - it makes testing hard. Instead they should return an error after their main return value.

What’s the benefit over a well established library such as https://github.com/fatih/color ?

Can you use a framework like urfavecli https://github.com/urfave/cli? This will auto-update every time it detects a new version from your CLI's GitHub repository

I use https://github.com/urfave/cli for local development over cli parameter inside docker over envs

....\Softwares\go\src\prysm\cmd\prysmctl\checkpointsync\cmd.go:3:8: cannot find package "github.com/urfave/cli/v2" in any of:

urfave/cli - A simple, fast, and fun package for building command line apps in Go;

and probably something else will be added in the future. The final kind of launch command would like to see such djob [options] - command. Command is the command (with arguments to run). -- should separate the arguments of the utility from the arguments of the program to run. There are several excellent solutions for working with command-line arguments, such as spf13/cobra or urfave/cli. But they’re good for building an interface out of a lot of commands, and for one (as in my example) they’re redundant. So I used the flag library. I have defined the following structure with arguments:

There are alternatives available for Cobra as well i.e. mitchellh/cli, go-flags, urfave/cli etc.

https://github.com/urfave/cli - A Golang package used to structure the CLI.