unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Jarek Czekalski <jarekczek@poczta.onet.pl>
To: emacs-devel@gnu.org
Cc: "tv.raman.tv@gmail.com >> \"T. V. Raman\"" <tv.raman.tv@gmail.com>
Subject: Re: Info: Console Vs GUI difference?
Date: Sat, 02 Nov 2013 09:06:44 +0100	[thread overview]
Message-ID: <5274B294.8080209@poczta.onet.pl> (raw)
In-Reply-To: <CADkJX2gXfrRmH9X1G+emm=jt_BmtEQ=5k_Wy89Q5ka3imSJBaA@mail.gmail.com>

W dniu 11/02/2013 02:39 AM, T.V. Raman pisze:
> Disabling the tool-bar in emacspeak likely affects low-vision
> users, so this would be good to fix.

Raman,

Emacspeak package was the reason I switched to Emacs. I use both visual 
Emacs functions and Emacspeak auditory feedback. Every loss in Emacs 
functionality is a big disadvantage for me. Please explain in what way 
you expect to fix this, so that we have Emacspeak without loosing any 
functionality of Emacs.

And please also explain what problems an Emacspeak user experiences 
without switching off the toolbar.

My vision is that Emacspeak be the best option for disabled programmers 
among all text editors. This Emacspeak should not be worse than Emacs.

Jarek




  reply	other threads:[~2013-11-02  8:06 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-30  9:27 Info: Console Vs GUI difference? T.V. Raman
2013-10-30 12:35 ` Stefan Monnier
2013-10-30 21:46   ` T.V. Raman
2013-10-30 23:11     ` Stefan Monnier
2013-10-31 16:21       ` T.V. Raman
2013-10-31 18:02         ` Stefan Monnier
2013-10-31 22:14           ` T.V. Raman
2013-11-01  1:32             ` Stefan Monnier
2013-11-01  2:10               ` T.V. Raman
2013-11-01 12:23                 ` Stefan Monnier
2013-11-01 16:55                   ` T.V. Raman
2013-11-01 18:34                     ` Eli Zaretskii
2013-11-01 20:24                       ` T.V. Raman
2013-11-01 20:36                         ` Eli Zaretskii
2013-11-02  0:17                           ` T.V. Raman
2013-11-02  2:04                             ` Stefan Monnier
2013-11-03 15:51                               ` T.V. Raman
2013-11-03 19:02                                 ` Jarek Czekalski
2013-11-03 19:05                                   ` T.V. Raman
2013-11-03 21:19                                     ` Stefan Monnier
2013-11-04  3:10                                     ` Dmitri Paduchikh
2013-11-04 16:38                                       ` T.V. Raman
2013-11-02  7:04                             ` Eli Zaretskii
2013-11-02  1:39                           ` T.V. Raman
2013-11-02  8:06                             ` Jarek Czekalski [this message]
2013-11-02 15:35           ` T.V. Raman
2013-11-02 15:56             ` Jarek Czekalski
2013-11-02 16:35             ` Dmitri Paduchikh
2013-11-02 20:46               ` T.V. Raman
2013-10-30 13:46 ` Jarek Czekalski
2013-10-30 21:45   ` T.V. Raman
2013-10-31 20:23   ` Richard Stallman
2013-11-01  7:37     ` Eli Zaretskii
2013-11-01 17:21       ` T.V. Raman

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

  List information: https://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=5274B294.8080209@poczta.onet.pl \
    --to=jarekczek@poczta.onet.pl \
    --cc=emacs-devel@gnu.org \
    --cc=tv.raman.tv@gmail.com \
    /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 public inbox

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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).