The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Clem Cole <clemc@ccc.com>
To: Dave Horsfall <dave@horsfall.org>
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] v7 uucp debugging help requested
Date: Mon, 6 Jul 2020 09:57:49 -0400	[thread overview]
Message-ID: <CAC20D2M=ZfqTVgZchttkVLccyziee+Ch46EXRY8b8ExJAuX7OQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.BSF.2.21.9999.2007061410530.455@aneurin.horsfall.org>

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

I always recommend doing the exercises in Rob and Brian's UPE on ed because
then everything else makes sense, like sed or any other editor.   Plus you
get the advantage you point out, and the reality is that so many
simpler editors (like edlin) have similar functionality, it means you can
get something done, just about anywhere.

On Mon, Jul 6, 2020 at 12:14 AM Dave Horsfall <dave@horsfall.org> wrote:

> On Sat, 4 Jul 2020, Adam Thornton wrote:
>
> > Since I find ed thoroughly unpleasant to use, having a screen editor was
> > a must for me to use v7 for any length of time, and s fills that role
> > rather nicely.
>
> 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...
>
> -- Dave
>

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

  parent reply	other threads:[~2020-07-06 13:59 UTC|newest]

Thread overview: 38+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
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 [this message]
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
2020-07-07  1:30         ` [TUHS] Editors (was: v7 uucp debugging help requested) Greg 'groggy' Lehey
2020-07-04  0:35 [TUHS] v7 uucp debugging help requested Norman Wilson
2020-07-07 19:20 Norman Wilson
2020-07-07 22:47 ` Rob Pike
2020-07-07 23:42   ` Adam Thornton

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='CAC20D2M=ZfqTVgZchttkVLccyziee+Ch46EXRY8b8ExJAuX7OQ@mail.gmail.com' \
    --to=clemc@ccc.com \
    --cc=dave@horsfall.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).