From: Kenny Hitt <kenny@hittsjunk.net>
To: Sean McMahon <smcmahon@usgs.gov>,
"Speakup is a screen review system for Linux."
<speakup@braille.uwo.ca>
Subject: Re: appropriate policy on keymaps with speakup 2.0 official release
Date: Tue, 10 May 2005 22:03:36 -0500 [thread overview]
Message-ID: <20050511030336.GB22208@blackbox> (raw)
In-Reply-To: <003801c555bc$af4933f0$77ac7682@azwaterDOM.wr.usgs.gov>
Hi.
The console-data package is the one you want. As root type:
dpkg-reconfigure console-data
Hope this helps.
Kenny
On Tue, May 10, 2005 at 05:02:07PM -0700, Sean McMahon wrote:
> While installing debian one of the questions was reguarding policy on new
> keymaps. My hunch was to not touch the keymap if a new one was available, but
> the notes on speakup 2.0 say that speakup loads its own keymap anyway. How I
> have answered the keymap question and what program under debian controlls
> keymaps?
> Sean
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
prev parent reply other threads:[~ UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Sean McMahon
` Kenny Hitt [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=20050511030336.GB22208@blackbox \
--to=kenny@hittsjunk.net \
--cc=smcmahon@usgs.gov \
--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).