The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: The Unix Heritage Society mailing list <tuhs@tuhs.org>
Subject: Re: [TUHS] Seeking wisdom from Unix Greybeards
Date: Wed, 10 Feb 2021 17:26:10 -0500	[thread overview]
Message-ID: <CAC20D2ORqo_XMGTG_AHg_PZu_+Fp6D=v=M6EfpSpJxSZBLbVhw@mail.gmail.com> (raw)
In-Reply-To: <m1l9ufi-0036urC@more.local>

[-- Attachment #1: Type: text/plain, Size: 1116 bytes --]

On Wed, Feb 10, 2021 at 1:57 PM Greg A. Woods <woods@robohack.ca> wrote:

> As an aside, the DEC VT100 terminal was an early (it came out a year before
> X3.64)

Yup, It was spec'ed at least a year ahead and its the code was
committed before the standard was even in a draft vote.



> and relatively complete (for a video terminal application) implementation
> of X3.64.
>
Although different from and the missing stuff was a bear.  Originally,
VT100 !=  X3.64       which has caused many issues over the years.  The big
issue was the lack of a proper insert/delete, it used scrolling regions
instead.  Kudos to Mary Ann for working through that whole mess years ago!
That's why back in the day, I preferred the H19 and later the Ambassador ;-)

My memory is that was ECMA that got the DEC changes/differences added/put
back/made legal.  But originally, there were not.   At one point, I had a
copy of the internal DEC documentation (which I think I got from Tom Kent
who wrote much of the rom code and had been on the committee for DEC at one
point, but I don't remember).

Clem
ᐧ
ᐧ

[-- Attachment #2: Type: text/html, Size: 3057 bytes --]

  reply	other threads:[~2021-02-10 22:26 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
     [not found] <20201126183746.DD93218C087@mercury.lcs.mit.edu>
     [not found] ` <7DBB40AE-259D-494E-8ABF-2FE4D47F4052@iitbombay.org>
2020-11-26 19:02   ` lars
2020-11-26 21:56   ` steffen

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='CAC20D2ORqo_XMGTG_AHg_PZu_+Fp6D=v=M6EfpSpJxSZBLbVhw@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=tuhs@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).