From: Igor Gueths <igueths@attbi.com>
To: speakup@braille.uwo.ca
Subject: Re: Speakout Users
Date: Wed, 30 Apr 2003 21:27:40 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0304302125070.29046-100000@igueths> (raw)
In-Reply-To: <Pine.LNX.4.53.0304301809410.381@princenet.sytes.net>
Well in terms of the pitch and stuff, I have a script that will reset
those values. I was just curious as to whether the punctuation delay
problem had been fixed, which it seems to have been. I apologize for
catching on late in this, however is Speakup now officially modular? Bc I
heard references to spkout.o, and I assume it is an lkm?
May you code in the power of the source,
may the kernel, libraries, and utilities be with you,
throughout all distributions until the end of the epoch.
On Wed, 30 Apr 2003, Lorenzo Prince wrote:
> The Dectalk bug seems to be fixed. I played around with it somewhat, and
> unloaded and reloaded the dectalk module, and also unplugged the dectalk
> from my system then plugged it in again. I didn't have any problem with
> the delay. The only thing that kinda bugs me a little is that the pitch
> is not initialized to the same value as the value in
> /proc/speakup/caps_stop, but I can fix that simply by changing the pitch
> value in the source code.
>
> Lorenzo
>
> I still maintain the point that designing a monolithic kernel in 1991 is a
> fundamental error. Be thankful you are not my student. You would not get a
> high grade for such a design :-)
> -- Andrew Tanenbaum to Linus Torvalds
>
> _______________________________________________
> 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
Steve Holmes
` Igor Gueths
` Lorenzo Prince
` Igor Gueths [this message]
` Steve Holmes
` Steve Holmes
` Charles Crawford
` Steve Holmes
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=Pine.LNX.4.44.0304302125070.29046-100000@igueths \
--to=igueths@attbi.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).