From: "Guy Abandon." <text.tools@virgin.net>
To: <speakup@braille.uwo.ca>
Subject: Re: error starting emacspeak under red hat 9
Date: Wed, 24 Sep 2003 21:54:44 +0100 [thread overview]
Message-ID: <009001c382de$151cb7a0$8200a8c0@bobsh> (raw)
In-Reply-To: <OKEHLMEIJPCEJEBPBEGFEEFACDAA.jared-stofflett@twmi.rr.com>
<<process speaker not running>>
I get this one without being in an X-Windows environment and put it
down to lack of configuration either with a suitable speech engine
part or similar.
<<sounds like the emacspeak list is an unforgiving place for
newbies.>>
I found that too, which is why I still don't use Emacspeak yet.
I downloaded but didn't get to try the Oralux distro yet either which
is meant to boot and work right out of the box so to speak. Has
anyone made that work like that?
Is there any mileage in trying to get Emacspeak to run with an
existing Apollo that is already being driven by Speakup?
Is it worth using plain old Emacs and skip the speak bit?
We're meant to be Speakup users here, so who uses Emacspeak or Emacs
and how successfully?
GA!
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
messages printed after login? Igor Gueths
` error starting emacspeak under red hat 9 Jared
` Guy Abandon. [this message]
` John covici
` Guy Abandon.
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='009001c382de$151cb7a0$8200a8c0@bobsh' \
--to=text.tools@virgin.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).