The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: "John P. Linderman" <jpl.jpl@gmail.com>
To: Jaap Akkerhuis <jaapna@xs4all.nl>
Cc: TUHS <tuhs@tuhs.org>
Subject: Re: [TUHS] keyboards and command names
Date: Wed, 5 Feb 2020 10:47:21 -0500	[thread overview]
Message-ID: <CAC0cEp8ZosxgmmHwgcoYM8iWGJmNXf=ZaTith6UgPeUZ0Cyocw@mail.gmail.com> (raw)
In-Reply-To: <1FE9FA5C-9802-4DAB-9814-3D15BBA2D10E@xs4all.nl>

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

I of course defer to dmr about the major influence, but I very much
appreciated the brevity when printing programs and shell scripts and lines
in ed at 110 baud, even with a terminal having a respectable keyboard.  I
printed much more than I entered.

On Wed, Feb 5, 2020 at 10:38 AM Jaap Akkerhuis <jaapna@xs4all.nl> wrote:

>
>
> > I have always suspected that the brevity of the Unix command names was
> strongly
> > influenced by the clunky keyboards on the teletypes that were being
> used.  Can
> > anyone confirm, deny, and/or comment on this?
>
> Peter Collinson made the same observation at the 25th year celebration
> of UNIX (USENIX, Washington) and it was confirmed by dmr.
>
>         jaap
>
>

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

  reply	other threads:[~2020-02-05 15:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-05 15:05 Rich Morin
2020-02-05 15:30 ` Jaap Akkerhuis
2020-02-05 15:47   ` John P. Linderman [this message]
2020-02-05 16:18     ` Clem Cole
2020-02-05 21:03 ` Andrew Newman
2020-02-05 21:59   ` Harald Arnesen
2020-02-05 22:20     ` Dave Horsfall
2020-02-05 23:40       ` Arthur Krewat
2020-02-10 17:11         ` Paul Winalski

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='CAC0cEp8ZosxgmmHwgcoYM8iWGJmNXf=ZaTith6UgPeUZ0Cyocw@mail.gmail.com' \
    --to=jpl.jpl@gmail.com \
    --cc=jaapna@xs4all.nl \
    --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).