The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Bakul Shah <bakul@iitbombay.org>
To: Rich Salz <rich.salz@gmail.com>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: [TUHS] Re: vi in cooked mode?
Date: Fri, 4 Nov 2022 20:44:22 -0700	[thread overview]
Message-ID: <D378B970-00A7-4881-9D4F-CD643F52FA12@iitbombay.org> (raw)
In-Reply-To: <CAFH29tpWDn9yG9=vqM2eLkqYQ7h5BuFNsOv1iUjooLAw-Jpb_Q@mail.gmail.com>

Wordstar came out in 1978, BDS C in 1979. MINCE was written in BDS C
so it probably didn't come with BDS C (but BDS C came with MINCE)!

In 1981/82 I ported Gosling Emacs to the Fortune box. It was slow
as molasses. My memory is that was due to it using bitfields, for
which our C compiler produced pretty bad code. But I didn't really
investigate it in any detail. In contrast vi & e (Rand editor as
further hacked on by Dave Yost) were so much better, especially on
a 60 line Ann Arbor Ambassador. 

> On Nov 4, 2022, at 7:31 PM, Rich Salz <rich.salz@gmail.com> wrote:
> 
> I don't recall BDS C having an editor but I could be wrong. They pushed Mark of the Unicorn's MINCE (mince is not complete emacs) and scribble, a scribe mini-clone. BDS was a one man shop, it stood for brain-damaged software.
> 
> On Fri, Nov 4, 2022, 9:40 PM Larry McVoy <lm@mcvoy.com> wrote:
> On Fri, Nov 04, 2022 at 06:25:03PM -0700, Bakul Shah wrote:
> > On Nov 4, 2022, at 6:02 PM, Larry McVoy <lm@mcvoy.com> wrote:
> > > 
> > > I also got a little corrupted by whatever editor came with BDS C
> > 
> > I think that was wordstar. I had to retrain my fingers when I
> > switched to vi! I used SOS, edt(?) on Tops-10, edit(?) on CMS,
> > teco (on ITS), wordstar (on CP/M), ed, vi, rand editor, acme.
> > Now I stick to nvi & acme. And cat for small programs/files.
> 
> I used wordstar but I think BDS C had their own thing.  Wordstar 
> was different.
> -- 
> ---
> Larry McVoy           Retired to fishing          http://www.mcvoy.com/lm/boat


  reply	other threads:[~2022-11-05  3:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-03 19:43 [TUHS] " Diomidis Spinellis
2022-11-03 20:26 ` [TUHS] " Clem Cole
2022-11-03 20:27   ` Clem Cole
2022-11-03 20:55   ` Warner Losh
2022-11-03 21:34     ` Clem Cole
2022-11-03 22:28       ` Warner Losh
2022-11-03 22:52         ` Ron Natalie
2022-11-04  6:43       ` Lars Brinkhoff
2022-11-04 15:18         ` Dan Cross
2022-11-04 17:54           ` Lars Brinkhoff
2022-11-04 18:33   ` Ron Natalie
2022-11-04 23:42     ` Theodore Ts'o
2022-11-05  0:45       ` Dave Horsfall
2022-11-05  1:02         ` Larry McVoy
2022-11-05  1:25           ` Bakul Shah
2022-11-05  1:40             ` Larry McVoy
2022-11-05  2:31               ` Rich Salz
2022-11-05  3:44                 ` Bakul Shah [this message]
2022-11-05 18:34               ` Theodore Ts'o
2022-11-05  9:29           ` Otto Moerbeek via TUHS
2022-11-04 22:13 ` Mary Ann Horton
2022-11-03 20:17 Noel Chiappa

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=D378B970-00A7-4881-9D4F-CD643F52FA12@iitbombay.org \
    --to=bakul@iitbombay.org \
    --cc=rich.salz@gmail.com \
    --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).