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

Previous Next

Package: emacs;

Reported by: Bastien Guerry <bzg <at> gnu.org>

Date: Sat, 17 May 2025 22:56:02 UTC

Severity: normal

Found in version 31.0.50

Done: Eli Zaretskii <eliz <at> gnu.org>

Full log


View this message in rfc822 format

From: Eli Zaretskii <eliz <at> gnu.org>
To: Robert Pluim <rpluim <at> gmail.com>
Cc: bzg <at> gnu.org, Sebastien.Hinderer <at> inria.fr, samuel.thibault <at> gnu.org, 78474 <at> debbugs.gnu.org
Subject: bug#78474: 31.0.50; Wrong char insertion in rxvt
Date: Tue, 22 Jul 2025 16:48:44 +0300
> From: Robert Pluim <rpluim <at> gmail.com>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  Sebastien.Hinderer <at> inria.fr,
>   bzg <at> gnu.org,  78474 <at> debbugs.gnu.org
> Date: Tue, 22 Jul 2025 14:45:12 +0200
> 
> >>>>> On Tue, 22 Jul 2025 14:33:38 +0200, Samuel Thibault <samuel.thibault <at> gnu.org> said:
> 
>     >> That was my misinterpretation of the request. Itʼs easy enough to
>     >> restrict the change to only affect the '\t\b' case, but weʼll have to
>     >> come up with a new name for the user option :-)
> 
>     Samuel> Since \t\b is actually slower than \e[C, I don't see why it should be an
>     Samuel> option.
> 
> Youʼre a braver man than I to make such a statement, and I for one
> will not propose a change like this that cannot be controlled with a
> variable of some sort.

Yes, I agree.  If only to have a "fire escape" if we ever bump into
some use case where this change might be a culprit, and will want an
easy way of testing that.




This bug report was last modified 1 day ago.

Previous Next


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