The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Rob Pike <robpike@gmail.com>
To: Norman Wilson <norman@oclsc.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] v7 uucp debugging help requested
Date: Wed, 8 Jul 2020 08:47:38 +1000	[thread overview]
Message-ID: <CAKzdPgxCuWH==39cmnjpNvnnu+1kEVcPoWazVrKN8_njSgCBCg@mail.gmail.com> (raw)
In-Reply-To: <1594149663.18455.for-standards-violators@oclsc.org>

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

The thing about ed that is missed by johnny-come-latelys who mock it for
its lowness is that it was so much higher than most, if not all the
commercially available text editors of its time. The gold standard was
perhaps Son of Stopgap, whose very name tells you the state of things.

I remember spending a couple of days baking inside a radio telescope
control cabin implementing a miniature version of ed in forth just so I
work more effectively on the task to come.

-rob


On Wed, Jul 8, 2020 at 5:22 AM Norman Wilson <norman@oclsc.org> wrote:

> Dave Horsfall:
>
>   A boss of mine insisted that we all learned "ed", because one day it
> might
>   be the only editor available to you after a crash; he was right...
>
> ====
>
> Besides which, as The Blessed Manual said in every
> Research edition:
>         ed is the standard text editor.
>
> Norman Wilson
> Toronto ON
> (typing this in Toronto qed)
>

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

  reply	other threads:[~2020-07-07 22:48 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-07-07 19:20 Norman Wilson
2020-07-07 22:47 ` Rob Pike [this message]
2020-07-07 23:42   ` Adam Thornton
  -- strict thread matches above, loose matches on Subject: below --
2020-07-04  0:35 Norman Wilson
2020-07-03 20:52 Adam Thornton
2020-07-03 21:26 ` Clem Cole
2020-07-03 22:38 ` Grant Taylor via TUHS
2020-07-04  0:28   ` Clem Cole
2020-07-04  0:31   ` Clem Cole
2020-07-04 19:33   ` Adam Thornton
2020-07-04 20:02     ` Clem Cole
2020-07-04 21:58       ` Adam Thornton
2020-07-05  5:42         ` Adam Thornton
2020-07-03 22:50 ` John Cowan
2020-07-04 16:33   ` Adam Thornton
2020-07-04 18:34     ` John Cowan
2020-07-04 18:44       ` Jon Forrest
2020-07-04 19:34       ` Adam Thornton
2020-07-06  4:12     ` Dave Horsfall
2020-07-06  4:18       ` Warner Losh
2020-07-06  6:51         ` arnold
2020-07-06  7:11           ` Michael Usher via TUHS
2020-07-06 13:57       ` Clem Cole
2020-07-06 18:51         ` John Cowan
2020-07-06 19:19           ` arnold
2020-07-06 19:36             ` John Cowan
2020-07-06 19:58               ` John Cowan
2020-07-06 20:48               ` Clem Cole
2020-07-07  6:21                 ` arnold
2020-07-10  5:05                 ` Win Treese
2020-07-10  5:19                   ` Warner Losh
2020-07-14  2:52                     ` Dave Horsfall
2020-07-06 21:47             ` Dave Horsfall
2020-07-07  6:23               ` arnold
2020-07-07 21:45                 ` Dave Horsfall
2020-07-06 21:18         ` Dave Horsfall
2020-07-06 21:47           ` John Cowan

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='CAKzdPgxCuWH==39cmnjpNvnnu+1kEVcPoWazVrKN8_njSgCBCg@mail.gmail.com' \
    --to=robpike@gmail.com \
    --cc=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).