On Sat, 23 May 2026 13:31:38 +0000 Roger Marsh <[email protected]> wrote:
> 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. > > > > The script *output* included in the body of the first email, > wine-python-debian, is attached. It was collected with a > > The script *output* attached as wine-python-openbsd-xserver shows what > happens with the 'import subprocess' statement in Whoops. I think I should have given the two attachments in my previous email the '.txt' extension. Anyway I cannot open them here directly from the email. Saving them first seems ok though. With or without '.txt' extension.
