From: "Pete" <persuric@ameritech.net>
To: <speakup@braille.uwo.ca>
Subject: Re: possible bug
Date: Sat, 4 May 2002 11:30:42 -0400 [thread overview]
Message-ID: <012001c1f384$7242d620$8017fea9@PreferedCustomer> (raw)
In-Reply-To: <Pine.LNX.4.44.0204221121380.1512-100000@maranatha.chartermi.net>
I like that, little messages like that are helpfull when learning how to use
speakup.
Pete
> I don't know about that; when I use speakup with doubletalk, if I do
> insert/enter it says "you turned me off" and when I hit it again it says
"Hey,
> that's better."
prev parent reply other threads:[~ UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
Deedra Waters
` Igor Gueths
` Deedra Waters
` Cheryl Homiak
` Shaun Oliver
` Cheryl Homiak
` Doug Lawlor
` Dave Hunt <
` Cheryl Homiak
` Dave Hunt <
` Toby Fisher
` Pete [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='012001c1f384$7242d620$8017fea9@PreferedCustomer' \
--to=persuric@ameritech.net \
--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).