From: "Nick Stockton" <nstockton@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: speakup drivers with 2.6.24
Date: Sat, 29 Mar 2008 22:46:21 -0400 [thread overview]
Message-ID: <2D45D740CE014D49AFF5F8E0D780E5B6@golly> (raw)
In-Reply-To: <alpine.DEB.1.00.0803291759580.19385@speech.braille.uwo.ca>
with out /proc/speakup will there be another way to make shell scripts to
change the pitch, rate, key_echo, delay_time etc or will that ability be
gone?
Nick Stockton
----- Original Message -----
From: "Kirk Reiser" <kirk@braille.uwo.ca>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Sent: Saturday, March 29, 2008 6:07 PM
Subject: Re: speakup drivers with 2.6.24
> Auh yes, you have put your finger on one of the problems with the
> current git repository. Once a built-in synth is loaded there is no
> current way to switch to another built-in synth. Upon loading a
> module there's no way to switch to another built-in synth. If
> changing synths is necessary I would recommend builting them as
> modules which can be loaded and unloaded at will.
>
> We are working on bringing back the ability to change synths but it is
> not complete yet. I will turn my attention to that as soon as I have
> the cut and paste issue fixed and ready for testing. It's current
> status is that I can lock a machine with a single mark keystroke
> everytime ten out of ten tries! 'grin' Anyone want to test it?
>
>
>
> Kirk Reiser The Computer Braille Facility
> e-mail: kirk@braille.uwo.ca University of Western Ontario
> phone: (519) 661-3061
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
Chuck Hallenbeck
` Kirk Reiser
` Chuck Hallenbeck
` Nick Stockton [this message]
` William Hubbs
` Zachary Kline
` Daniel Dalton
` Samuel Thibault
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=2D45D740CE014D49AFF5F8E0D780E5B6@golly \
--to=nstockton@gmail.com \
--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).