On Windows, we should probably try to detect if the command window supports ANSI escapes, and default to not using color if we are not sure. The situation is a bit tricky, as different console emulators set different environment variables. - Some programs (like [ConEmu](https://conemu.github.io/en/AnsiEscapeCodes.html#Environment_variable)) set the environment variable `ANSICON` (related to https://github.com/adoxa/ansicon, which also appears to set `CLICOLOR`) - Some set `TERM` (mostly bash, but for instance MSYS2 bash returns 0 for `isatty()`, explained [here](http://sourceforge.net/p/msys2/wiki/Porting/)) Most importantly though, the default command prompt does not support ANSI colors and returns true for `isatty()`.
This issue appears to be discussing a feature request or bug report related to the repository. Based on the content, it seems to be resolved. The issue was opened by jibsen and has received 5 comments.