Computer Old Farts Forum
 help / color / mirror / Atom feed
From: Lars Brinkhoff <lars@nocrew.org>
To: Dan Cross <crossd@gmail.com>
Cc: Jonathan Gray <jsg@jsg.id.au>,
	Computer Old Farts Followers <coff@tuhs.org>
Subject: [COFF] Re: [TUHS] Re: project athena (was Re: Setting up an X Development Environment for Mac OS)
Date: Fri, 10 Feb 2023 18:33:52 +0000	[thread overview]
Message-ID: <7w8rh54bfz.fsf@junk.nocrew.org> (raw)
In-Reply-To: <CAEoi9W6-XmdFWCB4gXRDLCBhOAc=ZejA94G7VYBDcojK92EdVA@mail.gmail.com> (Dan Cross's message of "Fri, 10 Feb 2023 12:19:25 -0500")

Dan Cross wrote:
> Oh yeah, I imagine [SUPDUP] was implemented on Lisp machines, probably
> for connecting to ITS. Lars, do you know?

I don't know if it was first implemented on ITS or Lisp machines, but
one of those two.  SUPDUP is basically just ITS' internal terminal
buffer codes for text and cursor movement, adopted as a network
protocol.  So certainly the first SUPDUP server would have been written
for ITS.  Stanford's AI lab also adopted the protocol.  But outside
those two sites, almost no one.

The name comes from "super-duper image mode", shortened to fit ITS' file
name limit of six characters.  On ITS, a terminal may be opened in
"ASCII mode" which means control chacters are interpreted.  In "image
mode" most control characters are passed through verbatim.  There's a
special "super-image mode" where *all* characters are passed through.
So "super-duper image mode", then, alludes to the fact that even the
normally invisible internal codes are passed through.

  reply	other threads:[~2023-02-10 18:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <3e272d72-b77a-d347-b5c3-7ed19482e5af@gmail.com>
     [not found] ` <3h5FEAegoTs6FrhHODiW-rBdB59dt_Rmr4G0PIw7flqaJLsmorgPsilm4f2aJkDud-qEljDjnCJcE1uY05Iw4HNQcyNG4W3wzVlLD0UZfLg=@protonmail.com>
     [not found]   ` <CAFH29trXu_SGp-7xv6xqMc49tTeEuyJdKwP-Fyfe6BCrpGZ9nQ@mail.gmail.com>
     [not found]     ` <Y9GIus/Iw21uvkFb@mit.edu>
     [not found]       ` <Y+QeTCCJf3UHagiP@largo.jsg.id.au>
     [not found]         ` <Y+Rfo2QQf9vcs+l1@mit.edu>
2023-02-10  6:19           ` Lars Brinkhoff
     [not found]             ` <Y+X1ulTtZRoKHCRO@largo.jsg.id.au>
2023-02-10 10:12               ` Lars Brinkhoff
2023-02-10 15:25                 ` Warner Losh
2023-02-10 15:33                   ` Dan Cross
2023-02-10 15:44                     ` Clem Cole
2023-02-10 17:19                       ` Dan Cross
2023-02-10 18:33                         ` Lars Brinkhoff [this message]
2023-02-10 18:43                           ` Lars Brinkhoff
2023-02-10 18:44                         ` Warner Losh
2023-02-10 18:53                           ` Warner Losh
2023-02-10 18:21                     ` Lars Brinkhoff
2023-02-10 20:21                       ` Lars Brinkhoff
2023-02-10 18:34                     ` Warner Losh

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=7w8rh54bfz.fsf@junk.nocrew.org \
    --to=lars@nocrew.org \
    --cc=coff@tuhs.org \
    --cc=crossd@gmail.com \
    --cc=jsg@jsg.id.au \
    /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).