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:14:28 -0500	[thread overview]
Message-ID: <199812141514.KAA01672@wlestes.uncg.edu> (raw)
In-Reply-To: <3.0.3.32.19981214064401.006b0410@popmail.eznet.net> (akp@eznet.net)


Note that Ann's response is essentially the same as one that might be
given by a sighted person. The real issue is that *whatever* the
interface, as a blind user, I, at least, want a way to access
it. There are some tasks for which command line programs are ideal,
and others for which visual/graphical interfaces are ideal. As Ann
says, some tasks are better suited for line editors and others less so.

> IMHO, it depends on what you're doing.  If I'm going to write a long
> document, like a report, then a full screen editor is what I want because
> you can move about easier within it. You can go to certain pages instead of
> lines and so on.
> 
> If, on the other hand, I'm writing something short, or if I am programming
> in MOO, or looking for errors in a program in MOO that I have written, then
> a line editor is much easier to use.
> 
> I guess what I am saying is that IMHO, it depends on why you're using the
> editor.
> 
> Ann P.


  reply	other threads:[~ UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Richard Uhtenwoldt
 ` Ann K. Parsons
   ` wlestes [this message]
     ` 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
 ` the glass tty model of human-computer interaction wlestes
 ` 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=199812141514.KAA01672@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).