Control: reopen -1 Control: found -1 405-1 On 2025-12-12 15:41:50 -0500, Thomas Dickey wrote: > On Fri, Dec 12, 2025 at 09:03:06PM +0100, Sven Joachim wrote: > > On 2025-12-11 20:10 -0500, Thomas Dickey wrote: > > > I see the cause, will make an update within the next day or so. > > > > Thanks. Do you intend to release xterm 405 this weekend, or should I > > cherry-pick the changes from xterm 404-c? I would prefer the former, > > but can do the latter. > > I'll release 405 this weekend (otherwise I'll be getting other reports).
Unfortunately, this does not fix the issue entirely. I've attached xterm-bug.mbox, and viewing the message with Mutt gives a line overflow, in particular (my Mutt configuration may have an influence, but see below to reproduce the issue more easily). With Mutt in GNU Screen, I still get something like https://bugs.debian.org/cgi-bin/bugreport.cgi?att=1;bug=1122519;filename=20251211-003112.png;msg=5 and even worse. To reproduce the issue more easily, I've attached Xterm.log.xz (compressed xterm log file obtained with the simple test on xterm-bug.mbox). Just run xterm -geometry 80x60 -e 'unxz -c Xterm.log.xz ; sleep 999' See the differences between xterm-403.png and xterm-405.png (attached). -- Vincent Lefèvre <[email protected]> - Web: <https://www.vinc17.net/> 100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/> Work: CR INRIA - computer arithmetic / Pascaline project (LIP, ENS-Lyon)
>From [email protected] Wed Dec 10 10:31:31 2025 From: [email protected] Subject: =?UTF-8?B?8J+nnfCfj7vigI3imYLvuI/wn4yLIENhbmRsZWxpZ2h0wqA6IExl?= =?UTF-8?B?IFNlaWduZXVyIGRlcyBBbm5lYXV4IHMnaW5zdGFsbGUgw6AgTHlvbg==?= Date: Wed, 10 Dec 2025 03:31:22 -0600 MIME-Version: 1.0
Xterm.log.xz
Description: Binary data
