From: Chuck Hallenbeck <chuckh@ftml.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: changing synths
Date: Sat, 30 May 2009 04:35:03 -0400 [thread overview]
Message-ID: <20090530083503.GA25793@rx.localhost> (raw)
In-Reply-To: <20090530004216.GA12847@localhost.localdomain>
Hi guys,
On Fri, May 29, 2009 at 05:42:17PM -0700, Gregory Nowak wrote:
> If the synth you want to switch to is built as a module, and that
> module hasn't yet been loaded, you'd just modprobe it. So, again for
> the dectlk, you'd modprobe speakup_dectlk I believe. Again, using the
> speakwith/talkwith script takes care of all of that for you automagically.
Not quite. The speakwith/talkwith scripts do not load modules. With
speakup, it is okay to have several of the driver modules loaded at the
same time, so that switching between synths is just a matter of echoing
the desired synth name to that variable, except that the connector
programs need to be killed or restarted as appropriate. Switching from
a soft synth to a hardware synth requires not only that the synthname
be changed, but the connector program be killed. And vice versa, it
needs to be restarted when switching back. Those are the chores the
scripts handle, plus reinitializing the speakup parameters just as
speakupconf would do.
Version 3 of the scripts merely avoids the bashism of relying on $UID
to detect who's running the scripts.
Chuck
--
The Moon is Waxing Crescent (41% of Full)
My web site: www.hallenbeck.ftml.net
Microblog: http://identi.ca
--------
The reason that every major university maintains a department of
mathematics is that it's cheaper than institutionalizing all those people.
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Christopher Moore
` Gregory Nowak
` Chuck Hallenbeck [this message]
` Christopher Moore
` Chuck Hallenbeck
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=20090530083503.GA25793@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).