http://bugs.winehq.org/show_bug.cgi?id=2974
Summary: winetty driver wrecks console output Product: Wine Version: 20050111 Platform: Other OS/Version: other Status: UNCONFIRMED Severity: normal Priority: P2 Component: wine-x11driver AssignedTo: wine-bugs@winehq.org ReportedBy: kuba@mareimbrium.org
- winetty seems to use ncurses for simple line-oriented output where winex11 did the right thing and didn't wrap the output with escape sequences in such a weird way
- winetty clears the screen upon startup (due to ncurses maybe), so e.g. running things from nmake.exe makes the screen get wiped everytime a compile/link step is invoked.
This has a nasty side effect: with winetty driver a simple wine foo.exe > log gives you corrupt output with escape sequences that weren't reallyoutput by foo.exe , whereas with winex11 wine foo.exe > log gives you the *correct* output capture.
I presume there should be a way in ncurses to preserve current console contents, for one. It'd be also desirable to only insert escape sequences when cursor movement is actually called for by the application itself by doing console buffer writes at locations that aren't at the current cursor position.