On 22/05/2026 11:18, Dan Ritter wrote:
nwe wrote:
On 5/21/26 3:10 PM, Roger Marsh wrote:
[?25l[?25l[?25h[?25l[?25l[?25h[?25l[1;35m>>>
[0m[?25h[?25l[4D[?25h[?25l[?25h[?25h[?25l[4C[?25h[?25l[?25l[?25h[?25l[?25l[?25h[?25l[4D[?25h[?25l[1;35m>>>
That looks like escape codes?
Yes. Roger's capture is unreadable unless you know or can guess
the exact terminal type he is using and can interpret those
codes.
Is this actually input to "script(1)"? Script produces a "typescript"
and, although the man page isn't explicit, it's conceivable that the
format is tuned for itself. The OP did start by saying "the script
shows...".
As for the original problem, it seems that python.exe is maybe making
some assumptions about the terminal which wine isn't handling correctly.
I would probably start by seeing if the bug is reproducible in "wine
cmd" and "wine pythonw" (it's been a while since I used pythonw; it
might *not* offer an interactive prompt).
It's the sort of thing which happens when there's a program
thinks that it is sending to a terminal but is actually sending
to a file.
And it's the sort of thing which everyone tends to do once, then
they realize their mistake and double-check in the future.
It's also likely that it has nothing much to do with the odd
behavior that he's trying to report, but it certainly obscures
whatever that is.
-dsr-
