xterm-256/24-bit colors are not supported

[nta]

The terminal does not seem able to display extended (256-color/24-bit) terminal color sequences, instead displaying a lot of escape codes.

[felixse]

Hi,
can you tell me which shell you experience this with?

[felixse]

So apparently the problem is that winpty does not support 256 colors: rprichard/winpty#108
Don't see any chance to fix this in the foreseeable future 😕

[hanskokx]

Is this why my vim colors don't show up properly?

[felixse]

Yes, exactly.
Microsoft is currently working on an official alternative for winpty (microsoft/terminal#57) that might support this, but I have no idea when this will be released

[Riebart]

Quick update: microsoft/terminal#57 is officially closed, that TTY API is coming in the fall release of Windows 10.

[felixse]

Yes, i read the blog post, this will be good. I plan to implement it once it hits the release preview update ring.

[Jaykul]

@felixse is this closed because it's fixed now? Because I downloaded 0.4.1 yesterday, and was just about to file this as a bug 😉 (thanks to node-pty 0.8 VS Code fixed this awhile ago, and Hyper got this fixed in their canary builds, so I was expecting to see it would work here too ...

[Riebart]

This works on Windows 10 1809 when not using winpty as the console backend. So give that a whirl and see if it is still an issue.

[Jaykul]

That's weird. I'm happy to open a new issue to discuss this, but isn't WinPTY meant to be the new hotness? How is it working without that, but not with!?

[Riebart]

ConPTY is the new wrapper provided by the Windows kernel starting in 1809. WinPTY was the previous third party wrapper, and while may grow to support ConPTY, for our needs using ConPTY is supported directly by FluentTerminal.

[Jaykul]

Seems like that checkbox should be off by default, then.

[Riebart]

My understanding is that ConPTY support is still experimental in FluentTerminal, hence why it isn't the default.

[horseinthesky]

I really don't know what WinPTY and ConPTY are. What is the reason of my nvim in SecureCRT looks like this

And nvim in FluentTerminal like this?

Can it be fixed?