The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Niklas Karlsson <nikke.karlsson@gmail.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] Typing tutors
Date: Sat, 6 Feb 2021 23:47:13 +0100	[thread overview]
Message-ID: <CAK6BEgd0WMidGQ1dKtvQZyQHSjx1AO4whSgHnBph+rZGYLpB=g@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2102070930110.70858@aneurin.horsfall.org>

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

Den lör 6 feb. 2021 kl 23:39 skrev Dave Horsfall <dave@horsfall.org>:

> On Sat, 6 Feb 2021, Mary Ann Horton wrote:
>
> > At Berkeley, everybody was already a touch typist. That's why vi
> > commands emphasize lower case letters, especially hjkl which are right
> > under the home position. The original reason for hjkl was the ADM3A, but
> > when I added arrow key support to vi and disabled the hardcoded hjkl, a
> > line of grad students made me put it back.
>
> I'm not surprised :-)  We were all playing "rogue" back then.  And my
> favourite terminal was indeed the ADM-3A; it just seemed to be designed
> for Unix, with the ESC key in the right place etc.
>

I'm probably a youngster in this crowd (no, I'm not calling you old farts,
more like people with a long history I respect and am willing to learn
from). Born in 1980. But I had similar reasons for feeling at home with
hjkl. In the 1980s (I think before I even started school) I got my hands on
what was then called HACK for MS-DOS, which of course later became NetHack.
So by the time I started playing with Linux and other *nixes in 2000, I
didn't have any real learning curve with basic vi usage.

Niklas

[-- Attachment #2: Type: text/html, Size: 1587 bytes --]

  reply	other threads:[~2021-02-06 22:47 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-06  2:57 Will Senn
2021-02-06 16:55 ` Clem Cole
2021-02-06 17:22   ` Ron Natalie
2021-02-06 17:29     ` Clem Cole
2021-02-06 17:33     ` Mary Ann Horton
2021-02-06 17:47       ` Ron Natalie
2021-02-06 18:06         ` Clem Cole
2021-02-06 22:38       ` Dave Horsfall
2021-02-06 22:47         ` Niklas Karlsson [this message]
2021-02-07  0:25           ` John Cowan
2021-02-08 22:20             ` Dave Horsfall
2021-02-08 22:58               ` David Barto
2021-02-08 23:01               ` Clem Cole
2021-02-07 17:43         ` Mary Ann Horton
2021-02-07 19:28           ` Dan Cross
2021-02-07 21:32           ` Nemo Nusquam
2021-02-07 23:17             ` Henry Bent
2021-02-07 23:55               ` Steve Nickolas
2021-02-08  0:56                 ` Henry Bent
2021-02-08  5:15                   ` Erik E. Fair
2021-02-08  5:33                     ` Steve Nickolas
2021-02-08 15:54                       ` Will Senn
2021-02-08  5:29             ` Doug McIntyre
2021-02-08 20:41               ` Andrew Newman
2021-02-06 18:56     ` David Barto
2021-02-08 21:50       ` Dave Horsfall
2021-02-09 16:29         ` Mary Ann Horton
  -- strict thread matches above, loose matches on Subject: below --
2017-04-06  2:15 [TUHS] I just noticed all the cfont aka C++ in research Jason Stevens
2017-04-06  2:20 ` Noel Hunt
2017-04-06  2:21   ` Jason Stevens
2017-04-06  6:57 ` [TUHS] Unix emacs at Bell Labs and elsewhere Erik E. Fair

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='CAK6BEgd0WMidGQ1dKtvQZyQHSjx1AO4whSgHnBph+rZGYLpB=g@mail.gmail.com' \
    --to=nikke.karlsson@gmail.com \
    --cc=dave@horsfall.org \
    --cc=tuhs@tuhs.org \
    /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).