From: Gregory Nowak <greg@romuald.net.eu.org>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: continuous reading feature
Date: Mon, 19 Jun 2006 10:50:24 -0700 [thread overview]
Message-ID: <20060619175024.GA25871@localhost.localdomain> (raw)
In-Reply-To: <20060619142728.GC6695@lnx3.holmesgrown.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
As Chuck has pointed out, the keymap tutorial is out of date, and
keymap.map has in fact been replaced by speakupmap.map. Also, the
speakup+r key is in fact listed at the very bottom.
The last time when I asked about this, and said I got no instructions,
I did in fact try compiling genmap.c, but ran into problems doing so,
which I don't remember anymore, but I'm sure I described them in that
long ago post, which is probably still in the archives somewhere. Anyway,
I've tried it again, and have gotten speakup+r working this time
around. So, here's what I did; it's very simple really.
1. cd to /usr/src/linux/drivers/char/speakup
2. If you have a recent version of speakup, speakupmap.map should
already have speakup+r defined as the last line, so you shouldn't need
to do anything.
3. Compile genmap.c by running:
gcc -o genmap genmap.c
4. Generate the keymap, placing the output in a file called keymap in
the current directory by running:
./genmap speakupmap.map >keymap
5. Finally, copy your new keymap to /proc/speakup/keymap by typing:
cat keymap >/proc/speakup/keymap
That's it, you should have speakup+r working now.
There are a couple of questions that I have, that maybe someone can
answer.
1. How do you stop speakup+r from reading? I thought it was done with
the escape key, but both that, and speakup+r itself don't stop it. I
had to finally use ctrl+c once I got to the end of the document in
emacs, and I'm pretty sure that this isn't how it should be done,
since that would have the probably unwanted side-effect of terminating
the currently foreground application.
2. How do I preserve my keymap changes across reboots? Do I need a
line in my boot scripts to copy it to /proc/speakup/keymap every time,
or is there a more permanent way of doing this, such as including it
in the kernel?
Greg
On Mon, Jun 19, 2006 at 07:27:30AM -0700, Steve Holmes wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
> The most recent versions of keymap.map in the speakup directory has
> speakup-R listed at the bottom of the list.
>
> I don't think this gets generated automatically though I saw some stuff
> in the Makefile for it. In fact, I recently had to manually compile the
> genmap.c program in order to regen my keymap. I have a keymap that I
> modified the laptop keys to be more clearly mapped and I included the
> read-all key in there as well. The keymap tutorial explains all how to
> build the keymap and I then explicitly copied the generated map into my
> /proc/keymap and backup directories so I don't lose them.
>
- --
web site: http://www.romuald.net.eu.org
gpg public key: http://www.romuald.net.eu.org/pubkey.asc
skype: gregn1
(authorization required, add me to your contacts list first)
- --
Free domains: http://www.eu.org/ or mail dns-manager@EU.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
iD8DBQFEluPg7s9z/XlyUyARAhfYAJ91W0UehlLFenmp6NXHvk8JS1WijQCdEqYg
0JWQHTPivkhl/DBbJAdnOrw=
=k0zE
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
MICHAEL MCDONALD
` Charles Hallenbeck
` Steve Holmes
` Charles Hallenbeck
` Gregory Nowak [this message]
` Steve Holmes
` Ameer Armaly
` Steve Holmes
` Charles Hallenbeck
-- strict thread matches above, loose matches on Subject: below --
MICHAEL MCDONALD
Charles Hallenbeck
` Luke Yelavich
` Charles Hallenbeck
` Gregory Nowak
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=20060619175024.GA25871@localhost.localdomain \
--to=greg@romuald.net.eu.org \
--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).