From: Buddy Brannan <davros@ycardz.com>
To: speakup@braille.uwo.ca
Subject: Re: keymap trouble
Date: Thu, 23 May 2002 17:27:52 -0400 [thread overview]
Message-ID: <20020523212752.GA26016@kb5elv> (raw)
In-Reply-To: <20020523205933.GA14340@asmodean.net>
Hey Raul,
The only thing you're missing as that with the CVS version(s) of
Speakup, the whole keymap has been changed to facilitate the use of
numlock to generate numbers on the number pad. That means that the
docs are...well...outdated. So ignore the keymap tutorial, at least
insofar as the key codes go. Looks like I may have to go in and update
the key codes. (Ooh, work. ...LOL) I should really do this, actually,
it'd keep my mind occupied. ...
--
Buddy Brannan, KB5ELV/3 | I choose you to take up all of my time.
Email: davros@ycardz.com | I choose you because you're funny and kind
| I want easy people from now on.
| --the Nields
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Raul A. Gallegos
` Buddy Brannan [this message]
` Janina Sajka
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=20020523212752.GA26016@kb5elv \
--to=davros@ycardz.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).