all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Eric Danan <eric.danan@u-cergy.fr>
Cc: 35435@debbugs.gnu.org
Subject: bug#35435: 26.1; Gnome magnifier not following cursor when typing in emacs
Date: Fri, 26 Apr 2019 14:14:47 +0300	[thread overview]
Message-ID: <83zhodvx08.fsf@gnu.org> (raw)
In-Reply-To: <77a6ac4f-aa3c-74ee-764b-e9df21692d36@u-cergy.fr> (message from Eric Danan on Fri, 26 Apr 2019 13:05:41 +0200)

> From: Eric Danan <eric.danan@u-cergy.fr>
> Date: Fri, 26 Apr 2019 13:05:41 +0200
> 
> Due to a visual impairment I constantly work with a screen magnifier 
> turned on (in full screen mode), and I need it to track the cursor/caret 
> to follow what I am typing.
> 
> So far I am using emacs 26.1 on cygwin on windows 10, and the windows 10 
> magnifier does the job of tracking the cursor.
> 
> I am considering switching to gnome on linux and therefore installed the 
> fedora (version 29) distribution to try it out. The gnome (3.30) shell 
> magnifier supports cursor tracking and it works in other applications 
> but not emacs (26.1).
> 
> I previously sent this message to the gnome accessibility list (that was 
> a long time ago in 2015, so with earlier versions of emacs and gnome) 
> and got a reply from Alex Arnaud stating:
> 
>  > I've tried to test Emacs with Accercicer (a accessibility debug tool) 
> and my conclusion are Emacs doesn't connect it to AT-SPI (accessibility 
> stack).

The Windows port of Emacs has special code to move the system caret in
sync with the cursor.  I guess the X build should have something
similar, patches are welcome to implement that.





  reply	other threads:[~2019-04-26 11:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-26 11:05 bug#35435: 26.1; Gnome magnifier not following cursor when typing in emacs Eric Danan
2019-04-26 11:14 ` Eli Zaretskii [this message]
2019-05-02  8:17   ` Eric Danan
2020-02-03 10:49     ` Eric Danan
2020-02-04  0:51       ` Stefan Kangas

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83zhodvx08.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=35435@debbugs.gnu.org \
    --cc=eric.danan@u-cergy.fr \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.