Some of my older TCCs, left in states of disarray, have other fonts. But v19 and v20 both use Andale Mono (Unicode), bold 16. All my TCCs (all my consoles) use CP437.I see the pics, but nothing changed in v20 (and it's not reproducible here).
Are you using the same Unicode font & codepage in all TCC versions?
4NT and every version of TCC from v11 to v19 didn't support ANSI, they supported a small subset of ANSI (basically just the colorization). V20 supports a much fuller set.4NTv8 and every version of TCC from v11 to v19 show my alias correctly with ANSI enabled. V20 does not.
There are a number of additional ANSI combinations that v20 supports that aren't in the documentation yet. And they don't begin with ^e[ or ^e].Every escape sequence listed in the help's ANSI reference and in "What's new" begins with ^e[ or ^e].
No.If you decide to use @, it would be a suffix, "^e[...@"... right?
The alias still *works*, it's just not displaying the escape sequence when you enable ANSI (which thinks it's an invalid sequence and discards it). This scarcely requires you to throw everything out the window.That's the alias which has displayed correctly until recently
alias /X @@ctrl-f10 1B 40 65 78 69 74
|Thread starter||Similar threads||Forum||Replies||Date|
|E||Fixed Bug with DIR /Z displaying descriptions||Support||8|
|WAD Display wrapping issue||Support||5|
|K||Fixed Prompt display will be shifted after use dir to display a filename with Chinese. (v25.00.28 x64)||Support||18|
|How to? How to display picture creation date with dir command||Support||6|
|B||Fullwidth Unicode forms display incorrectly||Support||5|