The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: steffen@sdaoden.eu (Steffen Nurpmeso)
Subject: [TUHS] Dash options
Date: Wed, 29 Nov 2017 20:16:43 +0100	[thread overview]
Message-ID: <20171129191643.XPHH3%steffen@sdaoden.eu> (raw)
In-Reply-To: <20171128062845.GB5277@eureka.lemis.com>

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1752 bytes --]

Greg 'groggy' Lehey <grog at lemis.com> wrote:
 |On Monday, 27 November 2017 at 21:51:13 -0800, Jon Steinhart wrote:
 |> Does anybody know the history of dash options?  Were they
 |> a UNIX thing or did UNIX borrow them from something earlier?
 |
 |If you mean specificall the dash, I can't help much.  But there were
 |similar ideas elsewhere.  UNIVAC EXEC-8 (for the 1108, late 1960s) had
 |options that followed the command with a comma, like:
 |
 |  @RUN,G GOPU,STANDARD,STANDARD
 |  @ADD,PL ASGDMS              . ASSIGNIERT DATENBASIS

"WEIßT DATENBASIS ZU" or "ZUWEISUNG DATENBASIS"

 |  @ASG,A PF.                  . PF IST PROGRAMM-FILE MIT GOPU

"PF IST PROGRAMM-DATEI MIT GOPU" or so.

 |  @XQT PF.GOPU
 |
 |The letters after the comma were option letters, conveniently packed
 |into a machine word so that they didn't require parsing.

Or.  Or the person who wrote the code above knew how German will
look like 50 years later.  Which could very well be, of course.
I am still impressed by the Lidlicker film the URL of which was
posted on this list, and the spirit and, well, let me say
progressiveness of the intellect of all the portrayed persons.
It was elevating to witness and also, a bit, become reminded of
this America in 2017.  A few weeks ago i could not do any
different but spent quite a few hours reading and thinking about,
and admiring Jacqueline Kennedy!  I was born almost a decade
later, but nonetheless seeing her sitting straight beside the
remains of her husband, i will never admire this woman enough.
And her naturalness.

--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)


  reply	other threads:[~2017-11-29 19:16 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-28  5:51 Jon Steinhart
2017-11-28  6:05 ` Dave Horsfall
2017-11-28  6:49   ` Andrew Warkentin
2017-11-28 11:18     ` Ralph Corderoy
2017-11-28 11:49       ` Michael Kjörling
2017-11-28 12:46         ` Ralph Corderoy
2017-11-28 18:01       ` Lawrence Stewart
2017-11-28 19:36     ` Paul Winalski
2017-11-28 20:03       ` Clem Cole
2017-11-28  6:28 ` Greg 'groggy' Lehey
2017-11-29 19:16   ` Steffen Nurpmeso [this message]
     [not found]     ` <20171204054651.GA17671@eureka.lemis.com>
     [not found]       ` <20171204215701.l9Pvr%steffen@sdaoden.eu>
2017-12-05 13:22         ` Steffen Nurpmeso
2017-12-07  5:15           ` Greg 'groggy' Lehey
2017-11-28 13:19 Noel Chiappa
2017-11-28 18:20 ` Clem Cole
2017-11-28 21:56   ` Dave Horsfall
     [not found] <mailman.376.1511899437.9955.tuhs@minnie.tuhs.org>
2017-11-28 21:30 ` Paul Ruizendaal
2017-11-29  1:23 Doug McIlroy
2017-11-29  1:37 ` George Michaelson
2017-11-29  2:22 ` Charles Anthony
2017-11-29 14:03 Noel Chiappa
2017-11-29 20:29 ` Charles Anthony

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=20171129191643.XPHH3%steffen@sdaoden.eu \
    --to=steffen@sdaoden.eu \
    /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).