Pass ANSI Escape Sequences up to the Console

[austinwagner]

Currently ConEmu cannot process escape codes generated by applications running under the Windows Subsystem for Linux because they are processed before they can reach ConEmu (as stated in ConEmu/ConEmu#573). These sequences should be passed along to be handled at the console level.

[musm]

Desperately needed. I mean apple fanboys always try to show off with fancy iterm2, while I hide in the corner living in an 8-bit world.

[rfc1459]

This not only breaks (potential) 256 color support, but also causes serious issues with basic ANSI functionality (arrow keys among other things - which have been worked around in ConEmu).

Simple reproducer for ANSI reverse:

printf "Normal\n\x1b[7mReverse\x1b[0m\nNormal\n"

The "reverse" sequence is silently swallowed and interpreted locally by the console emulation layer before it can reach ConEmu, so in plain bash.exe it would display "Reverse" with fg/bg swapped, but in ConEmu fg and bg are not swapped.

If you want a more complex reproducer, fire up aptitude in both plain bash.exe and ConEmu: the former will correctly highlight the current item, the latter won't because aptitude uses ANSI reverse for the current item.

[ysc3839]

The bash.exe uses SetConsoleMode setted ENABLE_VIRTUAL_TERMINAL_PROCESSING (MSDN). And we can get original ANSI sequences after disable it.

[Maximus5]

We can't get original ANSI. They are written directly into conhost memory. That means one console line would have few chars instead of full line of data.

[antitoxic]

I am also looking forward this. ref: #345 (comment)

@ysc3839 how do I do this? Are you sure it's possible?

[ysc3839]

@antitoxic I hooked SetConsoleMode then clear the ENABLE_VIRTUAL_TERMINAL_PROCESSING bit. But ConEmu can't process them.

[be5invis]

@Maximus5 We should push for the official PTY API, instead of hooking.