Bug#949139: xterm: ls --color with errors piped to less sometimes corrupts the xterm status (split escape sequences)
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 reproducible with
>
> /bin/ls -bFv --color -l -R /run | less
>
> That's rather strange.
The xterm logs show that stdout and stderr are mixed up in different
ways, which explains that the bug does not occur with the second
command. In short, there's some kind of race condition, and I suppose
that the difference is caused by a slightly different timing between
both commands. This *might* also explain why I cannot reproduce the
bug in other terminals.
--
Vincent Lefèvre <vincent@vinc17.net> - Web: <https://www.vinc17.net/>
100% accessible validated (X)HTML - Blog: <https://www.vinc17.net/blog/>
Work: CR INRIA - computer arithmetic / AriC project (LIP, ENS-Lyon)
Reply to: