Micro: True Colors don't show on Windows, no matter what

[tr4g]

Description of the problem or steps to reproduce

Specifications

Commit hash: f594686
OS: Windows 10
Terminal: Many

Hello. So i've tried almost every relevant terminal for Windows 10: regular Console, Microsoft Terminal, MinTTY, ConEmu, Cmder, and the PowerShell terminal which is pretty much the same as CMD.

I've set the environment var MICRO_TRUECOLOR to true every time, but no matter what , i keep getting basic colors.

Mouse interactions, however, work pretty well on most terminals, interestingly enough.

[Calinou]

Try set MICRO_TRUECOLOR=1 instead of set MICRO_TRUECOLOR=true.

[tr4g]

Try set MICRO_TRUECOLOR=1 instead of set MICRO_TRUECOLOR=true.

Thanks for your answer. Just tried that and got the same result.

Just FYI, in the same console window I get the colors perfectly fine if I enter into WSL (typing bash) and run micro from inside Ubuntu

[tr4g]

Here I have recorded micro working on both WIndows and Linux (WSL) in the same terminal:

COMPARISON: Windows vs Linux in the same terminal

https://share.getcloudapp.com/kpuLxE9e?embed=true

[Yevano]

Came here to say that I'm having the same problem. I looked into it and it seems the backend library tcell supports only 16 colors on Windows. https://github.com/gdamore/tcell/issues/187

I don't really understand why there is even an issue with Windows, as the console supports the same ANSI escape codes.

[mardukbp]

The author of tcell just posted that a PR is coming that will implement the missing functionality!

[mardukbp]

Yesterday the author of tcell commited the necessary changes and zyedidia/tcell was also updated. I just compiled the HEAD of master and it works! Just do the following before running micro: set MICRO_TRUECOLOR=1

Thank you @zyedidia!

[vazub]

Appears to be fixed in 2.0.8 - cfcb2e4, if env variable set to MICRO_TRUECOLOR=1

[Yevano]

@tr4g Could you verify if this works for you now?

[tr4g]

It works fine now, thank you very much :)

Mouse interaction still doesn't work in Windows Terminal, but I think it's a different issue