The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: cowan@mercury.ccil.org (John Cowan)
Subject: [TUHS] Command-line options
Date: Fri, 25 Mar 2016 22:10:18 -0400	[thread overview]
Message-ID: <20160326021018.GG897@mercury.ccil.org> (raw)
In-Reply-To: <20160325232516.GG3766@eureka.lemis.com>

Greg 'groggy' Lehey scripsit:

> > I'm going to throw in an aside at this point. PDP-7 Unix packed 2
> > characters per 18-bit word.
> 
> Really?  Most machines of that era used 6 bit characters, so you could
> fit 3 in an 18 bit word.  I had hypothesized that that was the reason
> for word lengths in increments of 6 bits in those days.

So they did, but DEC machines in general were always ASCII.  The PDP-8
used both 8-bit characters (ASCII with the high bit set) and 6-bit
ones (stripped ASCII without control characters or lower-case ones).
The former were packed three 8-bit characters in two 12-bit words; the
latter, two characters in one 12-bit word.  The PDP-10 packed five 7-bit
characters into a 36-bit word with one bit left over, which was used
(if at all) for various purposes.  Not until the PDP-11 did the 8-bit
character get aligned with the machine word size.

> In passing, it's interesting to note that the initial @ or # were used
> to identify a command.  Other systems of the time did similar things.
> My guess is that the command prompt in Unix started life as a "here's
> your command leadin for free".

All DEC systems had command prompts of the Unix type, though not changeable:
the original prompt was simply ".".  In the DOS/BATCH-11 operating system,
however, the shell-level command prompt was $ and the intra-command prompt
was *, and you wrote batch files with explicit $ and * sigils, so that
a $-marked line implicitly indicated the end of input for the previous
command, a compact equivalent of here-scripts.

-- 
John Cowan          http://www.ccil.org/~cowan        cowan at ccil.org
To say that Bilbo's breath was taken away is no description at all.  There are
no words left to express his staggerment, since Men changed the language that
they learned of elves in the days when all the world was wonderful. --The Hobbit


  reply	other threads:[~2016-03-26  2:10 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-25 14:43 [TUHS] Is the Teletype the unsung hero of Unix? Aharon Robbins
2016-03-25 19:47 ` Jaap Akkerhuis
2016-03-25 21:03 ` Diomidis Spinellis
2016-03-28 20:12   ` scj
2016-04-01 14:06     ` Dave Horsfall
2016-04-01 22:41       ` Greg 'groggy' Lehey
2016-03-25 21:29 ` [TUHS] Command-line options Warren Toomey
2016-03-25 23:25   ` Greg 'groggy' Lehey
2016-03-26  2:10     ` John Cowan [this message]
2016-03-26  3:09       ` Charles Anthony
2016-03-26 19:43         ` Clem Cole
2016-03-26 20:54           ` Ronald Natalie
2016-03-26 22:05             ` John Cowan
2016-03-27  1:25             ` Dave Horsfall
2016-03-27  1:50               ` Charles Anthony
2016-03-27  2:01               ` Greg 'groggy' Lehey
2016-03-27  6:18                 ` Random832
2016-03-27  6:57                   ` Greg 'groggy' Lehey
2016-03-27 19:38                   ` Dave Horsfall
2016-03-27  1:35             ` Greg 'groggy' Lehey
2016-03-26  3:54 ` [TUHS] Is the Teletype the unsung hero of Unix? Greg 'groggy' Lehey
2016-03-26  4:30   ` Steve Nickolas
2016-03-26  5:44     ` Greg 'groggy' Lehey
2016-03-26  8:33       ` Steve Nickolas

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=20160326021018.GG897@mercury.ccil.org \
    --to=cowan@mercury.ccil.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).