public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Frank Carmickle <frankiec@braille.uwo.ca>
To: speakup <speakup@braille.uwo.ca>
Subject: Re: Keymap problem maybe?
Date: Fri, 29 Jun 2001 09:00:27 -0400 (EDT)	[thread overview]
Message-ID: <Pine.LNX.4.21.0106290834270.3316-100000@localhost> (raw)
In-Reply-To: <Pine.LNX.4.30.0106281255120.404-100000@maranatha>

On Thu, 28 Jun 2001, Cheryl Homiak wrote:

> When I originally compiled my 2.4.5 kernel with speakup patched in using
> cvs, I chose my synthesizer in make config and also chose "y" for the
> speakup keymap as default.  My keyboard worked fine, nothing unusual.
> However, when my console-tools package was upgraded, I got the message
> "looking for keymap to install: none".  I wondered about that but didn't
> do anything about it since the keyboard was working.  However, I have now
> also done a 2.4.5 kernel without speakup, for using emacspeak by itself,
> for experimenting with festival, etc.  When I booted with this new kernel,
> I immediately discovered that my "alt" key isn't working correctly.  This
> is evidenced by the fact that I have to use escape instead of alt in
> emacspeak to enter a command.  Also I don't appear to be able to change
> consoles with alt-function keys.  Do I have to somehow install another
> keymap?  And do I have to do something more about the speakup keymap,
> since console-tools isn't finding any keymap?  I also had speakup and
> non-speakup versions of 2.2.19 kernel and never had this problem before.
 
Ok!  Well you had us all boggled until I carefully read your message
again!  If you make clean and recompile you should get a happy alt
key.  What happened was that speakup's keymap was undefined but no code
changed so the make process thought that the default keymap was up to
date.  So make clean and then rock&roll with the compile.

-- 
     Frank Carmickle
phone:     412 761-9568
email:     frankiec@dryrose.com



  reply	other threads:[~ UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Cheryl Homiak
 ` Frank Carmickle [this message]
   ` Cheryl Homiak
     ` Frank Carmickle

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.21.0106290834270.3316-100000@localhost \
    --to=frankiec@braille.uwo.ca \
    --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).