From: "Guy Abandon." <text.tools@virgin.net>
To: <speakup@braille.uwo.ca>
Subject: Re: error starting emacspeak under red hat 9
Date: Thu, 25 Sep 2003 21:57:19 +0100 [thread overview]
Message-ID: <009001c383a7$9c686410$8200a8c0@bobsh> (raw)
In-Reply-To: <16242.12640.378302.1574@ccs.covici.com>
<<suggest is that you buy the
$50 dectalk runtime for linux -- that will work with emacspeak and
you can have both at once.>>
I approve of this and have considered it often enough and will more
when wallet permits. I've read criticisms though even then that it
lacks the level of control you have with real hw synths like the
Apollo I have. Not being able to interrupt and shut-up output would
annoy me.
Would this level of use of the sound card get in the way of using the
sound for sound's sake.... like the jukebox facility I've been doing
these past few weeks. It's taking this long to load it with all the
CD's I have here.
I have another spare box though, so might keep jukebox as just that
and start again with a Slackware work machine.
GA!
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.
` John covici
` Guy Abandon. [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='009001c383a7$9c686410$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).