On Thu, May 21, 2026 at 01:58:25PM +0200, Vincent Lefevre wrote: > On 2026-05-21 13:16:18 +0200, Peter Dey wrote: > > So this does not appear to be a regression introduced in screen 4.8.x or > > 5.x. > > It looks like longstanding TERM-dependent behavior, which can appear as a > > regression when environments default to xterm-256color. > > Somewhere between buster and trixie, the default TERM seems to have changed > > from xterm to xterm-256color; making this appear as a regression. > > I've been using TERM=xterm-256color since December 2018, thus before > buster. But this was much after #578729 was closed anyway.
The relevant dates would be those for the Debian package you used, along with the release date which includes this change: commit 86ce25b620c52c9bdea94bf1185a274466f69b80 Author: Amadeusz Sławiński <[email protected]> Date: Fri Jul 7 18:39:34 2017 +0200 separate handling of 16 color and 256 color escapes on xterm echo -e "\e[38;5;1mtest\e[1mtest" puts both 'test' strings in same color, however in screen, second one is bright do note that defbce on, may interfere with this Bug: 50601 Signed-off-by: Amadeusz Sławiński <[email protected]> > > The fix to resolve #578729 (upstream commit 98bf413) still exists in screen > > 5.x. > > > > Given the interplay between screen, xterm, terminfo and mutt, I can't say > > which package the bug lies in. > > I suppose that only screen, xterm and terminfo settings are involved > by the redisplay (C-a C-l), which is important to trigger the problem. only screen. The checkin comment describes a regression. -- Thomas E. Dickey <[email protected]> https://invisible-island.net
signature.asc
Description: PGP signature
