From: Ken Perry <whistler@blinksoft.com>
To: blinux-list@redhat.com
Subject: Re: another idea for speech
Date: Tue, 10 Dec 1996 21:19:44 -0700 (MST) [thread overview]
Message-ID: <Pine.LNX.3.95.961210211912.17193A-100000@blinksoft.com> (raw)
In-Reply-To: <Pine.BSI.3.95.961210221450.3799B-100000@usr07.primenet.com>
The writer of Emacs says writing a driver for other boards is simple let
me know if you get one for Double talk written.
Ken /whistler
On Tue, 10 Dec 1996, Craig Martin wrote:
> well,
> this is a very interesting train of thought. It would be nice if we could
> find a way to use a doubletalk board in a linux invironment, But what you
> might be able to do is tell emacs speaks the way to control a double talk
> external or a lite talk and then use the standard console keys as the
> input. This might take some of the pressure off of those who have less
> resources. I have two double talk internal boards here at home, and I
> wonder if they could run with emacs speaks? I'm annew user of Linux, so
> this is a new idea to me.
> What do you all think?
>
>
> craig martin
> numbers@primenet.com
> packet:
> wa0wpj@wa0wpj.ampr.org
>
> ---
> Send your message for blinux-list to blinux-list@redhat.com
> Blinux software archive at ftp://leb.net/pub/blinux
> Blinux web page at http://leb.net/blinux
> To unsubscribe send mail to blinux-list-request@redhat.com
> with subject line: unsubscribe
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
Lar Kaufman
` Jim Rebman
` Jason John Griffin White
` Craig Martin
` Ken Perry [this message]
` Joel Zimba
` Ben Van Poppel
-- strict thread matches above, loose matches on Subject: below --
HRTC
` Travis Siegel
` Brian L. Sellden
` Travis Siegel
` Joel Zimba
` William Loughborough
` Travis Siegel
` Jim Rebman
` Travis Siegel
` Brian L. Sellden
Travis Siegel
michael malver
Craig Martin
` Kenneth Albanowski
` Jim Rebman
` Sam Hartman
` Kenneth Albanowski
` Steve Holmes
` Kenneth Albanowski
` Mark Newbold
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.3.95.961210211912.17193A-100000@blinksoft.com \
--to=whistler@blinksoft.com \
--cc=blinux-list@redhat.com \
/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).