From: "Brian L. Sellden" <Brian@henge.com>
To: blinux-list@redhat.com
Cc: blinux-list@redhat.com
Subject: Re: another idea for speech.
Date: Wed, 11 Dec 1996 09:18:40 -0700 [thread overview]
Message-ID: <199612111618.JAA03999@zygote.ivory.com> (raw)
In-Reply-To: <Pine.LNX.3.95.961211111333.17207A-100000@softcon.com> (message from Travis Siegel on Wed, 11 Dec 1996 11:15:33 -0500 (EST))
Hi all,
Travis said:
> I don't give a fiddle about x-windows. I just want a screen reader I can
> use with linux from the console. I don't run x, neither will I do so.
> But from the main console, there is still no options for me. I *must* use
> a terminal to get access to my system. That's what I'd like to fix. Now,
> anyone have any ideas?
I am getting weary of posts like this. Linux access
comes in many different forms. A console screen reader is only
one of them. Travis, whether or not you 'give a fiddle'
about X Windows access is of concern to noone.
On this list, discussions will continue on several different topics.
Getting access to consoles, X Windows, ttys, are all legitimate
topics.
Let's keep as many threads of discussion going as possible.
Regards,
Brian.
--
---------------
Brian L. Sellden - brian@henge.com, brians@usa.net
User of Emacspeak 5.0, making Unix talk.
http://www.henge.com/~brian
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
HRTC
` Travis Siegel
` Brian L. Sellden [this message]
` Travis Siegel
` Joel Zimba
` William Loughborough
` Travis Siegel
` Jim Rebman
` Travis Siegel
` Brian L. Sellden
-- strict thread matches above, loose matches on Subject: below --
Travis Siegel
michael malver
Lar Kaufman
` Jim Rebman
` Jason John Griffin White
` Craig Martin
` Ken Perry
` Joel Zimba
` Ben Van Poppel
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=199612111618.JAA03999@zygote.ivory.com \
--to=brian@henge.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).