The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Qed vs ed
Date: Sun, 31 Jan 2021 19:29:46 +1100	[thread overview]
Message-ID: <CAKzdPgxMiFVt5ejZm4-AHKEmqnimpZvqZXKy2afCsvkTOw0NXA@mail.gmail.com> (raw)
In-Reply-To: <7wh7mxpp4q.fsf@junk.nocrew.org>

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

The version of qed Leah refers to is not pure. It was created in the late
1970s by Tom Duff, Hugh Redelmeier, David Tilbrook and myself by hacking
the (already hacked) v6 ed we had at the University of Toronto, to restore
some of the programmability that had been removed when ed was created, and
to have fun. Mostly to have fun.

Tom Duff used a real QED (sic) on the GCOS at Waterloo and was a bit
conflicted about all this. For me the programmability was fun, and I wrote
the tutorial, but what ended up sticking with me was the ability to edit
multiple files simultaneously, something no other editor I had available
could do. I don't mean switching between files, I mean making things like
global substitutions across *.c. I'd start a session by typing qed *.[ch]
and go from there.

Our qed traveled with me from Caltech to Bell Labs, where I used it to
write jim, which I used to write sam, which I used to write Acme. I tried
vi when starting jim, but again the one file thing was too much to bear. I
also tried emacs, which could in principle handle multiple files but the
interface was cumbersome - it was much too hard to open a new file in a
subwindow - and without regular expressions I gave up after a day or two.
Also with a 2-d screen and a 1-d input device (no mouse), vi and emacs were
too remote, like giving directions to someone holding a map without being
able to point at the map. Describing where you want to point rather than
just pointing.

Anyway that was 40 or so years ago, and it's clear from the screens on
others' desks at work that my opinion on those matters is not widely shared.

I had a lot of fun hacking qed, mostly side-by-side with Tilbrook, who was
its biggest fan. He taught me a lot and I loved working with him.

-rob



On Sun, Jan 31, 2021 at 6:01 PM Lars Brinkhoff <lars@nocrew.org> wrote:

> Al Kossow wrote:
> > https://github.com/arnoldrobbins/qed-archive/tree/master/sds-940
> >
> > SDS 940 QED
> >
> > "These files were supplied to me by Lars Brinkhoff (lars AT
> > nocrew.org). I have no idea where he got them."
> >
> > Me, assuming he pulled them from the SDS940 tapes I recovered and are
> > on bitsavers
> >
> > The .pdf scans are from me, so I assume the code came from bitsavers as
> well.
>
> I got everything in a zip file from Mark Emmer when I asked him about QED.
>

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

  reply	other threads:[~2021-01-31  8:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-31  3:16 Will Senn
2021-01-31  3:48 ` Will Senn
2021-01-31  3:58   ` Will Senn
2021-01-31  4:07   ` Al Kossow
2021-01-31  7:00     ` Lars Brinkhoff
2021-01-31  8:29       ` Rob Pike [this message]
2021-01-31  9:28         ` Jaap Akkerhuis
2021-01-31 10:04     ` arnold

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=CAKzdPgxMiFVt5ejZm4-AHKEmqnimpZvqZXKy2afCsvkTOw0NXA@mail.gmail.com \
    --to=robpike@gmail.com \
    --cc=lars@nocrew.org \
    --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).