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: Andreas Schwab <schwab <at> suse.de>
Cc: bzg <at> gnu.org, Sebastien.Hinderer <at> inria.fr, rpluim <at> gmail.com, samuel.thibault <at> gnu.org, 78474 <at> debbugs.gnu.org
Subject: bug#78474: 31.0.50; Wrong char insertion in rxvt
Date: Wed, 23 Jul 2025 14:48:32 +0300

> From: Andreas Schwab <schwab <at> suse.de>
> Cc: Eli Zaretskii <eliz <at> gnu.org>,  bzg <at> gnu.org,  Seb Hinderer
>  <Sebastien.Hinderer <at> inria.fr>,  rpluim <at> gmail.com,  78474 <at> debbugs.gnu.org
> Date: Wed, 23 Jul 2025 10:06:19 +0200
> 
> On Jul 22 2025, Samuel Thibault wrote:
> 
> > Andreas Schwab, le mar. 22 juil. 2025 15:48:20 +0200, a ecrit:
> >> On Jul 21 2025, Samuel Thibault wrote:
> >> 
> >> > It is. Cat /dev/vcs, and you have it.
> >> 
> >> /dev/vcs contains the rendered contents, so how they were drawn should
> >> not make any difference.
> >
> > The question of this thread piece was not about that, but about screen
> > readers being able to read the screen without getting announced to
> > applications in any way.
> 
> Since screen readers using /dev/vcs are not affected by this issue they
> are irrelevant here.

So what do screen readers which _are_ affected by this issue use?

Previous Next

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