The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Warner Losh <imp@bsdimp.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] vi on v7
Date: Tue, 4 Jan 2022 18:36:35 -0700	[thread overview]
Message-ID: <CANCZdfq8pq8L7NZRd-Z+qUTFqVZi47hRyZb4wSqH3HVCoYfC+w@mail.gmail.com> (raw)
In-Reply-To: <CANCZdfrCSE1nqEaV8AzjabrQxRRBUx9rL3JGbvEkEWxKsnh18w@mail.gmail.com>

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

  reply	other threads:[~2022-01-05  1:37 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 [this message]
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

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=CANCZdfq8pq8L7NZRd-Z+qUTFqVZi47hRyZb4wSqH3HVCoYfC+w@mail.gmail.com \
    --to=imp@bsdimp.com \
    --cc=tuhs@minnie.tuhs.org \
    --cc=will.senn@gmail.com \
    /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).