TCC v20 worked ok anyway. The problem is with TCC v21. You can try the trial to see if it works (chances are, it won't - you're effectively using the old ConHost with this change). I have upgraded, specifically to get the full 24-bit ANSI colors. I have regretted it, of course, but that's on me...

Just to reiterate: The only way I could make TCC (not TCMD/TCE, as apparently it doesn't support 24-bit or 256-palette color) is through this: Code to reproduce: for /l %i in (0,1,255) do (echos %@char[27][48;5;%im%@char[32]%@char[27][0m & if (%i GT 8 .and. %@eval[%i mod 12] == 3) echo.)...

I recently found out they have even implemented the DEC Drawing Line mode - they don't have *some* Linux support, they have implemented the full VT100/VT220 manual!

The API to enable VT input is part of SetConsoleMode. Just set ENABLE_VIRTUAL_TERMINAL_INPUT. There's also an example in the master page.

The third picture shows exactly that ANSI codes are enabled in my Windows console (conhost). It's a pure cmd.exe Here's its settings for reference:

I have disabled it in both but all I get inside TCMD (by which I man the Take Command Environment), are the escape codes as raw text. With ANSI=No I get that both tin Take Command Environment and standalone (Conhost-ed) Take Command Console.

As I said, Windows 10 Creators Update. The new conhost has better support for ANSI than TCMD/TCC ever had. In addition to a 256 palette color (ESC [ 38/48; 5 ) and full 24-bit color (ESC [38/48; 2), it also has support for DEC Line Drawing, underlining, positioning etc. I think that MS has...

If you disable ANSI in TCC and enable it in TCE, ANSI parsing is completely ignored. As I said, I tried all combinations. In any case, this doesn't explain the fact that it doesn't work in PowerShell. EDIT: I neglected to post my software versions: TCC 21.00.32 x64 Windows 10 [Version...

Yes, I do. Both in TCC and TCE. I also tried all 4 combinations. EDIT: In PowerShell, it's more obvious. If ANSI is off, the actual escape character is displayed. If (TCE) ANSI is on, the escape character is parsed, but it has no effect.

Obviously in Windows 10 CU (1703), the TCMD environment doesn't display 256 or 24bit colors that conhost on its own displays. I've tried it with TCC21, TCC20, CMD and PowerShell. In all cases, instead of displaying colors, black was displayed. TCC: echo %@char[27][48;2;139;0;139mtest...

Well, yes, it does. It's more-or-less required if you're working Python on the console. Well, it seems to be working in PowerShell/CMD.

If it's a Windows issue, why does it work with TCC 19 and it doesn't work with TCC 20? EDIT: This happens exactly the same under Take Command (I just wanted to isolate the problem).

BTW, isn't the version supposed to be 10.0.14393? Why does TCC go to the fallback version (6.3)?

When typing any non-US-English character, an empty character (probably 0x00-NUL) is displayed on the right of the typed character. It doesn't overwrite the underlying character (if any), but the string is displayed as if you were pressing `space` after each. The weirder part is that this only...

I know the \\.\xxx usage it's wrong. It's supposed to only be used to open \\.\C: or \\.\PhysicalDrive1 or stuff like that. I'm not expecting it to work in any TCC, it's just that since the proper \\?\ format didn't work, \\.\ was a good replacement. Anyway, to make an invalid AUX.TXT on your...