From: clemc@ccc.com (Clem Cole)
Subject: [TUHS] I swear! I rtfm'ed
Date: Thu, 1 Jan 2015 10:45:37 -0500 [thread overview]
Message-ID: <CAC20D2PmK9zJAXEHv75DKOD-2gWJkGbR9A+C0hXonescC3_C6g@mail.gmail.com> (raw)
In-Reply-To: <CAHYQbfDOZwzcwCesrBk=OjMbstVnkr39CJm-80wM=Bq4JRQpWA@mail.gmail.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1269 bytes --]
On Wed, Dec 31, 2014 at 5:30 PM, Jacob Ritorto <jacob.ritorto at gmail.com>
wrote:
> CIT-101 from c.itoh
I remember those, but I do not have a manual for it.
I reasonable guess is they tried to clone the VT-100 which means its ANSI
sequences but not full ANSI and lots of strangeness - Thank you to my old
friend Tom Kent who had a lot to do with the original FW and the keyboard.
In his defense, the ANSI sequences were not yet a standard when then
started that project. So they took what they knew was going to be there,
add a ton of DEC specific stuff and the result is history.
BTW: If you even wanted to know why the original Masscomp keyboard worked
as it did, was because Tom had the "second systems effect" when he did the
MC-500 and I always tease him about it all the time - although unlike the
MC-500 you could not use the VT-100 as a weapon ;-)
Anyway - I just looked in the original VT-100 programmer guide again and
could not find the sequence "\033c" defined in it. So I'm >>guessing<< Tom
and team did not implement it, and thus c.itoh did not either when they
cloned it.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20150101/cf020c77/attachment.html>
next prev parent reply other threads:[~2015-01-01 15:45 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-30 22:56 Jacob Ritorto
2014-12-30 22:59 ` Milo Velimirovic
2014-12-30 23:03 ` Larry McVoy
2014-12-31 0:03 ` Steve Nickolas
2014-12-30 23:05 ` Warren Toomey
2014-12-31 0:01 ` Jacob Ritorto
2014-12-31 2:22 ` Dan Stromberg
2014-12-31 2:33 ` Mary Ann Horton
2014-12-31 5:44 ` Jacob Ritorto
2014-12-31 6:02 ` [TUHS] K&R C on a modern Linux box? ( was Re: I swear! I rtfm'ed ) Derrik Walker v2.0
2014-12-31 6:16 ` Jacob Ritorto
2014-12-31 7:52 ` Derrik Walker v2.0
2014-12-31 6:24 ` [TUHS] I swear! I rtfm'ed Dave Horsfall
2014-12-31 6:36 ` Lyndon Nerenberg
2014-12-31 14:58 ` Tim Bradshaw
2014-12-31 15:31 ` arnold
2014-12-31 15:37 ` Milo Velimirovic
2014-12-31 17:37 ` Derrik Walker v2.0
2014-12-31 20:09 ` Larry McVoy
2014-12-31 22:25 ` Jacob Ritorto
2014-12-31 16:11 ` Mary Ann Horton
2014-12-31 20:14 ` Clem Cole
2014-12-31 20:45 ` Erik E. Fair
2014-12-31 21:05 ` Clem Cole
2014-12-31 22:30 ` Jacob Ritorto
2014-12-31 23:06 ` Mary Ann Horton
2014-12-31 23:11 ` Jacob Ritorto
2015-01-01 15:45 ` Clem Cole [this message]
[not found] <mailman.110.1420006566.3354.tuhs@minnie.tuhs.org>
2014-12-31 10:37 ` Johnny Billquist
2014-12-31 11:13 ` arnold
2014-12-31 16:25 Noel Chiappa
[not found] <mailman.116.1420056874.3354.tuhs@minnie.tuhs.org>
2014-12-31 23:52 ` Johnny Billquist
2015-01-01 1:29 ` Erik E. Fair
2015-01-01 15:03 ` Johnny Billquist
2015-01-01 15:59 ` Mary Ann Horton
2015-01-01 20:18 ` Dave Horsfall
2015-01-01 20:11 ` Dave Horsfall
2015-01-01 16:01 ` Clem Cole
2015-01-01 16:11 ` Johnny Billquist
2015-01-01 16:59 ` Clem Cole
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=CAC20D2PmK9zJAXEHv75DKOD-2gWJkGbR9A+C0hXonescC3_C6g@mail.gmail.com \
--to=clemc@ccc.com \
/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).