The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Will Senn <will.senn@gmail.com>
To: Warner Losh <imp@bsdimp.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] vi on v7
Date: Wed, 5 Jan 2022 09:26:50 -0600	[thread overview]
Message-ID: <102db625-b2a0-935b-7424-a183ae64fb65@gmail.com> (raw)
In-Reply-To: <CANCZdfrCSE1nqEaV8AzjabrQxRRBUx9rL3JGbvEkEWxKsnh18w@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 3026 bytes --]

On 1/4/22 7:35 PM, Warner Losh wrote:
>
> 1. It's not going "full" screen, even with TERM=vt100 or TERM=ansi set 
> (not that I was surprised, but it'd be nice)...
>
> What does /etc/termcap look like?
>
All right, I'm getting warmer. I tried changing ttys to various speeds, 
and stty 9600, per Clem, Then, I looked at termcap, and saw that there 
weren't any ansi or vt100 entries (duh), so then I tryed vt50 and vt52 
modes:

vt50:

    HJ






       ~
       ~
       ~
       AAAA




           :q

vt52:

    Y7 HJY- ~
             ~
             ~
             ~
             ~
             ~
             ~
             ~
             ~
             ~Y, Y7 :q


Here are the termcap entries. I compared with termcap in svr2, which has 
vt50,vt52, and vt100:

v7:

    vh|vt50h|dec vt50h:\
    :bs:cd=\EJ:ce=\EK:cl=\EH\EJ:cm=\EY%+ %+ :co#80:li#12:nd=\EC:\
    :pt:sr=\EI:up=\EA:
    v2|vt52|dec vt52:\
    :bs:cd=\EJ:ce=\EK:cl=\EH\EJ:cm=\EY%+ %+ :co#80:li#24:nd=\EC:\
    :pt:sr=\EI:up=\EA:

svr2:

    d0|vt100|vt100-am|vt100|dec vt100:\
             :cr=^M:do=^J:nl=^J:bl=^G:co#80:li#24:cl=50\E[;H\E[2J:\
             :le=^H:bs:am:cm=5\E[%i%d;%dH:nd=2\E[C:up=2\E[A:\
    :ce=3\E[K:cd=50\E[J:so=2\E[7m:se=2\E[m:us=2\E[4m:ue=2\E[m:\
             :md=2\E[1m:mr=2\E[7m:mb=2\E[5m:me=2\E[m:is=\E[1;24r\E[24;1H:\
    :rs=\E>\E[?3l\E[?4l\E[?5l\E[?7h\E[?8h:ks=\E[?1h\E=:ke=\E[?1l\E>:\
    :rf=/usr/lib/tabset/vt100:ku=\EOA:kd=\EOB:kr=\EOC:kl=\EOD:kb=^H:\
    :ho=\E[H:k1=\EOP:k2=\EOQ:k3=\EOR:k4=\EOS:ta=^I:pt:sr=5\EM:vt#3:xn:\
             :sc=\E7:rc=\E8:cs=\E[%i%d;%dr:
    d1|vt100|vt100-nam|vt100 w/no am:\
             :am@:xn@:tc=vt100-am:
    d2|gt42|dec gt42:\
             :cr=^M:do=^J:bl=^G:\
             :le=^H:bs:co#72:ns:li#40:os:
    d3|vt132|vt132:\
    :al=99\E[L:dl=99\E[M:ip=7:dc=7\E[P:ei=\E[4l:im=\E[4h:xn:dN#30:tc=vt100:
    d4|gt40|dec gt40:\
             :cr=^M:do=^J:bl=^G:\
             :le=^H:bs:co#72:ns:li#30:os:
    d5|vt50|dec vt50:\
             :cr=^M:do=^J:nl=^J:bl=^G:\
    :le=^H:bs:cd=\EJ:ce=\EK:cl=\EH\EJ:co#80:li#12:nd=\EC:ta=^I:pt:up=\EA:

Here's the list of available terminals culled from /etc/termcap from v7 
and the buggy/untested list included in termcap:

    dumb, lsi adm3/adm3a/adm31/adm3a, concept100/concept100rv, hp2645,
    dm1520/dm2500/dm3025/3025a, dec gt40/gt42/vt50/vt50h/vt52, decwriter
    I/decwriter II, diablo 300s, hazeltine 1500/1510/2000, Infoton
    100/400/KAS, fox 1100, owl 1200, tektronix 4014, teleray 1061,
    terminet 1200/300, tty33/37/43, ti silent 700/745, xitex sct-100,
    beehiveIIIm, tvi912/tvi920, ttyWilliams, infoton|400|infoton 400

    buggy -dm2500
    Untested - gt40, gt42, vt50, vt50h, dw1, dtc300s, gsi, infoton, fox,
    tk4014, t1061, 1200, 300, tty33, tty37, tty43

I don't suppose any of these look like reasonable approximations of 
something I have available in Terminal/xterm?

Will

[-- Attachment #2: Type: text/html, Size: 5431 bytes --]

  parent reply	other threads:[~2022-01-05 15:27 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-05  0:32 Will Senn
2022-01-05  1:35 ` Warner Losh
2022-01-05  1:36   ` Warner Losh
2022-01-05 22:48     ` Will Senn
2022-01-05 15:26   ` Will Senn [this message]
2022-01-05 15:44     ` Clem Cole
2022-01-05 15:50       ` Clem Cole
2022-01-05 17:12         ` Grant Taylor via TUHS
2022-01-05 17:28           ` Clem Cole
2022-01-05 17:34     ` Phil Budne
2022-01-05 18:22       ` Will Senn
2022-01-05 19:02         ` Warner Losh
2022-01-05 20:13           ` Will Senn
2022-01-06  1:20       ` Humm
2022-01-05  1:40 ` Clem Cole
2022-01-06  2:18 ` Jeremy C. Reed

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=102db625-b2a0-935b-7424-a183ae64fb65@gmail.com \
    --to=will.senn@gmail.com \
    --cc=imp@bsdimp.com \
    --cc=tuhs@minnie.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).