On Fri, 22 May 2026 10:12:40 -0400 Greg Wooledge <[email protected]> wrote:
> On Fri, May 22, 2026 at 12:28:29 +0100, Darac Marjal wrote: > > > > 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)"? > > It's the *output* of script, though it could have been mangled during > email tranmission. > > If the log hasn't been mangled, then simply "cat"ing it on a compatible > terminal should leave the terminal in some sort of state resembling > what the OP saw on their terminal while recording the session. However, > there's a non-zero security risk in doing this (some terminal emulators > may execute commands when given certain escape sequences), so I would > not advise it. > (I think I have seen the 'non-zero security risk' thing happen several times recently, probably when using the scroll-wheel to look back through a session log and, I think, on one occaision when I decided to remove dirt from the ball contact points without turning the trackball off first.) Normally I work at an OpenBSD XServer, just the base system with no packages added except firmware by the OpenBSD installer, and ssh into whatever box has the application package to be used. The problem was first noticed in this environment but I did not think the scope narrow enough to ask anyone about it until it was seen on the Debian box without ssh being involved. The script *output* included in the body of the first email, wine-python-debian, is attached. It was collected with a monitor, keyboard, and trackball, connected to the Debian box and all input was via the keyboard with trackball focusing assistance. No ssh into the Debian box in other words. It seemed to me the 'cat' interpretation of the script output file did not accurately represent what was seen on the terminal as the characters were being typed. Specifically all of the '>>>' lines displayed except those terminated by a typed-in 'Enter' looked blank in part with the input cursor at an apparently random position on the latest line. The script *output* attached as wine-python-openbsd-xserver shows what happens with the 'import subprocess' statement in a Microsoft Windows 'py -3.14' session, a Debian 'wine python' session, and a Debian 'wine cmd python' session. The 'pythonw' command is accepted in wine but does nothing visible. OpenBSD 'less' translates the 'square with four things in it' symbol as ESC in both attachments.
wine-python-debian
Description: Binary data
wine-python-openbsd-xserver
Description: Binary data
