From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: cut and paste still doesn't work?
Date: Wed, 24 Apr 2002 15:43:28 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0204241531360.10708-100000@igueths> (raw)
In-Reply-To: <Pine.LNX.4.44.0204232142430.328-100000@homerun.us>
Hi Adam. I wouldn't think that this was the case since I completely
scrapped any trace of my old configuration. But the old keymap could still
be loading right now and I don't know about it? The reason why I don't
think this is likely is because I patched speakup-1.00 into the kernel,
with no reference to the old speakup 0.10 that I had back when I ran the
2.2.18pre21-idepci for a day or two. The only reference I found to keymaps
was in /etc/init.d/keymaps-lct.sh. This script seems to be just concerned
with loading kernel keymaps, not speakupmap.map.
On Tue, 23 Apr 2002, Adam Myrow wrote:
> Are you using at least Speakup 1.0? That's the latest stable version. If
> so, are you, perhaps, loading a keymap from an older version over the one
> that has cut and paste in it? This will happen if you previously used
> something like 0.10 and upgraded. In that case, find the script that
> loads your keymap and determine where the keymap is. Replace the keymap
> with the one in /usr/src/linux/drivers/char/speakup/speakupmap.map. Hope
> this helps. By the way, this is a problem on Debian stable as well as it
> was modified with an older Speakup. Good luck.
>
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Igor Gueths
` Buddy Brannan
` Igor Gueths
` Adam Myrow
` Igor Gueths [this message]
` jwantz
` Igor Gueths
` Adam Myrow
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.0204241531360.10708-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).