[Bug 49780] wineconsole mistakenly reports VT sequence support

[WineHQ Bugzilla]

https://bugs.winehq.org/show_bug.cgi?id=49780

Ron Yorston <rmy at pobox.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |rmy at pobox.com

--- Comment #7 from Ron Yorston <rmy at pobox.com> ---
I agree with magiblot, fixing the parameter validation is a good first step.
There's nothing *wrong* with a console that doesn't support Virtual Terminal
sequences. That's how it has been on most versions of Windows until recently.
But failing to report that the Wine console *doesn't* (currently) support VT is
problematic for applications.

My interest here is that I maintain a port of BusyBox to Windows
(https://frippery.org/busybox). I've recently changed its default behaviour so
it calls SetConsoleMode to determine whether VT sequences are supported. If
they are (as with recent Windows 10 consoles) it uses them, if not it uses the
console API to emulate them.

This results in ugly escape sequences being visible in the Wine console. There
is a workaround: it's possible to set an environment variable to turn off the
auto-detection of VT support. But it would be better if SetConsoleMode was more
accurate in its response.

-- 
Do not reply to this email, post in Bugzilla using the
above URL to reply.
You are receiving this mail because:
You are watching all bug changes.