The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Ralph Corderoy <ralph@inputplus.co.uk>
To: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] vi(1) in 10th Ed.  (Was: Vi Quick Reference card for 4.4 BSD)
Date: Tue, 04 Jun 2024 14:56:46 +0100	[thread overview]
Message-ID: <20240604135646.A1BB821EDB@orac.inputplus.co.uk> (raw)
In-Reply-To: <CAKH6PiWktD3WY7aiCgbs_nTNmC5BA3nGQF1KiUxk6hDOB9z8mw@mail.gmail.com>

Hi,

Doug wrote:
> It's not a card, but it's brief: vi(1) in the v10 manual covers vi,
> ex, and edit in three pages.

I went looking for it.  The source is
https://www.tuhs.org/cgi-bin/utree.pl?file=V10/man/man1/vi.1

The TUHS wiki,
https://wiki.tuhs.org/doku.php?id=publications:manuals:research#tenth_edition
links to a 10th Ed. PDF, but beware it isn't a scan of the manual.
Instead, as the blurb on scrolling down says, the man pages were
formatted with BSD's mandoc so not a lot of chance of the output
matching the original.

Page 389 of 992 is the start of vi(1).  The .2C two-column output
split by a tab character hasn't been honoured which is why it starts to
look garbled by the second page.

    .PP
    .de fq
    \&\f5\\$1\fR───→\\$2 \\$3 \\$4 \\$5 \\$6
    ..
    .de fz
    \&\f5\\$1 \fI\\$2\fR───→\\$3 \\$4 \\$5 \\$6
    ..
    .ta \w'\f5:e + file'u
    File manipulation
    .2C
    .fq :w write back changes
    .fz :w  file write \fIfile\fR
    .fz :w!  file overwrite \fIfile\fR

A scan of an authentic 10th Ed. manual would be handy.  If it already
exists, then the wiki would be better pointed at that.

-- 
Cheers, Ralph.

  reply	other threads:[~2024-06-04 13:56 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  4:31 [TUHS] Vi Quick Reference card for 4.4 BSD Will Senn
2024-06-04  4:46 ` [TUHS] " segaloco via TUHS
2024-06-04  5:47   ` segaloco via TUHS
2024-06-04 13:01     ` Douglas McIlroy
2024-06-04 13:56       ` Ralph Corderoy [this message]
2024-06-04 12:28   ` Matt Day
2024-06-04 13:06     ` Will Senn
2024-06-04 14:32 ` Clem Cole
2024-06-04 19:23   ` Matt Day
2024-06-04 14:42 ` Blake McBride

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=20240604135646.A1BB821EDB@orac.inputplus.co.uk \
    --to=ralph@inputplus.co.uk \
    --cc=tuhs@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).