support ENABLE_VIRTUAL_TERMINAL_PROCESSING per application

[mintty]

VT escape sequence handling can be enabled by design with some Windows API call enabling the ENABLE_VIRTUAL_TERMINAL_PROCESSING mode.
(Refer #6634 (comment)).
There is also a registry feature to change the default to enable it (https://stackoverflow.com/questions/51680709/colored-text-output-in-powershell-console-using-ansi-vt100-codes/51681675#51681675).
However, it would be very useful to enable it per application, i.e. per executable, by some kind of property (settable via Explorer Properties menu and some kind of executable flag, e.g. via manifest). (Not sure whether #2035 addresses this issue.)

[DHowett]

Hey, thanks for the request! Sorry to take so long to triage it. This is a specific case of #4954, so I'm going to close this out in favor of that. There's already some investigation underway over there 😄 where I'd like to make the input AND output states process-specific.

Having it be manifested would be pretty radical.

We've talked about having a new template for command-line applications in VS that sets nice defaults and pretty much communicates to the console subsystem that "this application is a well-behaved VT-only app" -- it would enable strict mode and passthrough mode and not allow buffer readout and all of the really annoying weird parts of the win32 API.

In general, /dup #4954

[ghost]

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!