True color support on Windows

OS: Windows 10 Creators Update Terminus version: Alpha 15

True color doesn’t seem to work in Bash on Windows (regardless if connected to a SSH session or not), instead, all colors are approximated to the 16-color palette. This was tested with micro with the MICRO_TRUECOLOR environment variable set to 1 (true color works in cmd.exe once this variable is set).

This issue can be reproduced by using the awk snippet available in the first link (the rainbow won’t be smooth, but will be approximated to the 16-color palette instead).

Supporting true color will make using terminal applications (such as text editors with syntax highlighting) much more convenient.

[Eugeny]

True Color now available with the xterm frontend - try the nightly build! https://ci.appveyor.com/project/Eugeny/terminus/build/artifacts

[daaang]

I’m unclear about how to enable 256 colors. I even tried upgrading to 1.0.88-nightly.0, and I’m still just seeing the usual 16 colors. If I run a VcXsrv X server and run terminator (not terminus) then I can run any of these print256colors scripts, and the output is all 256 colors. But in terminus (with any of the three frontends, running WSL / Bash on Windows), the same scripts try their best but are only able to approximate with the 16-color palate.

In both cases, $TERM is set to xterm-256color. Sorry to post in a long-closed ticket, but I’m liking this terminal emulator a lot so far, and it’d be really nice to have vim set up the way I’m used to.