The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
* [TUHS] vi on v7
@ 2022-01-05  0:32 Will Senn
  2022-01-05  1:35 ` Warner Losh
                   ` (2 more replies)
  0 siblings, 3 replies; 16+ messages in thread
From: Will Senn @ 2022-01-05  0:32 UTC (permalink / raw)
  To: TUHS main list

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

Well, hallelujah, after much travail (I've tried this every Christmas 
for at least 5 years now), I have succeeded in building vi on v7 from 
2bsd. Had to patch the c compiler to enlarge the symbol table, tweak 
some stuff here and there, but it finally built and installed without 
any errors, yay.

Now, I just want it to do some editing, preferably in visual mode. I can 
call it as ex or vi:

# ex
:

or

# vi

:

and q will exit, yay, again!

I have at least two problems:
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)...
2. If I type a for append and type something, there's no way to get back 
to the : prompt (ESC doesn't seem to work).
3. I'd like manpages (figure they might help with the above), but 
they're on the tape as .u files?

I'm hoping this triggers some, oh yeah I remember that, type responses.

Thanks,

Will



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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05  0:32 [TUHS] vi on v7 Will Senn
@ 2022-01-05  1:35 ` Warner Losh
  2022-01-05  1:36   ` Warner Losh
  2022-01-05 15:26   ` Will Senn
  2022-01-05  1:40 ` Clem Cole
  2022-01-06  2:18 ` Jeremy C. Reed
  2 siblings, 2 replies; 16+ messages in thread
From: Warner Losh @ 2022-01-05  1:35 UTC (permalink / raw)
  To: Will Senn; +Cc: TUHS main list

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

On Tue, Jan 4, 2022 at 5:33 PM Will Senn <will.senn@gmail.com> wrote:

> Well, hallelujah, after much travail (I've tried this every Christmas for
> at least 5 years now), I have succeeded in building vi on v7 from 2bsd. Had
> to patch the c compiler to enlarge the symbol table, tweak some stuff here
> and there, but it finally built and installed without any errors, yay.
>
> Now, I just want it to do some editing, preferably in visual mode. I can
> call it as ex or vi:
>
> # ex
> :
>
> or
>
> # vi
>
> :
>
> and q will exit, yay, again!
>
> I have at least two problems:
> 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?


> 2. If I type a for append and type something, there's no way to get back
> to the : prompt (ESC doesn't seem to work).
> 3. I'd like manpages (figure they might help with the above), but they're
> on the tape as .u files?
>
> I'm hoping this triggers some, oh yeah I remember that, type responses.
>
> Thanks,
>
> Will
>
>
>
>

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  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
  1 sibling, 1 reply; 16+ messages in thread
From: Warner Losh @ 2022-01-05  1:36 UTC (permalink / raw)
  To: Will Senn; +Cc: TUHS main list

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

On Tue, Jan 4, 2022 at 6:35 PM Warner Losh <imp@bsdimp.com> wrote:

>
>
> On Tue, Jan 4, 2022 at 5:33 PM Will Senn <will.senn@gmail.com> wrote:
>
>> Well, hallelujah, after much travail (I've tried this every Christmas for
>> at least 5 years now), I have succeeded in building vi on v7 from 2bsd. Had
>> to patch the c compiler to enlarge the symbol table, tweak some stuff here
>> and there, but it finally built and installed without any errors, yay.
>>
>> Now, I just want it to do some editing, preferably in visual mode. I can
>> call it as ex or vi:
>>
>> # ex
>> :
>>
>> or
>>
>> # vi
>>
>> :
>>
>> and q will exit, yay, again!
>>
>> I have at least two problems:
>> 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?
>

Doh! Hit send too fast


> 2. If I type a for append and type something, there's no way to get back
>> to the : prompt (ESC doesn't seem to work).
>>
>
Sounds like the timeout code for the terminal input isn't working (it's
what it uses to tell a ESC from a ESC [ A for example.


> 3. I'd like manpages (figure they might help with the above), but they're
>> on the tape as .u files?
>>
>
No clue there. Are the .u files nroff by chance?

Warner


> I'm hoping this triggers some, oh yeah I remember that, type responses.
>>
>> Thanks,
>>
>> Will
>>
>>
>>
>>

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05  0:32 [TUHS] vi on v7 Will Senn
  2022-01-05  1:35 ` Warner Losh
@ 2022-01-05  1:40 ` Clem Cole
  2022-01-06  2:18 ` Jeremy C. Reed
  2 siblings, 0 replies; 16+ messages in thread
From: Clem Cole @ 2022-01-05  1:40 UTC (permalink / raw)
  To: Will Senn; +Cc: TUHS main list

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

Ah. You discovered a feature of vi fir
Dialup terminals.  When the baud rate is 120cps or less then it will only
paint ½ the screen at a time.    Reset Getty to use the 960cps interface
and magically that will go away

On Tue, Jan 4, 2022 at 7:33 PM Will Senn <will.senn@gmail.com> wrote:

> Well, hallelujah, after much travail (I've tried this every Christmas for
> at least 5 years now), I have succeeded in building vi on v7 from 2bsd. Had
> to patch the c compiler to enlarge the symbol table, tweak some stuff here
> and there, but it finally built and installed without any errors, yay.
>
> Now, I just want it to do some editing, preferably in visual mode. I can
> call it as ex or vi:
>
> # ex
> :
>
> or
>
> # vi
>
> :
>
> and q will exit, yay, again!
>
> I have at least two problems:
> 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)...
> 2. If I type a for append and type something, there's no way to get back
> to the : prompt (ESC doesn't seem to work).
> 3. I'd like manpages (figure they might help with the above), but they're
> on the tape as .u files?
>
> I'm hoping this triggers some, oh yeah I remember that, type responses.
>
> Thanks,
>
> Will
>
>
>
> --
Sent from a handheld expect more typos than usual

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05  1:35 ` Warner Losh
  2022-01-05  1:36   ` Warner Losh
@ 2022-01-05 15:26   ` Will Senn
  2022-01-05 15:44     ` Clem Cole
  2022-01-05 17:34     ` Phil Budne
  1 sibling, 2 replies; 16+ messages in thread
From: Will Senn @ 2022-01-05 15:26 UTC (permalink / raw)
  To: Warner Losh; +Cc: TUHS main list

[-- 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 --]

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05 15:26   ` Will Senn
@ 2022-01-05 15:44     ` Clem Cole
  2022-01-05 15:50       ` Clem Cole
  2022-01-05 17:34     ` Phil Budne
  1 sibling, 1 reply; 16+ messages in thread
From: Clem Cole @ 2022-01-05 15:44 UTC (permalink / raw)
  To: Will Senn; +Cc: TUHS main list

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

Just add the vt100 entry from 4.1 you might be fine.  FYI:To there credit,
when the VT-100 was being developed the spec was a moving target and Tom
Kent and his brothers and sisters in the terminal group did an amazing job
-- but ....  VT-100 are not completely ANSI (DEC released before the spec
was ratified smd it lacks some features that are really needed).   It uses
scrolling regions to do some of the painting/update -- Mary Ann
undoubtedly has nightmares.

The termcap code in 2BSD is very early and may not be smart enough to do
some of the tricks that VT-100 demanded, so it might be wise to swipe the
4.1/4.2 version and see if you can substitute.   Also remember Sys V used
*terminfo* [again Maryann can explain having fought that war].   Termcap
was included in later versions by demand.

On Wed, Jan 5, 2022 at 10:28 AM Will Senn <will.senn@gmail.com> wrote:

> 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: 6831 bytes --]

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05 15:44     ` Clem Cole
@ 2022-01-05 15:50       ` Clem Cole
  2022-01-05 17:12         ` Grant Taylor via TUHS
  0 siblings, 1 reply; 16+ messages in thread
From: Clem Cole @ 2022-01-05 15:50 UTC (permalink / raw)
  To: Will Senn; +Cc: TUHS main list

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

FWIW: Since I know you are on a Mac - there are couple of retro style
terminal emulators, that may be able to be configured to be VT52 or one of
the others from that time.   One is call Cathode which I think cost a few
$s and there is a free one called Cool-Retro-Term (
https://github.com/Swordfish90/cool-retro-term)

On Wed, Jan 5, 2022 at 10:44 AM Clem Cole <clemc@ccc.com> wrote:

> Just add the vt100 entry from 4.1 you might be fine.  FYI:To there credit,
> when the VT-100 was being developed the spec was a moving target and Tom
> Kent and his brothers and sisters in the terminal group did an amazing job
> -- but ....  VT-100 are not completely ANSI (DEC released before the spec
> was ratified smd it lacks some features that are really needed).   It uses
> scrolling regions to do some of the painting/update -- Mary Ann
> undoubtedly has nightmares.
>
> The termcap code in 2BSD is very early and may not be smart enough to do
> some of the tricks that VT-100 demanded, so it might be wise to swipe the
> 4.1/4.2 version and see if you can substitute.   Also remember Sys V used
> *terminfo* [again Maryann can explain having fought that war].   Termcap
> was included in later versions by demand.
>
> On Wed, Jan 5, 2022 at 10:28 AM Will Senn <will.senn@gmail.com> wrote:
>
>> 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: 7653 bytes --]

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05 15:50       ` Clem Cole
@ 2022-01-05 17:12         ` Grant Taylor via TUHS
  2022-01-05 17:28           ` Clem Cole
  0 siblings, 1 reply; 16+ messages in thread
From: Grant Taylor via TUHS @ 2022-01-05 17:12 UTC (permalink / raw)
  To: tuhs

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

On 1/5/22 8:50 AM, Clem Cole wrote:
> One is call Cathode which I think cost a few $s

Is Cathode still a thing?

I just quickly searched for it in the App Store and didn't find it.

I seem to recall reading that it had been discontinued O(few years) ago.

I'd appreciate learning that it's simply me looking in the wrong place.



-- 
Grant. . . .
unix || die


[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4017 bytes --]

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05 17:12         ` Grant Taylor via TUHS
@ 2022-01-05 17:28           ` Clem Cole
  0 siblings, 0 replies; 16+ messages in thread
From: Clem Cole @ 2022-01-05 17:28 UTC (permalink / raw)
  To: Grant Taylor; +Cc: tuhs

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

On Wed, Jan 5, 2022 at 12:12 PM Grant Taylor via TUHS <tuhs@minnie.tuhs.org>
wrote:

> On 1/5/22 8:50 AM, Clem Cole wrote:
> > One is call Cathode which I think cost a few $s
>
> Is Cathode still a thing?
>
Sort of...

>
> I just quickly searched for it in the App Store and didn't find it.
>
https://www.macupdate.com/app/mac/36568/cathode


>
> I seem to recall reading that it had been discontinued O(few years) ago.
>
Yes..

>
> I'd appreciate learning that it's simply me looking in the wrong place.
>
>

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05 15:26   ` Will Senn
  2022-01-05 15:44     ` Clem Cole
@ 2022-01-05 17:34     ` Phil Budne
  2022-01-05 18:22       ` Will Senn
  2022-01-06  1:20       ` Humm
  1 sibling, 2 replies; 16+ messages in thread
From: Phil Budne @ 2022-01-05 17:34 UTC (permalink / raw)
  To: will.senn; +Cc: tuhs

Will Senn wrote:
> so then I tryed vt50 and vt52 modes...

xterm should have VT52 emulation, at least the man page on my system says:
>        o   VT52 emulation is complete.

But looking at CTRL+{LEFT,MIDDLE,RIGHT}_CLICK menus didn't show a toggle.

The VT100 sequence to enter VT52 mode seems to be <ESC>[?2l
you should be able to send it with echo.

Then <ESC>H<ESC>J should clear the screen.

NOTE! The ANSI command prefix <ESC>[ will put a real VT52 into "hold
screen" mode where you need to press some (scroll?) button to allow
new lines to be added at the bottom of the screen.  Ask me how I know!

phil

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05 17:34     ` Phil Budne
@ 2022-01-05 18:22       ` Will Senn
  2022-01-05 19:02         ` Warner Losh
  2022-01-06  1:20       ` Humm
  1 sibling, 1 reply; 16+ messages in thread
From: Will Senn @ 2022-01-05 18:22 UTC (permalink / raw)
  To: Phil Budne; +Cc: tuhs

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

On 1/5/22 11:34 AM, Phil Budne wrote:
> Will Senn wrote:
>> so then I tryed vt50 and vt52 modes...
> xterm should have VT52 emulation, at least the man page on my system says:
>>         o   VT52 emulation is complete.
> But looking at CTRL+{LEFT,MIDDLE,RIGHT}_CLICK menus didn't show a toggle.
>
> The VT100 sequence to enter VT52 mode seems to be <ESC>[?2l
> you should be able to send it with echo.
>
> Then <ESC>H<ESC>J should clear the screen.
>
> NOTE! The ANSI command prefix <ESC>[ will put a real VT52 into "hold
> screen" mode where you need to press some (scroll?) button to allow
> new lines to be added at the bottom of the screen.  Ask me how I know!
>
> phil
Well, is there no end to fascination... That 'worked' in that I was able 
to do this in n xterm on my mac:

    printf "\033[?2l"


which changed the size of the xterm window to 80 chars wide... then:

    printf "\033H\033J"


which cleared the screen as you said it would.

But, then, I telnet'd into the the v7 instance and set TERM=vt52, etc.

Now vi gives this:

    Y7 HJY- ~
             ~
             ~
             ~
             ~
             ~
             ~
             ~
             ~
             ~Y,


However, I should note that v7 doesn't seem to process escape sequences, 
either with a pristine instance or my fully configured instance...

    echo '\033'
    \033

    $ ed test
    ?test
    a
    <ESC>J (just echoes the J)
    .
    w
    3
    q
    $ od -c test
    0000000 033   J  \n  \0
    0000003

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05 18:22       ` Will Senn
@ 2022-01-05 19:02         ` Warner Losh
  2022-01-05 20:13           ` Will Senn
  0 siblings, 1 reply; 16+ messages in thread
From: Warner Losh @ 2022-01-05 19:02 UTC (permalink / raw)
  To: Will Senn; +Cc: TUHS main list

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

On Wed, Jan 5, 2022 at 11:23 AM Will Senn <will.senn@gmail.com> wrote:

> On 1/5/22 11:34 AM, Phil Budne wrote:
>
> Will Senn wrote:
>
> so then I tryed vt50 and vt52 modes...
>
> xterm should have VT52 emulation, at least the man page on my system says:
>
>        o   VT52 emulation is complete.
>
> But looking at CTRL+{LEFT,MIDDLE,RIGHT}_CLICK menus didn't show a toggle.
>
> The VT100 sequence to enter VT52 mode seems to be <ESC>[?2l
> you should be able to send it with echo.
>
> Then <ESC>H<ESC>J should clear the screen.
>
> NOTE! The ANSI command prefix <ESC>[ will put a real VT52 into "hold
> screen" mode where you need to press some (scroll?) button to allow
> new lines to be added at the bottom of the screen.  Ask me how I know!
>
> phil
>
> Well, is there no end to fascination... That 'worked' in that I was able
> to do this in n xterm on my mac:
>
> printf "\033[?2l"
>
>
> which changed the size of the xterm window to 80 chars wide... then:
>
> printf "\033H\033J"
>
>
> which cleared the screen as you said it would.
>
> But, then, I telnet'd into the the v7 instance and set TERM=vt52, etc.
>
> Now vi gives this:
>
> Y7 HJY- ~
>         ~
>         ~
>         ~
>         ~
>         ~
>         ~
>         ~
>         ~
>         ~Y,
>
>
> However, I should note that v7 doesn't seem to process escape sequences,
> either with a pristine instance or my fully configured instance...
>
> echo '\033'
> \033
>
> This is why I suggested using printf direct in C :)

$ ed test
> ?test
> a
> <ESC>J (just echoes the J)
> .
> w
> 3
> q
> $ od -c test
> 0000000 033   J  \n  \0
> 0000003
>
> There's escape problems :(.  I'll see if I can spin up a V7 box and see if
I have any suggestions.

Warner

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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05 19:02         ` Warner Losh
@ 2022-01-05 20:13           ` Will Senn
  0 siblings, 0 replies; 16+ messages in thread
From: Will Senn @ 2022-01-05 20:13 UTC (permalink / raw)
  To: Warner Losh; +Cc: TUHS main list

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


> There's escape problems :(.  I'll see if I can spin up a V7 box and 
> see if I have any suggestions.
>
> Warner

OK. Here's the update. I set tto 7b in SimH (which is bad?) and ESC 
works. Then in vi, it only uses half the screen. Per Clem's suggestion, 
I ran stty 9600, and voila, it "worked" full screen. Yay!

Now, it's just a matter of getting ex/vi working properly as an editor. 
I can confuse it pretty easy once it's up and running. Either this 
version of vi's got some pretty awful bugs, or I screwed up the build, 
but at least the screen's cooperating better now.

So, is 7b bad and should I be looking for another solution?

Will



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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05  1:36   ` Warner Losh
@ 2022-01-05 22:48     ` Will Senn
  0 siblings, 0 replies; 16+ messages in thread
From: Will Senn @ 2022-01-05 22:48 UTC (permalink / raw)
  To: Warner Losh; +Cc: TUHS main list

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

On 1/4/22 7:36 PM, Warner Losh wrote:
>
>         3. I'd like manpages (figure they might help with the above),
>         but they're on the tape as .u files?
>
>
> No clue there. Are the .u files nroff by chance?
>
>

I figured out the manpages. Just need to copy the tmac files from 2bsd 
into /usr/lib, then copy the *.u files into /usr/man/manu, then:

    man vi
    VI(UCB)             UNIX Programmer's Manual VI(UCB)



    NAME
          vi - screen oriented (visual) display editor based on ex
    ...
    Printed 1/1/70               4/4/79 2

The .u suffix was another duh moment. .u for UCB...

Will


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

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05 17:34     ` Phil Budne
  2022-01-05 18:22       ` Will Senn
@ 2022-01-06  1:20       ` Humm
  1 sibling, 0 replies; 16+ messages in thread
From: Humm @ 2022-01-06  1:20 UTC (permalink / raw)
  To: Phil Budne; +Cc: tuhs

Quoth Phil Budne:
>NOTE! The ANSI command prefix <ESC>[ will put a real VT52 into "hold
>screen" mode where you need to press some (scroll?) button to allow
>new lines to be added at the bottom of the screen.  Ask me how I know!

How do you know?

-- 
Humm

^ permalink raw reply	[flat|nested] 16+ messages in thread

* Re: [TUHS] vi on v7
  2022-01-05  0:32 [TUHS] vi on v7 Will Senn
  2022-01-05  1:35 ` Warner Losh
  2022-01-05  1:40 ` Clem Cole
@ 2022-01-06  2:18 ` Jeremy C. Reed
  2 siblings, 0 replies; 16+ messages in thread
From: Jeremy C. Reed @ 2022-01-06  2:18 UTC (permalink / raw)
  To: Will Senn; +Cc: TUHS main list

I don't know if is applicable, but
2bsd's doc/vi/vi.in says the vt52 is "Dumb"
Maybe try an "Intelligent" choice listed there.
Also see:
     The editor can simulate an intelligent  terminal  on  a
dumb one.  Try giving the command :se redrawESC

^ permalink raw reply	[flat|nested] 16+ messages in thread

end of thread, other threads:[~2022-01-06  2:56 UTC | newest]

Thread overview: 16+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-05  0:32 [TUHS] vi on v7 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
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

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).