From: Clem Cole <clemc@ccc.com>
To: Lars Brinkhoff <lars@nocrew.org>
Cc: coff@tuhs.org, Will Senn <will.senn@gmail.com>
Subject: [COFF] Re: [TUHS] Re: regex early discussions
Date: Mon, 4 Mar 2024 15:53:52 -0500 [thread overview]
Message-ID: <CAC20D2MvRV9EWsbT7zsmOzb6wm1iGh36JhQ6ws61zj+TcuhfwQ@mail.gmail.com> (raw)
In-Reply-To: <7w7cih7nfd.fsf@junk.nocrew.org>
[-- Attachment #1: Type: text/plain, Size: 2286 bytes --]
On Mon, Mar 4, 2024 at 3:27 PM Lars Brinkhoff <lars@nocrew.org> wrote:
>
>
> I'd like expand on this, since I never heard about STOPGAP or SOS on the MIT
> PDP-6/10 computers.
Hmm, you are undoubtedly right. STOPGAP and SOS might just have been at
DECisms.
I initially used SOS on the CMU PDP-10s to prep BLISS, Macro-10, and SAIL
for a small job I got. It was the most like the editor used on
other job on the Computere Center's TSS system (whose name I forget, which
I learned first). I wanted to get stuff done, not learn a new editor, so
that was fine. It also worked on VMS 1.0, IIRC, as I had a job moving some
BLISS-10 code to BLISS32 on the first Vax. At some point, I was shown TECO
and EMACS on the PDP-10s, but I had started to work on PDP-11 UNIX by then,
and ed(1) was all that was on V5. At the time, learning something fancier
for the PDP-10 seemed like a wrong time investment since I was not getting
paid to work on that system, and I was getting paid to hack on UNIX.
Truth be known, as a UNIX person, I got pretty adept with ed, so even when
vi mode of ex showed up a few years later, I was actually slow to bother.
Any the CMU SOS doc I have says STOPGAP was DEC/MIT-ism but I bet that's
wrong -- it was probably just DEC.
Jargon file says: *SOS n.,obs. /S-O-S/ 1. An infamously {losing} text
editor. Once, back in the 1960s, when a text editor was needed for the
PDP-6, a hacker crufted together a {quick-and-dirty} `stopgap editor' to be
used until a better one was written. Unfortunately, the old one was never
really discarded when new ones (in particular, {TECO}) came along. SOS is a
descendant (`Son of Stopgap') of that editor, and many PDP-10 users gained
the dubious pleasure of its acquaintance. Since then other programs similar
in style to SOS have been written, notably the early font editor BILOS
/bye'lohs/, the Brother-In-Law Of Stopgap (the alternate expansion `Bastard
Issue, Loins of Stopgap' has been proposed). 2. /sos/ n. To decrease;
inverse of {AOS}, from the PDP-10 instruction set.*
> TECO was ported over to the 6 only a few weeks after delivers, and that
> seems to have been the major editor ever since.
> Did you think of the SAIL PDP-6?
>
Maybe. I don't know.
ᐧ
ᐧ
[-- Attachment #2: Type: text/html, Size: 4735 bytes --]
next prev parent reply other threads:[~2024-03-04 20:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <13abd764-984a-4c9f-8e3e-b1eb7c624692@gmail.com>
[not found] ` <CAC20D2MFY4g+j+e3OUOLgZtcgnYKu93ENjkG80cH59fr5n44bQ@mail.gmail.com>
2024-03-04 20:27 ` Lars Brinkhoff
2024-03-04 20:53 ` Clem Cole [this message]
2024-03-05 6:49 ` Lars Brinkhoff
2024-03-05 16:34 ` Clem Cole
2024-03-06 0:59 ` Will Senn
2024-03-05 19:30 Noel Chiappa
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=CAC20D2MvRV9EWsbT7zsmOzb6wm1iGh36JhQ6ws61zj+TcuhfwQ@mail.gmail.com \
--to=clemc@ccc.com \
--cc=coff@tuhs.org \
--cc=lars@nocrew.org \
--cc=will.senn@gmail.com \
/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).