The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: lars at nocrew.org (Lars Brinkhoff)
Subject: [TUHS] Seeking wisdom from Unix Greybeards
Date: Thu, 26 Nov 2020 19:02:22 +0000	[thread overview]
Message-ID: <7wr1ogdjr5.fsf@junk.nocrew.org> (raw)
In-Reply-To: <7DBB40AE-259D-494E-8ABF-2FE4D47F4052@iitbombay.org> (Bakul Shah's message of "Thu, 26 Nov 2020 10:50:23 -0800")

Noel Chiappa wrote:
> If the latter, there's the terminal-independent support of video
> terminals in ITS; that dates to the mid-1970's (i.e. circa V5 or
> so). User programs output device-independent display control codes (I
> have this memory that they were called P-Codes, but that could be my
> memory failing), and the OS translated them to the appropriate
> screen-control characters.

That's correct.  Or ^P-codes, from the character that signalled a
control code.  It would be interesting to figure out when they were
introduced.  They were not present in 1972; at this point ITS only
supported printing terminals, Datapoints, and Imlacs.

WAITS allegedly had an even better abstration of terminal control codes.

> One additional hack was that the number of terminal types supported in
> the OS was limited; there was however a protocol called SUPDUP which
> sent (basically) those device-independent codes over a remote login

Basically, but another set of equivalent codes internal to ITS.  SUPDUP
means super-duper image mode, which alludes to image mode.

> (originally over NCP) frm the server machine to the client. The User
> SUPDUP client supported a lot more terminal types; so people with
> odd-ball terminals used to log in, SUPDUP _back_ to their machine, and
> away they went.

See also CRTSTY.


       reply	other threads:[~2020-11-26 19:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201126183746.DD93218C087@mercury.lcs.mit.edu>
     [not found] ` <7DBB40AE-259D-494E-8ABF-2FE4D47F4052@iitbombay.org>
2020-11-26 19:02   ` lars [this message]
2020-11-26 21:56   ` steffen
2020-11-25 17:14 Grant Taylor via TUHS
2020-11-25 17:22 ` Ralph Corderoy
     [not found]   ` <20201126145134.GB394251@mit.edu>
2020-11-26 21:48     ` steffen
2021-02-10 18:57       ` Greg A. Woods
2021-02-10 22:26         ` Clem Cole
2021-02-24 22:20         ` Steffen Nurpmeso
2020-11-26 21:59     ` dave
2020-11-25 17:38 ` Larry McVoy
2020-11-25 18:00 ` Steffen Nurpmeso
2020-11-25 20:03   ` Steffen Nurpmeso
     [not found] ` <CACYmRNAtdJu0ui=CgrEcWH6J3uikCh0=aCLNvk0+V29rypDBAg@mail.gmail.com>
     [not found]   ` <71fdfa2e-1483-4985-3f55-6760b3a84ec0@gmail.com>
     [not found]     ` <20201126182937.GN9589@mcvoy.com>
2020-11-26 23:14       ` erc
2020-11-26 23:23         ` lm

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=7wr1ogdjr5.fsf@junk.nocrew.org \
    --to=tuhs@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).