From: William Hubbs <w.d.hubbs@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: control vs keypad enter (was Re: Initial success with Espeakup)
Date: Sat, 2 Aug 2008 12:26:36 -0500 [thread overview]
Message-ID: <20080802172636.GA26756@linux1> (raw)
Actually, in speakup, these keys do slightly different things.
Control flushes the buffer then starts speaking again immediately, and
keypad enter shuts up until another key is pressed.
To see this, cat a very long file then hit control a couple of times
while it is scrolling. Then, hit keypad enter.
William
On Sat, Aug 02, 2008 at 10:00:37AM -0700, Hart Larry wrote:
> In reality Greg, I would guess some of us are used to useing controll as
> earlier screen-readers Vocal-Eyes--and-Jaws use that. About the only way I
> will use the other kee, would be if some1 else is working on the
> machine--and-I come up from the right to stop it
> Hart
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
William Hubbs [this message]
` Hart Larry
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=20080802172636.GA26756@linux1 \
--to=w.d.hubbs@gmail.com \
--cc=speakup@braille.uwo.ca \
/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.
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).