The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Steffen Nurpmeso <steffen@sdaoden.eu>
To: "John P. Linderman" <jpl.jpl@gmail.com>
Cc: steve jenkin <sjenkin@canb.auug.org.au>, TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Early Unix and Keyboard Skills
Date: Wed, 02 Nov 2022 14:27:34 +0100	[thread overview]
Message-ID: <20221102132734.PwCRX%steffen@sdaoden.eu> (raw)
In-Reply-To: <CAC0cEp9v1ZhTgEFMNGMGH1GhXo9V87QiOPfbbCuMG1y6D9Esaw@mail.gmail.com>

John P. Linderman wrote in
 <CAC0cEp9v1ZhTgEFMNGMGH1GhXo9V87QiOPfbbCuMG1y6D9Esaw@mail.gmail.com>:
 |When I was in high school (in the early sixties) I tried to sign up for
 |typing, which was taught on manual typewriters. I was told that the class
 |was for girls only, and I was turned away. I never did develop good typing
 |skills. I'm pretty much a two-fingered typist. Ironically, I have probably

This can be a winner:

  https://www.youtube.com/watch?v=G4nX0Xrn-wo

(The classic.)

 |done more typing than 90% of the female classmates who were allowed to take
 |the class.

These machine-gunners are in another league per se from my modest
point of view.  Ten finger thunderstorms.

 |Precision figured mightily in those days, which may also have pre-dated
 |white-out. Eliminating an error was a big deal. Now it's dead easy, and
 |auto-correct has already fixed several errors in this message.

Since i now own a (used!!) smartphone i unfortunately have to live
with such things when doing my little bit of SMS messaging.  It is
terrible.  Ooften do i have to delete the word entirely to unlock
the screen.  Ach! for the Asians who commit suicide because they
messed up a calligraphical painting.

It seems to me TUHS has lost its Sender: message header btw, which
longs for fixing as it is SHOULD in RFC 5322 in this ML case
(except for Warren himself, maybe).

--steffen
|
|Der Kragenbaer,                The moon bear,
|der holt sich munter           he cheerfully and one by one
|einen nach dem anderen runter  wa.ks himself off
|(By Robert Gernhardt)

  parent reply	other threads:[~2022-11-02 13:28 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  2:36 [TUHS] " steve jenkin
2022-11-02  6:53 ` [TUHS] " Michael Kjörling
2022-11-02  7:11   ` Rob Pike
2022-11-02 13:28     ` Clem Cole
2022-11-03 21:51     ` Stuff Received
2023-08-05 23:53     ` scj
2023-08-06  0:22       ` KenUnix
2023-08-06  0:43         ` Larry McVoy
2023-08-06 14:51           ` Leah Neukirchen
2023-08-06 15:01             ` Larry McVoy
2023-08-06 16:31             ` Clem Cole
2023-08-06 18:20               ` Jon Forrest
2023-08-07  4:56                 ` Adam Thornton
2023-08-06  8:37       ` Ronald Natalie
2022-11-02 12:13 ` Steffen Nurpmeso
2022-11-02 12:24   ` Steffen Nurpmeso
2022-11-02 20:35     ` Ron Natalie
2022-11-02 12:26   ` John P. Linderman
2022-11-02 13:07     ` Larry Stewart
2022-11-02 13:16       ` Larry McVoy
2022-11-02 13:27     ` Steffen Nurpmeso [this message]
2022-11-02 19:01 ` jason-tuhs
2022-11-02 19:20   ` John P. Linderman
2022-11-03  1:47     ` Ronald Natalie
2022-11-03  1:59       ` Dave Horsfall
2022-11-03  3:01       ` Clem Cole
2022-11-03 15:17       ` Paul Winalski
2022-11-03 16:18         ` Clem Cole
2022-11-03 17:02         ` John Cowan
2022-11-03 19:36           ` Rich Morin
2022-11-03 20:01             ` Charles H Sauer (he/him)
2022-11-02 12:16 Douglas McIlroy

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=20221102132734.PwCRX%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    --cc=jpl.jpl@gmail.com \
    --cc=sjenkin@canb.auug.org.au \
    --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).