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:24:47 +0300

> Date: Tue, 22 Jul 2025 14:09:40 +0200
> From: Samuel Thibault <samuel.thibault <at> gnu.org>
> Cc: Robert Pluim <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 15:03:52 +0300, a ecrit:
> > Of course, specially-tailored cases could be concocted which show the
> > contrary, but that's not what this code is about.  The request in this
> > bug report, AFAIU, was to disable the use of TABs _in_all_cases_,
> 
> No.
> 
> “
> Quoting Samuel: "Emacs, instead of sending a rightward cursor movement
> (\e[C), sends \009\008 (a tabulation and a leftward cursor movement)"
> 
> This char insertion problem confuses assistive technologies for the
> visually impaired.
> ”

We are mis-communicating.  When I said "in all cases", I meant even
when TABs do not cause any problems and/or when screen-reading
software is not used at all.

> I don't remember really asking for more than that.

A reminder from https://debbugs.gnu.org/cgi/bugreport.cgi?bug=78474#77

> This leads me to the suggestion that the configuration where tab is not
> used is the one enabled by default, leaving the configuraitn burden to
> those to whom performance matters enough for them to care.

And no, it wasn't you who asked for that; but then I didn't say it was
you.

Previous Next

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