The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: grog@lemis.com (Greg 'groggy' Lehey)
Subject: [TUHS] Command-line options
Date: Sun, 27 Mar 2016 17:57:22 +1100	[thread overview]
Message-ID: <20160327065722.GR3766@eureka.lemis.com> (raw)
In-Reply-To: <1459059513.1943874.560637466.6C561BB5@webmail.messagingengine.com>

On Sunday, 27 March 2016 at  2:18:33 -0400, Random832 wrote:
> On Sat, Mar 26, 2016, at 22:01, Greg 'groggy' Lehey wrote:
>> All octal from here on.
>>
>> CDC had several different character sets, most called BCD.  They were
>> unlike Fieldata, which in fact bore some resemblance to ASCII (letters
>> starting @ABC.. from 0 (or 40 in ASCII), digits starting at 60, ...)
>
> Wikipedia mentions one called "CDC display code" that went :ABC..., then
> the digits followed after Z.

Ah, right.  That was on my table too, but I didn't understand it.

> Also, according to Wikipedia, Fieldata was a seven-bit code

Yes, I saw that too.  As used on the big UNIVACs, only the low-order 6
bits were used.  I note that the upper 64 characters include control
characters.

> with A at 006 (putting Z at 037) it wasn't ASCII-like at all, except
> for having the letters in a continuous run.

Hmm.  Somewhere I read a different version where the A followed
directly after the @.  I stand corrected.

Greg
--
Sent from my desktop computer.
Finger grog at FreeBSD.org for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed.  If your Microsoft MUA reports
problems, please read http://tinyurl.com/broken-mua
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20160327/dcb1246c/attachment.sig>


  reply	other threads:[~2016-03-27  6:57 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
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 [this message]
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=20160327065722.GR3766@eureka.lemis.com \
    --to=grog@lemis.com \
    /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).