The Unix Heritage Society mailing list
 help / color / mirror / Atom feed
From: Michael Usher via TUHS <tuhs@minnie.tuhs.org>
To: arnold@skeeve.com
Cc: The Eunuchs Hysterical Society <tuhs@tuhs.org>
Subject: Re: [TUHS] v7 uucp debugging help requested
Date: Mon, 6 Jul 2020 00:11:33 -0700	[thread overview]
Message-ID: <CACg3+DG3UCLuxn-KkXdPsyuiKSKxcN2vQtqWXTOpVUm1ExrJ3A@mail.gmail.com> (raw)
In-Reply-To: <202007060651.0666paxk031885@freefriends.org>

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

I actually like ed and sam.  I find it "soothing" to be able to manipulate
text almost "programmatically"....

As an undergrad at USyd EE Dept, the VT100s in the computer lab were often
all taken, but there were a few LA30s still hooked up and no-one wanted to
use them.  I learned how to optimally enter, compile and debug code through
a paper interface.  It was VMS of course at EE, but when I started using
the Unix systems at CS a year later, the 11/750 was so heavily loaded that
"ed" was the best choice for getting assignments done quickly.  Line
editors were also much more pleasant to use over slow modem connections.  I
had a 28.8k modem but the dialup pool rarely got you a high speed
connection...

But back to the original topic...  Has the MHSnet code made it into the
public domain?

Michael

On Sun, Jul 5, 2020 at 11:52 PM <arnold@skeeve.com> wrote:

> Warner Losh <imp@bsdimp.com> wrote:
>
> > On Sun, Jul 5, 2020, 10:14 PM 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...
> > >
> >
> > I should do that... So far I've managed to get by with sed :)
> >
> > Warner
> >
> > >
>
> If you know the ex subset of vi, you know most of what you need to
> know to use ed ...
>
> Arnold
>


-- 
Michael Usher
Senior Wireless Network Engineer
University of California, Santa Cruz
musher@ucsc.edu        831-459-3697

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

  reply	other threads:[~2020-07-06  7:13 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 [this message]
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
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=CACg3+DG3UCLuxn-KkXdPsyuiKSKxcN2vQtqWXTOpVUm1ExrJ3A@mail.gmail.com \
    --to=tuhs@minnie.tuhs.org \
    --cc=arnold@skeeve.com \
    --cc=musher@ucsc.edu \
    --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).