From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: Making Custom keymaps.
Date: Wed, 8 May 2002 20:13:23 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0205082012360.1516-100000@igueths> (raw)
In-Reply-To: <006d01c1f6e4$40c7d920$0100a8c0@stargate>
Hi all. If anyone finds documentation related to Thomas's question, can
you CC it to me? I'm also interested in doing this at some point. Thanks!
Gates go to hell, your OS is waiting for you there!
On Wed, 8 May 2002, Thomas Ward wrote:
> Hello, list. Can anyone please help me with making a custom keymap for
> Speakup? I've never been fond of the current one, and I've always wanted to
> make my own.
> However, I am not real familiar with the logic behind the hex codes. If
> someone can send me a detailed list of the values of what exactly what is
> what, or direct to me on really good documentation on this subject I'dbe in
> his or her debt. Thanks.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
prev parent reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E175ZI3-0002rd-00@speech.braille.uwo.ca>
` Thomas Ward
` 'Georgina'
` Igor Gueths [this message]
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=Pine.LNX.4.44.0205082012360.1516-100000@igueths \
--to=igueths@attbi.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).