Bug#949139: xterm: ls --color with errors piped to less sometimes corrupts the xterm status (split escape sequences)

2022-02-14 Thread Vincent Lefevre
Control: reassign -1 less Control: found -1 487-0.1 Control: found -1 590-1 Control: retitle -1 less: with option -R, the escape sequences should be sent in an atomic way so that they are not broken by stderr Control: tags -1 upstream - wontfix On 2020-01-30 21:21:03 -0500, Thomas Dickey wrote:

Bug#949139: xterm: ls --color with errors piped to less sometimes corrupts the xterm status (split escape sequences)

2020-01-30 Thread Thomas Dickey
On Thu, Jan 30, 2020 at 08:11:30PM -0500, Thomas Dickey wrote: ... The logfile doesn't give a clue about the screensize; there's no cursor movement in it other than to the home-position. Using unmap, which prints the escapes in visible form (and happens to split the lines on escape characters),

Bug#949139: xterm: ls --color with errors piped to less sometimes corrupts the xterm status (split escape sequences)

2020-01-30 Thread Thomas Dickey
On Sat, Jan 18, 2020 at 12:26:34AM +0100, Vincent Lefevre wrote: > On 2020-01-18 00:02:46 +0100, Vincent Lefevre wrote: > > On my machine, the problem is almost always reproducible with > > > > ll -R /run | less > > > > where > > > > zira:~> where ll > > ll: aliased to ls -l > > zira:~> where

Bug#949139: xterm: ls --color with errors piped to less sometimes corrupts the xterm status (split escape sequences)

2020-01-17 Thread Vincent Lefevre
On 2020-01-18 00:02:46 +0100, Vincent Lefevre wrote: > On my machine, the problem is almost always reproducible with > > ll -R /run | less > > where > > zira:~> where ll > ll: aliased to ls -l > zira:~> where ls > ls: aliased to \ls -bFv --color > /bin/ls > > but it does not seem to be

Bug#949139: xterm: ls --color with errors piped to less sometimes corrupts the xterm status (split escape sequences)

2020-01-17 Thread Vincent Lefevre
On 2020-01-17 23:45:20 +0100, Vincent Lefevre wrote: > This is not this issue. The problem is that xterm sets up some margin, > and the lines at the top can no longer be erased. I need to use the > "reset" command to fix things. On my machine, the problem is almost always reproducible with ll

Bug#949139: xterm: ls --color with errors piped to less sometimes corrupts the xterm status (split escape sequences)

2020-01-17 Thread Vincent Lefevre
On 2020-01-17 17:12:48 -0500, Thomas Dickey wrote: > https://invisible-island.net/xterm/xterm.faq.html#vt100_wrapping This is not this issue. The problem is that xterm sets up some margin, and the lines at the top can no longer be erased. I need to use the "reset" command to fix things. --

Bug#949139: xterm: ls --color with errors piped to less sometimes corrupts the xterm status (split escape sequences)

2020-01-17 Thread Thomas Dickey
On Fri, Jan 17, 2020 at 12:01:57PM +0100, Vincent Lefevre wrote: ... https://invisible-island.net/xterm/xterm.faq.html#vt100_wrapping -- Thomas E. Dickey https://invisible-island.net ftp://ftp.invisible-island.net signature.asc Description: PGP signature

Bug#949139: xterm: ls --color with errors piped to less sometimes corrupts the xterm status (split escape sequences)

2020-01-17 Thread Vincent Lefevre
On 2020-01-17 11:55:28 +0100, Vincent Lefevre wrote: > This is not reproducible only with xterm, not with other terminals, > such as rxvt and gnome-terminal (but perhaps the race occurs > differently). Grrr... I meant: "This is reproducible only with xterm, not with other terminals [...]". --

Bug#949139: xterm: ls --color with errors piped to less sometimes corrupts the xterm status (split escape sequences)

2020-01-17 Thread Vincent Lefevre
Package: xterm Version: 351-1 Severity: normal I've run the equivalent of ls with some options including --color piped to less with the -R option, and after quitting less, the xterm status sometimes get corrupt, apparently due to some margin set up. I've attached the xterm output log, but I can