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


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

From: Eli Zaretskii <eliz <at> gnu.org>
To: Seb Hinderer <Sebastien.Hinderer <at> inria.fr>
Cc: bzg <at> gnu.org, 78474 <at> debbugs.gnu.org, rpluim <at> gmail.com,
 samuel.thibault <at> gnu.org
Subject: Re: bug#78474: 31.0.50; Wrong char insertion in rxvt
Date: Tue, 22 Jul 2025 17:25:26 +0300
> Date: Tue, 22 Jul 2025 16:06:15 +0200
> From: Seb Hinderer <Sebastien.Hinderer <at> inria.fr>
> Cc: Samuel Thibault <samuel.thibault <at> gnu.org>, rpluim <at> gmail.com,
> 	bzg <at> gnu.org, 78474 <at> debbugs.gnu.org
> 
> Eli Zaretskii (2025/07/22 16:27 +0300):
> > > Yes, screen readers have always had to be privileged somehow.
> >
> > Which maybe gives us a way to detect them?
> 
> Frankly Eli, I cannot urge you enough to just forget about this idea, as
> swiftly as possible, for your own good (and ours).
> 
> There is the ssh case I mentionned and also, if you go through the WCAG
> and all the principles of the Internet, sane communication is based on
> agreements on what is exchanged which do not try to depend on which
> software is on the other side.

If better methods are possible, they are of course preferred.  But if
they are impossible, I don't want to reject other methods, even if
they are less elegant.

> Did you once see one RFC specifying what theprotocol should be depending
> on which client or server one is talking to?

Yes, of course.  Emacs has several features where we change behavior
depending on which external program we are communicating with or using
as a sub-process.




This bug report was last modified 2 days ago.

Previous Next


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