This bug has been present since at least the 5.14 kernel. It's
profoundly annoying and shouldn't have been allowed to slip into
production release. Maybe someone could fix the problem this year?
It's really pathetic when things that worked perfectly 20 years ago
are broken because of shoddy code
On 2023-01-23 03:11:59 +0100, Vincent Lefevre wrote:
> On 2006-10-14 15:56:10 -0400, Thomas Dickey wrote:
> > On Sat, Oct 14, 2006 at 08:20:14PM +0200, Andrew Moise wrote:
> > > I still see this misbehavior with xterm 210-3.1 and
> > > linux-image-2.6.17-2-686 2.6.17-9.
> >
> > I can see it
On 2006-10-14 15:56:10 -0400, Thomas Dickey wrote:
> On Sat, Oct 14, 2006 at 08:20:14PM +0200, Andrew Moise wrote:
> > I still see this misbehavior with xterm 210-3.1 and
> > linux-image-2.6.17-2-686 2.6.17-9.
>
> I can see it (now) with a 2.6.15 kernel (814 lines copied).
> I also note that
I still see this misbehavior with xterm 210-3.1 and
linux-image-2.6.17-2-686 2.6.17-9.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
On Sat, Oct 14, 2006 at 08:20:14PM +0200, Andrew Moise wrote:
I still see this misbehavior with xterm 210-3.1 and
linux-image-2.6.17-2-686 2.6.17-9.
I can see it (now) with a 2.6.15 kernel (814 lines copied).
I also note that Branden got no followup from the kernel people.
--
Thomas E.
5 matches
Mail list logo
