From: Lars Brinkhoff <lars@nocrew.org>
To: "Joseph Holsten" <joseph@josephholsten.com>
Cc: segaloco <tuhs@tuhs.org>
Subject: [TUHS] Re: DMD 5620 simulator
Date: Wed, 14 Sep 2022 07:48:17 +0000 [thread overview]
Message-ID: <7wzgf24cse.fsf@junk.nocrew.org> (raw)
In-Reply-To: <a61aa4e6-7cd4-4ce9-8145-82b36fe99dc1@www.fastmail.com> (Joseph Holsten's message of "Tue, 13 Sep 2022 15:29:39 -0700")
Joseph Holsten wrote:
> I was wondering why you’d pick this term of all historical terms to
> emulate. Now I have a terrible urge to try my hand at an ADM-3A.
Please do! There is a suite of terminal emulators that try to use the
original font and render the display somewhat pleasingly. It includes
VT05, VT50, VT52, DataPoint 3300, and a few more. Arguably it's mostly
eye candy, but I'd say it adds a little retro flair to the experience.
In a similar vein, I have written terminal simulators that run the
original VT100 and VT52 firmware and try to render the video output in
real time.
> Which just reminds me of this teletype 33 ad:
> https://commons.wikimedia.org/wiki/File:Teletype_Model_33_Terminal_June_1974.jpg
I have long maintained we need a good teletype emulator... nay,
simulator. Think physics engine.
prev parent reply other threads:[~2022-09-14 7:49 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 23:25 [TUHS] DMD 5620 simulator Seth Morabito
2022-09-13 1:53 ` [TUHS] " Larry McVoy
2022-09-13 1:58 ` Rob Pike
2022-09-13 2:12 ` Larry McVoy
2022-09-13 13:01 ` Clem Cole
2022-09-14 0:23 ` Rob Pike
2022-09-14 0:33 ` Larry McVoy
2022-09-14 0:43 ` Rich Salz
2022-09-13 19:21 ` Paul Guertin
2022-09-13 22:29 ` Joseph Holsten
2022-09-13 23:35 ` Larry McVoy
2022-09-14 3:55 ` Joseph Holsten
2022-09-14 16:09 ` Kevin Bowling
2022-09-14 0:44 ` Steve Nickolas
2022-09-14 0:47 ` joe mcguckin
2022-09-14 3:10 ` Seth Morabito
2022-09-14 3:40 ` Warner Losh
2022-09-14 7:48 ` Lars Brinkhoff [this message]
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=7wzgf24cse.fsf@junk.nocrew.org \
--to=lars@nocrew.org \
--cc=joseph@josephholsten.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).