all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Antonio Gervasoni <agervasoni@gmail.com>
To: 19792@debbugs.gnu.org
Subject: bug#19792: Emacs and Voiceover
Date: Fri, 6 Feb 2015 11:39:52 -0500	[thread overview]
Message-ID: <CA+O6dK2HZe+ztX4tFSKcJO6vLpPLbwEqFcDW1ytVkTC9U1=4zw@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]

Hi,

What I'd like to report is not exactly a bug (or maybe it is) and I'm not
really sure if you could fix it or if I should be writing to someone else.

I have a blind student who would benefit a lot from using Emacs but,
unfortunately, it doesn't work for him because he's on a Mac and Voiceover
can't read information correctly from the Emacs window (I have installed
the "Emacs for Mac OS X" that can be downloaded from here
<http://emacsformacosx.com/>). A blind friend who runs Emacs on Linux has
told me that Orca has the same problem and that emacspeak is the only
solution that worked for him.

The method of installation of emacspeak on a Mac is pretty obscure. I have
been able to find a few old pages with dozens of steps and none of them
guarantee that it will work. And, besides, I don't have the necessary
skills to try that approach either.

I wonder if the problem with Voiceover could be solved from the Emacs side
(because, expecting Apple to to anything is of course ridiculous), which
may also solve the problem with Orca.

If there's anything on your power to solve this, I'm sure a lot of people
would be very grateful, including me and my student. If not, could you
please point me out to whom I could write for help?

Sincerely,

Antonio Gervasoni

[-- Attachment #2: Type: text/html, Size: 1518 bytes --]

             reply	other threads:[~2015-02-06 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 16:39 Antonio Gervasoni [this message]
2015-02-10  9:03 ` bug#19792: Emacs and Voiceover YAMAMOTO Mitsuharu

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='CA+O6dK2HZe+ztX4tFSKcJO6vLpPLbwEqFcDW1ytVkTC9U1=4zw@mail.gmail.com' \
    --to=agervasoni@gmail.com \
    --cc=19792@debbugs.gnu.org \
    /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.