From: Chuck Hallenbeck <chuckh@ftml.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Retraction: My espeak 1.44.05 is also broken.
Date: Sun, 19 Sep 2010 17:39:03 -0400 [thread overview]
Message-ID: <20100919213903.GA9609@rx.localhost> (raw)
Hi,
On Friday I commented that my new copy of espeak 1.44.05 was working
normally, as indeed it was at the time. But I had not restarted my
computer since updating to that version a couple of days earlier. On
Saturday, a new kernel was available from the arch mirrors, and after
obtaining it, I then rebooted.
Guess what? My espeak is now broken too, misbehaving worse in some
applications than in others, but definitely difficult to use. I'm
switching to my doubletalk lt for the time being.
Chuck
--
The Moon is Waxing Gibbous (89% of Full)
My personal website: hallenbeck.ftml.net
Software: edway.ftml.net, and Blog: edway.wordpress.com
My Jabber ID: chuckh1@jabber.org (beware the silent h!)
--------
Some people claim that the Linux learning curve is steep, but at least you
only have to climb it once.
next reply other threads:[~ UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck [this message]
` Steve Holmes
` Kyle
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=20100919213903.GA9609@rx.localhost \
--to=chuckh@ftml.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).