The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: norman@oclsc.org (Norman Wilson)
To: tuhs@tuhs.org
Subject: Re: [TUHS] Remember the ed thread?
Date: Mon, 29 Mar 2021 11:58:12 -0400 (EDT)	[thread overview]
Message-ID: <20210329155812.C66DF640CB6@lignose.oclsc.org> (raw)

ed is the standard editor, they say.

The b command (stands for browse) came from late-1970s
U of T; rob probably brought it to 1127.  There were a
handful of other syntactic conveniences, like being
allowed to leave off the final delimeter of an s command,
and declaring that a missing address means 1 before the
comma or semicolon and $ after, so
	3,s/fish/&head
works over all lines from 3 to the last, and , standing
alone addresses the whole buffer.

Also the idea that s followed by a digit N means start
with the Nth instance of the pattern:
	s3/fish/&head/
affects only the third fish, and
	s3/fish/&head/g
every fish after the second.

I have all those tweaks, plus a few others, embedded in
my fingers from the qed produced by the same Toronto
hacks.  I contracted it from the copy rob left behind
at Caltech, which means it has been my editor of choice
for 40 years now (with sam as an alternate favourite
since its inception 35 years or so ago).  That qed
has a lot of cryptic programming stuff that I have
mostly forgotten because it was never that useful, but
what really hooked me was
a.  Multiple buffers, with the ability to move and
copy text between them reasonably smoothly (both with
the m and t commands and with an interpolate-into-input
magic character);
b.  The > < | commands, which respectively send the
addressed lines to a shell command (default ,), replace
the addressed lines or append after the single addressed
line the standard output of the shell command (default .),
and replaced addressed lines with what you get by
sending them (default ,) to the shell command, replacing
them with its standard output.

The last operators make qed into a kind of workbench,
both for massaging data and for constructing a list
of commands to send to the shell.

I gather current Linux/BSD eds have > and <, spelled
r ! and w !, but without | it just ain't the same,
rather like the way | revolutionized the shell.

I believe the credit for U of T ed and qed go mainly
to Rob Pike, Tom Duff, Hugh Redelmeier, and the (alas
now late) David Tillbrook.  David remained an avid
user of qed, continuing to add stuff to it.

Norman Wilson
Toronto ON

PS: this message, as most of my e-mail, composed by
typing it into qed, editing as needed, then running
	>mail tuhs@tuhs.org

             reply	other threads:[~2021-03-29 16:00 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-29 15:58 Norman Wilson [this message]
2021-03-30  0:11 ` John Cowan
  -- strict thread matches above, loose matches on Subject: below --
2021-03-31  0:54 Norman Wilson
2021-03-31  1:29 ` John Cowan
     [not found] <CAKH6PiXmR6Jv0bkyOtHuk1ZLV64aeW7bnQkUnzV9-G_JaUVDAA@mail.gmail.com>
2021-03-30 23:38 ` John Cowan
2021-03-31  2:34   ` Bakul Shah
2021-03-29 23:21 M Douglas McIlroy
2021-03-30  3:39 ` Rich Morin
2021-03-29 14:34 Larry McVoy
2021-03-29 15:09 ` Anders Damsgaard
2021-03-29 15:26   ` Brantley Coile
2021-03-29 15:36     ` Mark van Atten
2021-03-29 15:43       ` Brantley Coile
2021-03-29 15:52         ` Mark van Atten
2021-03-29 15:45     ` Andy Kosela
2021-03-29 15:51       ` Clem Cole
2021-03-29 17:22       ` arnold
     [not found]         ` <CALMnNGgWrFRjXk5N4PgTj0_Yw3W5nCR2=CYSASM6dnqTooy8Dw@mail.gmail.com>
2021-03-30  8:53           ` arnold
2021-03-29 15:37   ` Clem Cole
2021-03-29 15:42     ` Anders Damsgaard
2021-03-29 15:49     ` Larry McVoy
2021-03-29 16:01     ` Andy Kosela
2021-03-29 18:12     ` Tom Ivar Helbekkmo via TUHS
2021-03-29 16:20 ` Steve Nickolas
2021-03-29 19:50 ` Rob Pike
2021-03-29 20:50   ` Michael Usher via TUHS
2021-03-29 20:55     ` Larry McVoy
2021-03-29 21:10       ` Erik E. Fair
2021-03-29 21:14         ` Larry McVoy
2021-03-29 21:53         ` Clem Cole
2021-03-29 22:29           ` John P. Linderman
2021-03-30  4:30             ` Rob Pike
2021-03-30  7:37             ` Harald Arnesen
2021-03-30 15:00         ` Kenneth Goodwin

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=20210329155812.C66DF640CB6@lignose.oclsc.org \
    --to=norman@oclsc.org \
    --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).