Computer Old Farts Forum
 help / color / mirror / Atom feed
From: grog at lemis.com (Greg 'groggy' Lehey)
Subject: [COFF] Fieldata characters (was:  Comparative promptology)
Date: Thu, 31 Oct 2019 12:19:05 +1100	[thread overview]
Message-ID: <20191031011905.GA68439@eureka.lemis.com> (raw)
In-Reply-To: <m2bltyzlvb.fsf@thuvia.hamartun.priv.no>

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

On Wednesday, 30 October 2019 at  9:19:20 +0100, COFF wrote:
> Harald Arnesen <skogtun at gmail.com> writes:
>
>> Harald Arnesen [29.10.2019 11:30]:
>>> Warner Losh [28.10.2019 20:57]:
>>>
>>>> "@  " was the TOPS-20 prompt.
>>>
>>> Also the Sintran (Norsk Data) prompt.
>>
>> btw, we used to call it "grisehale" ("pig's tail").
>
> Not at the Norwegian Institute of Technology (now part of the Norwegian
> University of Technology and Science).  There, it was called "nabla",
> because of the EXEC 8 operating system on UNIVAC mainframes, which used
> the FIELDATA character set, and where the "Master Space" character,
> (visually represented by nabla, which looks like an upside-down capital
> delta: '???' if what you're reading this text on supports Unicode) was
> used as a prefix character indicating an operating system command.

I worked for and with UNIVAC for most of the 1970s and early 1980s,
including on EXEC 8/OS 1100, and the master space (binary 0) was
always represented by @, on punched cards, printouts, terminals and
the documentation.  I've just confirmed with my copy of UP-4040,
dating from 1971.  https://en.wikipedia.org/wiki/Fieldata#UNIVAC
agrees, though it notes:

   Sometimes switched with Δ

But that's a delta, not a nabla.  Fieldata also had a Δ (code 04), and
I have never seen this switch.

FWIW, this was in Germany, where we called the @ a „Klammeraffe“
(originally a spider monkey).  This wasn't limited to UNIVAC.

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


  reply	other threads:[~2019-10-31  1:19 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201910272031.x9RKVSem124842@tahoe.cs.Dartmouth.EDU>
     [not found] ` <CAFH29trMHepMHK0C+UapNVXvjfnFMv5ov4W4YS+yOn4i+mhV0A@mail.gmail.com>
     [not found]   ` <CANV78LQa=VTZAMmVeRphTvrkxrkrAzgoU_-KqtdgqfWY2uUZJg@mail.gmail.com>
     [not found]     ` <51f2d838-d097-a93f-b44d-9c670d206d2b@tnetconsulting.net>
     [not found]       ` <alpine.BSF.2.02.1910272110350.28402@frieza.hoshinet.org>
     [not found]         ` <xzdtvssnnqfvfxq9swgv979g@localhost>
     [not found]           ` <alpine.BSF.2.02.1910281106290.77349@frieza.hoshinet.org>
2019-10-28 18:47             ` [COFF] [TUHS] UNIX Backslash History dave
2019-10-28 19:10               ` [COFF] Comparative promptology lars
2019-10-28 19:57                 ` imp
2019-10-28 20:29                   ` jpl.jpl
2019-10-29 10:30                   ` skogtun
2019-10-29 10:32                     ` skogtun
2019-10-30  8:19                       ` tih
2019-10-31  1:19                         ` grog [this message]
2019-10-29 19:57                   ` 
2019-10-30  7:01                   ` lars
     [not found]                 ` <2daf68cb-1b16-05a5-af0c-6d64778b2da2@kilonet.net>
2019-10-28 23:13                   ` krewat
2019-10-29  5:32                     ` lars
2019-10-28 20:43               ` [COFF] [TUHS] UNIX Backslash History paul.winalski
2019-10-28 23:17                 ` krewat
2019-10-31  1:59                 ` gtaylor

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=20191031011905.GA68439@eureka.lemis.com \
    --to=coff@minnie.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).