You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There doesn't seem to be a built in way in the Windows UI to enable VT processing in a specific console instance, only to turn ConsoleV2 on or off for all console instances (and ConsoleV2 controls more than just VT processing).
It would be useful and convenient to have a setting for Clink to enable VT processing in its console host.
The text was updated successfully, but these errors were encountered:
When terminal.emulate is off, all output is passed through directly to
the console. So it makes sense to set the console flag to force console
VT emulation when emulate is 'off'.
This addresses issue #8.
Setting clink set terminal.emulate off now forces console VT emulation on a per-console basis, starting in the Proof of Concept 5 (pre-)release and later.
Update: forcing ENABLE_VIRTUAL_TERMINAL_PROCESSING seems to cause compatibility problems. I've had to revert that change. Maybe it will be feasible sometime in the future.
When Clink uses "native" terminal emulation mode (i.e. Clink expects the console itself to perform terminal emulation), Clink forces the ENABLE_VIRTUAL_TERMINAL_PROCESSING on when CMD.EXE calls it to show the command prompt.
There are problems with leaving the ENABLE_VIRTUAL_TERMINAL_PROCESSING flag set outside of Clink, though, so it also clears the flag before returning control back to CMD.EXE.
There doesn't seem to be a built in way in the Windows UI to enable VT processing in a specific console instance, only to turn
ConsoleV2
on or off for all console instances (andConsoleV2
controls more than just VT processing).It would be useful and convenient to have a setting for Clink to enable VT processing in its console host.
The text was updated successfully, but these errors were encountered: