Differing ANSI color palettes in TCC on Windows 11, depending on context (?).

[mfarah]

On Windows 11, when running TCC by itself (over the console host or the Windows Terminal), text coloring by TCC (like, say, when doing COLORDIR) takes one palette (I assume TCMD's own), but when coloring directly through ANSI sequences, it uses another one (which I assume is the OS's default palette). TCC running over TCMD, however, uses the same palette for both; this doesn't happen on Windows 10.

Now, these are two different computers, and it may well be that something has gone haywire on the registry of either, but I don't know if that should be it (or WHERE to look at this). TCMD.INI is the same on both computers and its configuration shouldn't be an issue, I believe (the "ANSI" directive is set to "No" in [TCMD] and to "Yes" in [4NT]; playing around with those values did not produce a difference).


(I like the new palette better, too)

 

[rconn]

TCC running by itself (i.e., a console window) gets the default console color palette or the custom palette for just TCC, depending on how you defined / saved your console settings. TCC doesn't know which; that is handled by the console host.

TCC calls the Windows API GetConsoleScreenBufferInfoEx to get the palette. It then checks TCMD.INI to see if you've defined a custom palette (in OPTION), and overwrites the Windows-defined palette if it finds one.

TCMD doesn't know or care about the console palettes. It defines a default color palette based on the stock Windows colors. It then checks to see if you defined a custom palette in the TCMD configuration (Tabs / Windows Colors).

When you're using ANSI sequences, Windows (the console host) is responsible for choosing and displaying colors.