The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: segaloco via TUHS <tuhs@tuhs.org>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: Vi Quick Reference card for 4.4 BSD
Date: Tue, 04 Jun 2024 04:46:01 +0000	[thread overview]
Message-ID: <4YcO7QxSRsr-EFfdZcWDr8bsnSJkpl8bgWhtvn4PYDYO1UzTHdpwYOvQXue_O3X319Nt1AY9BAyvMLbM7v0E0HJEnnN_JIgrgmRu5pC1ygA=@protonmail.com> (raw)
In-Reply-To: <dcc7d835-5c3a-44c1-855c-72c2301b6cc0@gmail.com>

On Monday, June 3rd, 2024 at 9:31 PM, Will Senn <will.senn@gmail.com> wrote:

> Today after trying to decipher the online help for vim and neovim, I decided I'd had enough and I opted for nvi - the bug for bug vi compatible that I've used for so long on FreeBSD. It handles cursor keys, these days (my biggest gripe back when, now I'm not so sure it's an improvement). It's in-app help pages are about 300 lines long, the docs are just four of the 4.4 docs: An Introduction to Display Editing with VI, Edit: A tutorial, EX Reference Manual, and VI-EX Reference Manual - all very well written and understandable. It does everything I really need it to do without the million and one extensions and "enhancements" the others offer.
> 
> In doing the docs research, I found many, many references to a "Vi Quick Reference card" in the various manpages and docs. I googled and googled some more and of course got thousands of hits (really many thousands), but I can't seem to find the actual card referenced. I'm pretty sure what I want to find is a scanned image or pdf of the card for 4.4bsd.
> 
> Do y'all happen to know of where I might find the golden quick ref card for vi from back in the 4.4bsd days or did it even really exist?
> 
> Will

Perhaps this?  https://imgur.com/a/unix-vi-quick-reference-Nw0sfTH

Pardon the quality and host, not in a place to do a more thoughtful scan and archival right now.  That was in a stack of documents I received some time ago, thrown in with stuff like V6 and KSOS manuals, some BSD docs, etc. so I presume it's also "official" fare.  That and no commercial indicators (TMs, copyrights, etc.)

Let me know if that link doesn't work and I'll try and find my scanner and do it properly (scanner is MIA apparently...)

- Matt G.

P.S. I also have the AT&T branded version of this from 1984, it's a small 22 page flipbook with the same cover motif as early SVR2 binders (so the grey with some "deathstar" lines not the red with black accent dots).  Once I find my scanner I'll get that on the glass.

  reply	other threads:[~2024-06-04  4:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-04  4:31 [TUHS] " Will Senn
2024-06-04  4:46 ` segaloco via TUHS [this message]
2024-06-04  5:47   ` [TUHS] " segaloco via TUHS
2024-06-04 13:01     ` Douglas McIlroy
2024-06-04 13:56       ` [TUHS] vi(1) in 10th Ed. (Was: Vi Quick Reference card for 4.4 BSD) Ralph Corderoy
2024-06-04 12:28   ` [TUHS] Re: Vi Quick Reference card for 4.4 BSD 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='4YcO7QxSRsr-EFfdZcWDr8bsnSJkpl8bgWhtvn4PYDYO1UzTHdpwYOvQXue_O3X319Nt1AY9BAyvMLbM7v0E0HJEnnN_JIgrgmRu5pC1ygA=@protonmail.com' \
    --to=tuhs@tuhs.org \
    --cc=segaloco@protonmail.com \
    --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).