From: Clem Cole <clemc@ccc.com>
To: Rob Pike <robpike@gmail.com>
Cc: TUHS main list <tuhs@minnie.tuhs.org>
Subject: Re: [TUHS] Old screen editors
Date: Tue, 29 Mar 2022 09:24:51 -0400 [thread overview]
Message-ID: <CAC20D2NSvE0irwt7gZGSC5OaFQx=Z1i=4ARon7ht2vXhGY_qZw@mail.gmail.com> (raw)
In-Reply-To: <CAKzdPgyfAvAy+EeeQGhTP609dLhb715yXwFf=-D-+emP=pgt7w@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1124 bytes --]
On Tue, Mar 29, 2022 at 4:31 AM Rob Pike <robpike@gmail.com> wrote:
> I used SOS a bit, but did anyone use Stopgap itself, or only its son?
>
I was going to ask the same question.
Funny, I still often (tend) to use line numbers to do multi-line operations
not marks - probably because SOS was one of the first editors I learned and
first I learned to use really well.
Now here is where my memory is hazy. I do remember using SOS on the
PDP-10s which had mostly glass TTYs, but for some reason I have memories of
using it on an ASR-33 on the TSS/360 - which must be wrong. I thinking,
there probably had to have been an IBM editor similar to it that I'm
confusing with the TOPS/TENEX. I also have no memories of what editor we
used on the original VMS V1.0 machine -- it must have been a member of the
TECO family, although again I want to say we had something like SOS.
I do remember that learning ed(1) on UNIX was a piece of cake and
immediately loved regex for patterns. I was still doing some PDP-10
hacking for the CS-Dept in those days, and bitching that I wanted ed(1) on
the 10s after I mastered it.
Clem
[-- Attachment #2: Type: text/html, Size: 2613 bytes --]
next prev parent reply other threads:[~2022-03-29 13:25 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 ` [TUHS] Old screen editors Lawrence Stewart
2022-03-29 0:53 ` Charles H Sauer (he/him)
2022-03-29 8:29 ` Rob Pike
2022-03-29 13:24 ` Clem Cole [this message]
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='CAC20D2NSvE0irwt7gZGSC5OaFQx=Z1i=4ARon7ht2vXhGY_qZw@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=robpike@gmail.com \
--cc=tuhs@minnie.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).