GNU bug report logs - #78474
31.0.50; Wrong char insertion in rxvt

Previous Next

Full log

View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Samuel Thibault <samuel.thibault <at> gnu.org>
Cc: bzg <at> gnu.org, Sebastien.Hinderer <at> inria.fr, rpluim <at> gmail.com, 78474 <at> debbugs.gnu.org
Subject: bug#78474: 31.0.50; Wrong char insertion in rxvt
Date: Tue, 22 Jul 2025 16:18:48 +0300

> Date: Tue, 22 Jul 2025 13:30:41 +0200
> From: Samuel Thibault <samuel.thibault <at> gnu.org>
> Cc: rpluim <at> gmail.com, Sebastien.Hinderer <at> inria.fr, bzg <at> gnu.org,
> 	78474 <at> debbugs.gnu.org
> 
> Eli Zaretskii, le mar. 22 juil. 2025 14:28:19 +0300, a ecrit:
> > > Date: Mon, 21 Jul 2025 18:00:47 +0200
> > > From: Samuel Thibault <samuel.thibault <at> gnu.org>
> > > Cc: rpluim <at> gmail.com, Sebastien.Hinderer <at> inria.fr, bzg <at> gnu.org,
> > > 	78474 <at> debbugs.gnu.org
> > > 
> > > I have tried the attached test which reproduces both ways and reports
> > > the time to achieve one million iteration, on my system:
> > > 
> > > - with rxvt: non-optimized way takes ~1.9s, optimized way takes ~2.1s.
> > > - with mate-terminal: non-optimized way takes ~1.8s, optimized way takes
> > >   ~2.0s.
> > > 
> > > So on my system at least the "optimized" way is actually slower.
> > 
> > For that particular single case.
> 
> Which is exactly the case that we are reporting about.

No, it isn't.  Not even if only \t\b should be disabled.

What we need is to implement a prototype of the change to disable the
above, and then time it on a large enough buffer.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.