From: Brad Spencer <brad@anduin.eldar.org>
To: David Arnold <davida@pobox.com>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: Compatibility question
Date: Sun, 17 Dec 2023 09:07:54 -0500 [thread overview]
Message-ID: <xoncyv4sz0l.fsf@anduin.eldar.org> (raw)
In-Reply-To: <7AD36632-2B2F-43E2-999D-4F6373C3C64C@pobox.com> (message from David Arnold on Sun, 17 Dec 2023 16:55:37 +1100)
David Arnold <davida@pobox.com> writes:
>
>> On 17 Dec 2023, at 13:02, KenUnix <ken.unix.guy@gmail.com> wrote:
>
> -8<—
>
>> I have tried vt100, vt100-am, vt100-nam and none
>> work as expected.
>
> I have a long-ago recollection that using vt100 had rendering issues with emacs, but vt102 was fine. Maybe worth a shot?
>
>
>
> d
Unless you are actually using a real VT100 physical serial terminal
there is very much a non-zero chance that the terminal emulator that you
are using is not really vt100, vt102, or any such thing, but some
subset, superset or variant that isn't quite like a real physical VT100,
close but not exact. You may try 'ansi' or 'xterm', if either of those
are available in the Unix you are using. If not, try a different
terminal emulator.
Example.. a long time ago in a university far away, there was Data
General systems mostly and lots of DG211 terminals. The DG211 have a
ansi mode that is very close to vt100, but not quite. Along comes
various Unix systems, in particular, a RS6000. Wanting to play Moria
(successor to rogue), I found that the ansi mode didn't quite cut it and
ended up hacking up a TERMCAP / TERMINFO entry to deal with the issue as
best as it was possible. I could never come up with a native DG211
entry that worked any better than my hacks. If I recall, the terminal
*MAY* have supported VT52 as well (or that might have been the MV10000
that did some sort of DG211 to VT52 translation) I know I ended up
writing a VT52 terminal emulator (for some reason or other... it was a
long time ago) and I know I used it on the Unix systems that started to
appear around the university as time went on. VT52 was pretty simple
and it tended to work pretty well.
--
Brad Spencer - brad@anduin.eldar.org
next prev parent reply other threads:[~2023-12-18 16:34 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
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 [this message]
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=xoncyv4sz0l.fsf@anduin.eldar.org \
--to=brad@anduin.eldar.org \
--cc=davida@pobox.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).