public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: wlestes@wlestes.uncg.edu
To: blinux-list@redhat.com
Subject: Re: the glass tty model of human-computer interaction
Date: Mon, 14 Dec 1998 10:09:31 -0500	[thread overview]
Message-ID: <199812141509.KAA01668@wlestes.uncg.edu> (raw)
In-Reply-To: <199812140555.VAA29035@ohio.river.org> (message from Richard Uhtenwoldt on Sun, 13 Dec 1998 21:55:00 -0800 (PST))

> I'm not blind, just interested in making my software blind friendly.

In general, I have noticed that "good Unix programs" are best for me
as a blind user.

> it occurs to me, tho, that if I were a blind user using text-to-speech
> hardware or a braille output device, I would prefer a line editor.  but the
> Linux Access Howto mentions Emacspeak but does not mention any line
> editors.
> 
> so, if you are blind and have used a line editor, please tell me whether
> you prefer line editors or visual editors.

My own preference is for visual editors. I think this is because
visual editors reflect more naturally the structure (lines, pages,
paragraphs, etc.) of files and line editors typically do not. So this
is not inherent in line editors, just a historical development.

--will


  parent reply	other threads:[~ UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Richard Uhtenwoldt
 ` Ann K. Parsons
   ` wlestes
     ` Matthew Campbell
   ` Jude Dashiell
 ` Charles Hallenbeck
 ` Dave Mielke
   ` Lisa Carmelle
   ` Why I learned emacs was " wlestes
     ` Dave Mielke
       ` wlestes
         ` Moe Aitel
           ` Luke Davis
             ` Moe Aitel
               ` Luke Davis
         ` Lar Kaufman
       ` Why I learned emacs Richard Uhtenwoldt
         ` Dave Mielke
         ` Jude Dashiell
 ` wlestes [this message]
 ` the glass tty model of human-computer interaction Jude Dashiell
 ` Jude Dashiell
 ` James H. Cloos Jr.
 ` Mike Keithley
   ` 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=199812141509.KAA01668@wlestes.uncg.edu \
    --to=wlestes@wlestes.uncg.edu \
    --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).