[Bug] Windows Leo CLI colors fail and print escape codes instead

[damons]

🐛 Bug Report

While running any Leo CLI command that produces color text on Windows, the resulting text prints escape codes rather than producing color text.

Steps to Reproduce

1. Install Leo on Windows
2. Execute leo new test-project
3. See the attached image for the result.

Expected Behavior

Should look like this:

Your Environment

Leo 1.2.3
rustc 1.53.0-nightly (2e495d2e8 2021-04-08)
Windows 10 Home v.1909 OS build 18363.628

[damirka]

Duplicate of #609.

[damirka]

It is a Clap coloring issue, which can only be solved by turning colors off on Windows builds.

[damons]

Since I installed directly using Cargo, is there a way to turn off colors in our build while compiling on Windows?

And, also, isn't this already implemented in clap? See: https://github.com/clap-rs/clap/pull/1178/files

I'm guessing I'm missing something?

[damirka]

It's not that easy. Here's a link to Clap documentation.

Long story short:

1. Coloring library which Clap uses does not support Windows;
2. They have beta 3.0 release which changes that, but it's still beta;
3. We use StructOpt, which is a wrapper for Clap, and currently it's built on 2.33.3;

The only way for us to fix this bug at this moment is to turn off color feature for Windows builds.

[damirka]

Since I installed directly using Cargo, is there a way to turn off colors in our build while compiling on Windows?

There is a way (or at least should be) - we can specify build features in Cargo.toml. But again, only turning colors off is a solution rn.