public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Thomas Ward" <tward@bright.net>
To: <speakup@braille.uwo.ca>
Subject: Re: speakup keymaps
Date: Sat, 20 Oct 2001 05:34:38 -0400	[thread overview]
Message-ID: <003801c1594a$78a33b60$0200a8c0@enterprise> (raw)
In-Reply-To: <01101917111202.10448@lightstar>

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.
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Tyler Spivey
 ` Jason
   ` Thomas Ward [this message]
     ` Kenny Hitt
       ` Jason
       ` 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='003801c1594a$78a33b60$0200a8c0@enterprise' \
    --to=tward@bright.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).