From: "Tyler Littlefield" <tyler@tysdomain.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: more key echo
Date: Wed, 28 Jan 2009 15:37:05 -0800 [thread overview]
Message-ID: <597D2D09F99549A3AC177B94452FD55D@tdsdev> (raw)
In-Reply-To: <20090128222459.GA2512@debian.Belkin>
it's everyone. I had about 12+ messages this morning, when I checked email,
which is high traffic for this list.
I submitted a bug on Sunday, and seen my USB question and thanks to kerry,
but nothing about the bug, so some mail might not have made it through
----- Original Message -----
From: "Keith Barrett" <lists@barrettpianos.co.uk>
To: <speakup@braille.uwo.ca>
Sent: Wednesday, January 28, 2009 2:24 PM
Subject: more key echo
> Thanks to Willum and Samuel,
>
> Still having some problems. I looked at /etc/modprobe.d but was unsure
> where to make the change. I tryed the local file as there was reference
> to speakup there but I somehow mannaged to kill speakup completely and
> had to get my daughter to read the screen while I put things back.
>
> If anyone has turned off key echo on debian lenny and could tell me how
> it is done that would be good. Still new at this so could do with some
> basic instructions.
>
> Also, has there been a problem with the list as I sent the first message
> a couple of days ago and only saw it appear today. My isp has been
> making some changes so would be good to know if the list has been slow
> before I decide it is them.
>
> 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: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
Keith Barrett
` Tyler Littlefield [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=597D2D09F99549A3AC177B94452FD55D@tdsdev \
--to=tyler@tysdomain.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).