9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: nigel@9fs.org
To: 9fans@cse.psu.edu
Subject: Re: [9fans] text editor
Date: Fri, 26 Apr 2002 11:45:34 +0100	[thread overview]
Message-ID: <20020426104534.356FA19988@mail.cse.psu.edu> (raw)

[-- Attachment #1: Type: text/plain, Size: 746 bytes --]

As rog points out, if you don't want to watch the screen, you're not
using a visual editor.

hjkl does solve the hand motion issue, but a strong reason for that
mapping was ambiguity between tty escape sequences, and vi(1)
commands. Basically it couldn't tell the difference between the
user pressing escape then A, and a cursor key generating the very
same sequence.

It tried timing out after escape waiting for another character, but
at 9600 baud, users often generated ambiguous sequences within
the timeout. It would never work.

As a result, all users learnt hjkl for their own sanity, and configured
their termcaps not to tell vi(1) about cursor sequences just in case
it was stupid enough to try to tell the difference.


[-- Attachment #2: Type: message/rfc822, Size: 2400 bytes --]

From: Alexander Viro <viro@math.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] text editor
Date: Fri, 26 Apr 2002 06:21:24 -0400 (EDT)
Message-ID: <Pine.GSO.4.21.0204260613271.20558-100000@weyl.math.psu.edu>



On Fri, 26 Apr 2002 nigel@9fs.org wrote:

> To recap the logic (it has been repeated many times in the archives),
> once you switch to mouse centric operation, you become faster, not
> slower.  It may be counterintuitive, but I believe it has been shown
> by research, not that I can quote anything.  You have to move your
> hands to get to the cursor keys

..... unless you have sensible mappings for them - hjkl works fine, as
far as I'm concerned.  Not to (re)start religious wars, but... mouse
pretty much requires visual feedback.  I.e. you need to watch the
screen while you are using it.  Which is bloody inconvenient in a lot
of situations.  FWIW, I still prefer vi, but using sam as extended ed
works for me...

             reply	other threads:[~2002-04-26 10:45 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-26 10:45 nigel [this message]
2002-04-26 11:04 ` Alexander Viro
  -- strict thread matches above, loose matches on Subject: below --
2002-04-29  9:36 Andrew Simmons
2002-04-26 17:31 Russ Cox
2002-04-26 14:52 anothy
2002-04-26 16:59 ` peter huang
2002-04-26 14:10 Russ Cox
2002-04-26 10:27 ` Sam Hopkins
2002-04-29  9:40 ` Douglas A. Gwyn
2002-04-26 13:40 forsyth
2002-04-26 13:27 presotto
2002-04-26 12:46 bwc
2002-04-26 16:33 ` mcguire
2002-04-30  1:54   ` chad
2002-04-26 12:40 nigel
2002-04-26 11:41 forsyth
2002-04-26 11:39 rog
2002-04-26 11:45 ` Boyd Roberts
2002-04-26 10:22 nigel
2002-04-26 11:15 ` Boyd Roberts
2002-04-26 11:25   ` Boyd Roberts
2002-04-26 16:06   ` Ronald G Minnich
2002-04-26 10:11 rog
2002-04-26 23:30 ` Micah Stetson
2002-04-26  9:49 nigel
2002-04-26 10:21 ` Alexander Viro
2002-04-26 11:38   ` Michael Grunditz
2002-04-26 20:35   ` Dan Cross
2002-04-29  9:40     ` Douglas A. Gwyn
2002-04-29  9:36 ` Andrew Stitt
2002-04-29 15:58   ` Douglas A. Gwyn
2002-04-26  8:47 Andrew Stitt

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=20020426104534.356FA19988@mail.cse.psu.edu \
    --to=nigel@9fs.org \
    --cc=9fans@cse.psu.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 NNTP newsgroup(s).