From: Jason <unleet@qwest.net>
To: speakup@braille.uwo.ca
Subject: Re: speakup keymaps
Date: Sat, 20 Oct 2001 07:22:40 -0700 [thread overview]
Message-ID: <01102007224000.01901@lightstar> (raw)
In-Reply-To: <20011020092154.C23022@learning>
Hmm.... how 'bout all of the above (not in the same keymap). Or a really
detailed keymap howto, that way the user has the final say.
On Saturday October 20, 2001 07:21 am, you wrote:
> Hi. How about using the Windows key? I've seem messages from other
> Linux lists about people using it for short cuts.
>
> Kenny
>
> On Sat, Oct 20, 2001 at 05:34:38AM -0400, Thomas Ward wrote:
> > How about using capslock key for commands? One thing I have noticed in
> > Jaws 4.0 is using the capslock for laptop keys, and I am wondering if
> > this is possible under speakup.
> > If it is possible then any number of keys can be asigned with out
> > conflicts with other programs keyboard commands.
> > It certainly makes an interesting look into.
> >
> > ----- Original Message -----
> > From: "Jason" <unleet@qwest.net>
> > To: <speakup@braille.uwo.ca>
> > Sent: Friday, October 19, 2001 8:11 PM
> > Subject: Re: speakup keymaps
> >
> > > Hey, one thought for bypass... does any software for Linux use the
> > > Scroll Lock key? Perhaps that could be used to toggle bypass?
> > >
> > > On Friday October 19, 2001 04:54 pm, you wrote:
> > > > here's my input:
> > > > we could make keymaps for most common screen readers, but speakup
> > > > needs
> >
> > a
> >
> > > > bypass key. unless we used alt keys, but alt is hard to type.
> > > >
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
Tyler Spivey
` Jason
` Thomas Ward
` Kenny Hitt
` Jason [this message]
` Raul A. Gallegos
` djc
` Raul A. Gallegos
` djc
` speakup key maps Georgina
` Tim Burgess
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=01102007224000.01901@lightstar \
--to=unleet@qwest.net \
--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).