The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <>
To: Leah Neukirchen <>
Subject: [TUHS] Re: Early Unix and Keyboard Skills
Date: Sun, 6 Aug 2023 12:31:51 -0400	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

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

On Sun, Aug 6, 2023 at 10:51 AM Leah Neukirchen <> wrote:

> Vim was based on Stevie, an Atari ST vi clone he ported to the Amiga 2000.
Thank you. I also remember stevie and that stevie beget vim make so much
sense.   It was one of the clones I ran back in the day.

The point is that there were (are) a number of vi clones.   Which is why I
started to switch to it.  It ran on everything from small 8-bit systems on
up.   Particularly on the micros, they all had something akin to what
Microsoft called edlin, often just called edit.  If you knew UNIX ed(1) or
any other editor from the old GED family from the 1960s, chances were you
could make it do something -- but it was PITA as each was a bit different
 So copies of the editors from the larger [often DEC based systems] started
to appear on the smaller and smaller machines.

And vi seemed to be a pretty popular as a starting point[I always suspect
Webb Miller's book had something to do with that since 's' was so small and
using it to add  missing vi features was not terrible].  That said, there
was an IBM PC/386 "MS-DOS" version of vi that required ANSI.SYS that was on
the market for about $50-$100.  It was 'bug for bug' compatible with Joy's
version.  I always suspected that unlike Keith, they just took the Vax
code, stripped out termcap so it did not need an external terminal
database, hard coded it for ANSI.SYS, then ran it through the PHARLAP C/386
subsystem.  Unlike any of the other 'clones' until nvi -- it was the only
one that had some of the same wonkiness.

As I understand it from him, Keith did nvi(1) because Joy's original work
was based on the v6 ed(1).  As part of Keith's effort to try to remove any
core code in the BSD releases that had any AT&T source taint, it was just
easier to start over.  The Berkeley Shell [in 1BSD] beget the C Shell, was
derived from Ken's sh in v5 and v6.   I think Keith/Kirk et al felt
that any of Ken's original code had long been removed - whereas ex(1) (vi
is the actually the VIsual command for ex) probably had a lot of core ed(1).


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

  parent reply	other threads:[~2023-08-06 16:32 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-02  2:36 [TUHS] " steve jenkin
2022-11-02  6:53 ` [TUHS] " Michael Kjörling
2022-11-02  7:11   ` Rob Pike
2022-11-02 13:28     ` Clem Cole
2022-11-03 21:51     ` Stuff Received
2023-08-05 23:53     ` scj
2023-08-06  0:22       ` KenUnix
2023-08-06  0:43         ` Larry McVoy
2023-08-06 14:51           ` Leah Neukirchen
2023-08-06 15:01             ` Larry McVoy
2023-08-06 16:31             ` Clem Cole [this message]
2023-08-06 18:20               ` Jon Forrest
2023-08-07  4:56                 ` Adam Thornton
2023-08-06  8:37       ` Ronald Natalie
2022-11-02 12:13 ` Steffen Nurpmeso
2022-11-02 12:24   ` Steffen Nurpmeso
2022-11-02 20:35     ` Ron Natalie
2022-11-02 12:26   ` John P. Linderman
2022-11-02 13:07     ` Larry Stewart
2022-11-02 13:16       ` Larry McVoy
2022-11-02 13:27     ` Steffen Nurpmeso
2022-11-02 19:01 ` jason-tuhs
2022-11-02 19:20   ` John P. Linderman
2022-11-03  1:47     ` Ronald Natalie
2022-11-03  1:59       ` Dave Horsfall
2022-11-03  3:01       ` Clem Cole
2022-11-03 15:17       ` Paul Winalski
2022-11-03 16:18         ` Clem Cole
2022-11-03 17:02         ` John Cowan
2022-11-03 19:36           ` Rich Morin
2022-11-03 20:01             ` Charles H Sauer (he/him)
2022-11-02 12:16 Douglas McIlroy

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \

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