From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 25397 invoked from network); 18 Dec 2023 16:34:01 -0000 Received: from minnie.tuhs.org (2600:3c01:e000:146::1) by inbox.vuxu.org with ESMTPUTF8; 18 Dec 2023 16:34:01 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id C337742415; Mon, 18 Dec 2023 00:08:09 +1000 (AEST) Received: from anduin.eldar.org (anduin.eldar.org [IPv6:2001:470:c620:0:280:c8ff:fef8:70bc]) by minnie.tuhs.org (Postfix) with ESMTPS id 3728842402 for ; Mon, 18 Dec 2023 00:08:02 +1000 (AEST) Received: from anduin.eldar.org (IDENT:brad@localhost [127.0.0.1]) by anduin.eldar.org (8.16.1/8.13.8) with ESMTPS id 3BHE7tL3010588 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NO); Sun, 17 Dec 2023 09:07:55 -0500 (EST) Received: (from brad@localhost) by anduin.eldar.org (8.16.1/8.13.8/Submit) id 3BHE7tT0024981; Sun, 17 Dec 2023 09:07:55 -0500 (EST) From: Brad Spencer To: David Arnold In-Reply-To: <7AD36632-2B2F-43E2-999D-4F6373C3C64C@pobox.com> (message from David Arnold on Sun, 17 Dec 2023 16:55:37 +1100) Date: Sun, 17 Dec 2023 09:07:54 -0500 Message-ID: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.6.4 (anduin.eldar.org [0.0.0.0]); Sun, 17 Dec 2023 09:07:55 -0500 (EST) Message-ID-Hash: N5DPBP6RNSYGVZX7HNWI2NJQYJOIWY6F X-Message-ID-Hash: N5DPBP6RNSYGVZX7HNWI2NJQYJOIWY6F X-MailFrom: brad@anduin.eldar.org X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: tuhs@tuhs.org X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [TUHS] Re: Compatibility question List-Id: The Unix Heritage Society mailing list Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: David Arnold writes: > =EF=BB=BF >> On 17 Dec 2023, at 13:02, KenUnix wrote: > > -8<=E2=80=94 > >> 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. --=20 Brad Spencer - brad@anduin.eldar.org