From: Rich Morin <rdm@cfcl.com>
To: TUHS <tuhs@tuhs.org>
Subject: [TUHS] keyboards and command names
Date: Wed, 5 Feb 2020 07:05:24 -0800 [thread overview]
Message-ID: <F5C1F516-167C-4A64-B405-156364388BF3@cfcl.com> (raw)
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?
-r
next reply other threads:[~2020-02-05 15:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-05 15:05 Rich Morin [this message]
2020-02-05 15:30 ` Jaap Akkerhuis
2020-02-05 15:47 ` John P. Linderman
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=F5C1F516-167C-4A64-B405-156364388BF3@cfcl.com \
--to=rdm@cfcl.com \
--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).