Why is unknown_cmd unable to draw ansi if it’s invoked due to a piped command?

[Claire_CJS]

Finding out about unknown_cmd was a game changer for me, because pausing in response to an unknown_command helps stop runaway errant situation.

But because I used ANSI color in my response, it was a bit long for an alias, so I simply made the alias call a bat file:

(I attached my unknown_cmd.bat to this post, or view it with a single click at https://raw.githubusercontent.com/C...ads/main/BAT-and-UTIL-files-1/unknown_cmd.bat )

My question is... Why does the ansi work for non-piped commands, but doesn’t for piped commands?

This makes me sad

 

[rconn]

ANSI is handled by Windows, not TCC.

 

[Claire_CJS]

Well then I guess that begs the question of why does Windows handle ANSI with TCC differently?

Could it possibly be something I’m doing?

CMD.exe:

Powershell:

TCC.exe:

 

[rconn]

The registry key at HKEY_CURRENT_USER\Console\VirtualTerminalLevel sets the global default behavior for processing ANSI escape sequences. Create a DWORD key (if necessary) and set its value to 1 to globally enable (or 0 to disable) ANSI processing by default.

[HKEY_CURRENT_USER\Console]
"VirtualTerminalLevel"=dword:00000001

 

[Claire_CJS]

Very interesting!

I checked, and that is actually already set as 1 for me.