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 16:48:25 -0600	[thread overview]
Message-ID: <b809509d-078d-6052-e67a-53bea7528aaa@gmail.com> (raw)
In-Reply-To: <CANCZdfq8pq8L7NZRd-Z+qUTFqVZi47hRyZb4wSqH3HVCoYfC+w@mail.gmail.com>

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

  reply	other threads:[~2022-01-05 22:49 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 [this message]
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=b809509d-078d-6052-e67a-53bea7528aaa@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).