Computer Old Farts Forum
 help / color / mirror / Atom feed
From: tih at hamartun.priv.no (Tom Ivar Helbekkmo)
Subject: [COFF] Comparative promptology
Date: Wed, 30 Oct 2019 09:19:20 +0100	[thread overview]
Message-ID: <m2bltyzlvb.fsf@thuvia.hamartun.priv.no> (raw)
In-Reply-To: <fe823dd3-8b5a-4a4f-1705-1881e055b5ca@gmail.com> (Harald Arnesen's message of "Tue, 29 Oct 2019 11:32:29 +0100")

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

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.  It
was mapped to ASCII 64 externally, a natural choice, because FIELDATA
had no @, ASCII had no nabla -- and Master Space was encoded as decimal
64 in FIELDATA already.

The name stuck, and @ kept being called nabla at least until 1990.

-tih
-- 
Most people who graduate with CS degrees don't understand the significance
of Lisp.  Lisp is the most important idea in computer science.  --Alan Kay


  reply	other threads:[~2019-10-30  8: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 [this message]
2019-10-31  1:19                         ` [COFF] Fieldata characters (was: Comparative promptology) grog
2019-10-29 19:57                   ` [COFF] Comparative promptology 
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=m2bltyzlvb.fsf@thuvia.hamartun.priv.no \
    --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).