From: Lawrence Stewart <stewart@serissa.com>
To: TUHS@tuhs.org
Subject: [TUHS] Old screen editors
Date: Mon, 28 Mar 2022 20:31:14 -0400 [thread overview]
Message-ID: <11FBF445-4956-427E-8751-60BF5CA88116@serissa.com> (raw)
In-Reply-To: <19FC5DAF-A4C7-4EE0-BF34-91B340910641@iitbombay.org>
At the Stanford Information Systems Lab while I was there 1976-81, we had a series of PDP-11s. The first one I remember was an 11/34 running V6 and later V7. It was later upgraded to, I think a /45 and finally a /70.
At first everyone used ed, then Prof. John Gill hacked it to add a command, I think ‘%’ that was the equivalent of .-10,.+10p which on our 9600 baud Hazeltine’s was a glimpse of the future.
At some point we got ex/vi, but before that we got the “Rand Editor” re, which was a perfectly
functional screen editor, if you squinted a bit.
Does anyone here know the place of re in the history?
Later, Gill went off for a sabbatical at Yorktown Heights and came back to complain about having
to use SOS on the mainframe. He reported, however, that global search and replace was very fast.
-L
Also a few years later I got Dave Conroy’s version of microemacs. I complained about the key bindings and he told me to use the “change configuration” command, or cc.
next prev parent reply other threads:[~2022-03-29 0:41 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-28 21:03 [TUHS] Alive? Warren Toomey via TUHS
2022-03-28 21:17 ` Hellwig Geisse
2022-03-28 21:21 ` Steve Nickolas
2022-03-28 21:27 ` Charles H Sauer (he/him)
2022-03-28 21:29 ` Larry McVoy
2022-03-29 1:14 ` Chet Ramey
2022-03-28 21:43 ` Dave Horsfall
2022-03-28 22:24 ` Bakul Shah
2022-03-28 23:23 ` Greg 'groggy' Lehey
2022-03-28 23:29 ` Andrew Hume
2022-03-28 23:56 ` George Michaelson
2022-03-29 0:00 ` Bakul Shah
2022-03-29 0:31 ` Greg 'groggy' Lehey
2022-03-29 0:31 ` Lawrence Stewart [this message]
2022-03-29 0:53 ` [TUHS] Old screen editors Charles H Sauer (he/him)
2022-03-29 8:29 ` Rob Pike
2022-03-29 13:24 ` Clem Cole
2022-03-29 8:34 ` George Michaelson
2022-03-29 8:40 ` arnold
2022-03-29 13:45 ` Clem Cole
2022-03-29 14:31 ` Andrew Hume
2022-03-29 14:35 ` arnold
2022-03-29 14:42 ` Andrew Hume
2022-03-30 0:59 ` Mary Ann Horton
2022-03-30 5:11 ` arnold
2022-03-29 12:45 ` Thomas Paulsen
2022-03-29 13:26 ` arnold
2022-03-30 8:37 ` Ralph Corderoy
2022-03-29 1:10 ` [TUHS] Alive? Steve Nickolas
2022-03-29 6:37 ` Henry Mensch
2022-03-29 20:46 ` Dave Horsfall
2022-03-29 21:53 ` John Cowan
2022-03-29 10:39 [TUHS] Old screen editors Noel Chiappa
2022-03-29 11:05 ` Rob Pike
2022-03-29 13:37 ` Clem Cole
2022-03-29 15:43 ` Angelo Papenhoff
2022-03-30 5:36 ` Lars Brinkhoff
2022-03-29 18:35 Noel Chiappa
2022-03-29 19:09 Steve Simon
2022-03-29 21:46 ` Ron Natalie
2022-03-30 0:22 ` Tom Lyon via TUHS
2022-03-29 20:40 Noel Chiappa
2022-03-29 20:50 ` Phil Budne
2022-03-29 20:54 ` Ron Natalie
2022-03-30 5:41 ` Lars Brinkhoff
2022-03-30 7:50 ` Thomas Paulsen
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=11FBF445-4956-427E-8751-60BF5CA88116@serissa.com \
--to=stewart@serissa.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).