From: James Frew <frew@ucsb.edu>
To: tuhs@tuhs.org
Subject: [TUHS] Re: Compatibility question
Date: Sun, 17 Dec 2023 10:04:09 -0800 [thread overview]
Message-ID: <17d9946c-6f41-4c56-9cb0-3218a2550299@ucsb.edu> (raw)
In-Reply-To: <DxACovqRKKIMOfC0g1pwGRuTFi3DH_PHoG8YmC-k0p7cMGTVGsSch7VtBzrnaZeLCZKOKokC8gOYqlrEh0memA77YhauZ86yS8HXB_6nWGE=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 564 bytes --]
Wow, an actual VT-100! Have you tried "smooth scrolling" (aka "barf
mode")? AFAIK none of the emulators (or "VT100-compatible" iron, for
that matter) ever bothered to replicate this (for which hackers prone to
motion sickness remain grateful 🤢)
/Frew
P.S.: Fond memories of the USENIX where Rob Pike, in a talk describing
the Blit, announced "and [pause] it is NOT VT-100 compatible", to
thunderous applause. A lot of termcap tweakers in that audience...
On 2023-12-17 00:08, segaloco via TUHS wrote:
> secured a VT100 for a reasonable price
[-- Attachment #2: Type: text/html, Size: 1087 bytes --]
next prev parent reply other threads:[~2023-12-18 2:48 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-17 5:55 David Arnold
2023-12-17 8:08 ` segaloco via TUHS
2023-12-17 18:04 ` James Frew [this message]
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
-- strict thread matches above, loose matches on Subject: below --
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
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
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=17d9946c-6f41-4c56-9cb0-3218a2550299@ucsb.edu \
--to=frew@ucsb.edu \
--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).