From: covici@ccs.covici.com (John Covici)
To: brian@henge.com
Cc: malv0002@gold.tc.umn.edu, blinux-list@goldfish.cube.net
Subject: Re: UltraSonix screen-reader for X-windows available at BLINUX site
Date: Thu, 10 Oct 1996 21:42:51 -0400 [thread overview]
Message-ID: <325dab57.ccs@ccs.covici.com> (raw)
Message-ID: <bYaXy0r1JI2D089yn@ccs.covici.com> (raw)
In-Reply-To: <199610092344.RAA01844@zygote.ivory.com>
on Wed, 9 Oct 1996 17:44:02 -0600 brian@henge.com in
<199610092344.RAA01844@zygote.ivory.com> wrote:
>Hello Michael,
>
>> pardon my ignorance. I am glad to see that we can use x-windows,
>> but will this program also support standard unix shells such as bash, or
>> tcsh?
>
>Absolutely! Running a shell in a X-terminal is peanuts
>compared to many more complicated applications. UltraSonix is not written
>with any particular application in mind. You want shells? We got shells!
But can you do the simple thing, i.e. set up a computer with Linux and
run something from the console which will speak everything?
Would have been nice to have something in the kernel for some of the
basic sdreen reader functionality.
--
John Covici
covici@ccs.covici.com
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
michael malver
` brian
[not found] ` <bYaXy0r1JI2D089yn@ccs.covici.com>
` John Covici [this message]
` Nicolas Pitre
` AARON HOWELL
` UltraSonix scope and screen-reader issues (was: Re: UltraSonix screen-reader for X-windows available at BLINUX site) Nikhil Nair
[not found] <199610110725.BAA01013@zygote.ivory.com>
[not found] ` <MRjXy0r1JQNW089yn@ccs.covici.com>
` UltraSonix screen-reader for X-windows available at BLINUX site John Covici
-- strict thread matches above, loose matches on Subject: below --
BLINUX Documentation Project
UltraSonix-FAQ zocki
` UltraSonix screen-reader for X-windows available at BLINUX site BLINUX Documentation and Development Project
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=325dab57.ccs@ccs.covici.com \
--to=covici@ccs.covici.com \
--cc=blinux-list@goldfish.cube.net \
--cc=brian@henge.com \
--cc=malv0002@gold.tc.umn.edu \
/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).