The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Jon Forrest <nobozo@gmail.com>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Compatibility question
Date: Mon, 18 Dec 2023 14:29:05 -0800	[thread overview]
Message-ID: <acbccaf6-5f9d-474b-9c71-1df45527db17@gmail.com> (raw)
In-Reply-To: <CABH=_VQzW1v9qGeDLvfYDw9NGUaoWR2hruWh6jG3rNSvBswYzg@mail.gmail.com>

Speaking of how VMS handled escape sequences, in the 1980s I
swung both ways (e.g. VMS and Unix). When DEC announced TERMTABLE,
a termcap-like library for VMS, I thought it would be fun to
write a termcap to TERMTABLE conversion program, so I did.
I thought this would let me run VMS TUI programs on non-DEC
compatible terminals.

This turned out to be a bad idea because none (?) of the DEC-written
programs actually used TERMTABLE. They were all hard-wired to use
VT100 (and VT52?) escape sequences. As I recall, I couldn't find any
programs that used TERMTABLE in non-trivial ways so I gave up.

Jon Forrest
UCB (ret.)

  reply	other threads:[~2023-12-18 22:29 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-17  2:01 [TUHS] " KenUnix
2023-12-17 18:13 ` [TUHS] " Seth Morabito
2023-12-17 18:23   ` segaloco via TUHS
2023-12-17 22:51     ` Mary Ann Horton
2023-12-17 22:59       ` Ron Natalie
2023-12-17 23:08         ` Warner Losh
2023-12-18  0:35           ` KenUnix
2023-12-18  3:24             ` segaloco via TUHS
2023-12-18 17:05         ` Paul Winalski
2023-12-18 22:29           ` Jon Forrest [this message]
2023-12-19  1:46           ` Dave Horsfall
2023-12-19  7:56             ` Harald Arnesen
2023-12-19 17:40             ` Paul Winalski
2023-12-19 18:07               ` Tom Lyon
2023-12-19 20:23                 ` Clem Cole
2023-12-19 21:31                   ` Paul Winalski
2023-12-19 23:52                     ` Bakul Shah
2023-12-20  0:05                       ` Greg 'groggy' Lehey
2023-12-20  1:03                         ` Bakul Shah
2023-12-20  1:32                           ` Greg 'groggy' Lehey
2023-12-20  6:05                             ` Wesley Parish
2023-12-20  0:15                       ` Mary Ann Horton
2023-12-20 16:07                         ` Adam Thornton
2023-12-20 16:22                           ` Clem Cole
2023-12-20 18:11                           ` Alan D. Salewski
2023-12-20 16:34                         ` Paul Winalski
2023-12-20 18:15                           ` Jon Forrest
2023-12-20  1:11                       ` Steffen Nurpmeso
2023-12-20  1:23                         ` Tom Lyon
2023-12-21  3:53                     ` Rod Bartlett via TUHS
2023-12-19 21:34                   ` Rob Pike
2023-12-17  5:55 David Arnold
2023-12-17  8:08 ` segaloco via TUHS
2023-12-17 18:04   ` James Frew
2023-12-17 18:18     ` Lars Brinkhoff
2023-12-17 19:14       ` Brad Spencer
2023-12-17 18:48     ` Paul Winalski
2023-12-17 18:59       ` Warner Losh
2023-12-17 20:24       ` Dave Horsfall
2023-12-17 19:26     ` Dan Cross
2023-12-17 20:08       ` Warner Losh
2023-12-17 14:07 ` Brad Spencer
2023-12-17 14:47   ` Arrigo Triulzi via TUHS

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=acbccaf6-5f9d-474b-9c71-1df45527db17@gmail.com \
    --to=nobozo@gmail.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).