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

Previous Next

Full log

View this message in rfc822 format

From: Robert Pluim <rpluim <at> gmail.com>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: bzg <at> gnu.org, Sebastien.Hinderer <at> inria.fr, samuel.thibault <at> gnu.org, manuel <at> ledu-giraud.fr, 78474 <at> debbugs.gnu.org
Subject: bug#78474: 31.0.50; Wrong char insertion in rxvt
Date: Thu, 24 Jul 2025 15:46:16 +0200

>>>>> On Thu, 24 Jul 2025 16:22:51 +0300, Eli Zaretskii <eliz <at> gnu.org> said:

    >> From: Robert Pluim <rpluim <at> gmail.com>
    >> Cc: Eli Zaretskii <eliz <at> gnu.org>,  bzg <at> gnu.org,
    >> Sebastien.Hinderer <at> inria.fr,  manuel <at> ledu-giraud.fr,
    >> 78474 <at> debbugs.gnu.org
    >> Date: Thu, 24 Jul 2025 12:27:44 +0200
    >> 
    >> >>>>> On Thu, 24 Jul 2025 09:57:50 +0200, Samuel Thibault <samuel.thibault <at> gnu.org> said:
    >> 
    Samuel> It was xterm.
    >> 
    >> Eliʼs scrolling test for src/xdisp.c also doesnʼt result in the use of
    >> many \t\b sequences in any case (121 in my testing, for a 39k line
    >> file).
    >> 
    >> I did the following instead, with a testfile containing 40k lines of
    >> 01234567cbaaaaaa
    >> 
    >> (progn
    >> (find-file "src/testfile")
    >> (let ((oldgc gcs-done)
    >> (oldtime (float-time)))
    >> (goto-char (point-min))
    >> (condition-case nil
    >> (while t (right-char 5) (right-char) (redisplay))
    >> (error (message "GCs: %d Elapsed time: %f seconds"
    >> (- gcs-done oldgc) (- (float-time) oldtime))))))
    >> 
    >> (this is all over a fast ssh connection, with the underlying terminal
    >> being iterm2)

    Eli> How many times was the \t\b sequence used in this test?

27151

Robert
-- 

Previous Next

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