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

Previous Next

Full log

Message #359 received at 78474 <at> debbugs.gnu.org (full text, mbox):

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: Re: bug#78474: 31.0.50; Wrong char insertion in rxvt
Date: Wed, 23 Jul 2025 14:22:40 +0300

> Date: Tue, 22 Jul 2025 20:15:51 +0200
> From: Samuel Thibault <samuel.thibault <at> gnu.org>
> Cc: Seb Hinderer <Sebastien.Hinderer <at> inria.fr>, rpluim <at> gmail.com,
> 	bzg <at> gnu.org, 78474 <at> debbugs.gnu.org
> 
> Eli Zaretskii, le mar. 22 juil. 2025 17:26:06 +0300, a ecrit:
> > > Eli Zaretskii (2025/07/22 16:18 +0300):
> > > > What we need is to implement a prototype of the change to disable the
> > > > above, and then time it on a large enough buffer.
> > > 
> > > Assuming the time actually does depend on the buffer's size, whihc I am
> > > very not convinced about.
> > 
> > The buffer size is a means to get a good average measure of the speed.
> 
> But it also makes saving one byte even less a bonus... I tried to write
> 100 right-left movements (\t\b\b vs \e[C\b) at a time, the \t\b trick
> takes ~30s while the standard \e[C takes ~5s.

As I wrote elsewhere, I'm interested in a real-life test case, such as
paging through xdisp.c or some other large C source file.  Synthetic
test cases are less useful in this case.

Previous Next

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