The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Harald Arnesen <skogtun@gmail.com>
To: tuhs@tuhs.org
Subject: Re: [TUHS] keyboards and command names
Date: Wed, 5 Feb 2020 22:59:08 +0100	[thread overview]
Message-ID: <73524e91-0b05-e4b7-524b-1c7247d48846@gmail.com> (raw)
In-Reply-To: <4425E818-B9C3-4BFA-BD69-EA4A35D9772E@optusnet.com.au>

Andrew Newman [05/02/2020 22.03]:

> Somewhat related.  My first “real” job after university, and
> introduction to UNIX
> et al, was using IBM machines running VM/370 and the CMS single-user OS
> for user
> accounts.  CMS used long command names but, like some other OSes of its
> ilk, allowed
> you to define what it called “abbreviations" via a count of the minimum
> number of
> unique, leading, characters from which it could determine the actual
> command name.
> The CMS file copy program was “copyfile” but the abbreviation length, at
> least at
> our “shop", was 2 and everyone used “co”.  Similarly the editor “xedit”
> was “x”.
> I always found that amusing considering complaints about cryptic UNIX names.

Norsk Data's OS Sintran was the same, except that "COLD-START" (reboot
the OS) was defined twice, so you had to spell it out in full.
-- 
Hilsen Harald


  reply	other threads:[~2020-02-05 21:59 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
2020-02-05 16:18     ` Clem Cole
2020-02-05 21:03 ` Andrew Newman
2020-02-05 21:59   ` Harald Arnesen [this message]
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=73524e91-0b05-e4b7-524b-1c7247d48846@gmail.com \
    --to=skogtun@gmail.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).