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: Samuel Thibault <samuel.thibault <at> gnu.org>
Cc: bzg <at> gnu.org, Sebastien.Hinderer <at> inria.fr, rpluim <at> gmail.com, 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 10:44:21 +0300
> Date: Thu, 24 Jul 2025 09:14:46 +0200
> From: Samuel Thibault <samuel.thibault <at> gnu.org>
> Cc: manuel <at> ledu-giraud.fr, rpluim <at> gmail.com, bzg <at> gnu.org,
> 	Sebastien.Hinderer <at> inria.fr, 78474 <at> debbugs.gnu.org
> 
> (gnome-terminal is libvte-based, so it's the same as mate-terminal)

Btw, any reason why libvte works as it does?  The fact that there's no
document specifying what \t\b should produce is not a reason good
enough to behave in a deviant way.  Are there any downsides to what
xterm does with \t\b that justify the decision of libvte to work
differently?  If there are no downsides, why do they insist not to
change their implementation to match the others?




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.