public inbox for blinux-list@redhat.com
 help / color / mirror / Atom feed
From: sholmes@primenet.com (Steve Holmes)
To: blinux-list@redhat.com
Subject: Re: the glass tty model of human-computer interaction
Date: Fri, 01 Jan 1999 11:39:16 -0700	[thread overview]
Message-ID: <368e13e0.311578919@192.168.1.1> (raw)
In-Reply-To: <Ikxh2cj9CVON091yn@concentric.net>

I've always prefered using full screen or "visual" editors.  I always
found line editors to be too okward and clumbsy for me.

My favorite editor of all time is the semware editor for DOS and
programmers file editor for windows a close second.  The linux or unix
full screen editors such as VI or emacs, have navigation commands far
less intuitive than their DOS / windows counterparts.

On Sun, 27 Dec 1998 21:37:12 -0800, mikek24@concentric.net (Mike
Keithley) wrote:

>>so, if you are blind and have used a line editor, please tell me whether
>>you prefer line editors or visual editors.
>>
>I've used line editors on Compuserve and HPUX in the days when I was
>using the VersaBraille.  I never did like them because I always got
>lost.  Vi is much nicer through a VT100 terminal, even working through a
>slow derial connection.

--
<Steve> Holmes
Tempe, Arizona  USA


      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
 ` the glass tty model of human-computer interaction wlestes
 ` Jude Dashiell
 ` Jude Dashiell
 ` James H. Cloos Jr.
 ` Mike Keithley
   ` Steve Holmes [this message]

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=368e13e0.311578919@192.168.1.1 \
    --to=sholmes@primenet.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).