From: clemc at ccc.com (Clem Cole)
Subject: [COFF] [TUHS] History of m6?
Date: Wed, 13 Nov 2019 10:32:29 -0500 [thread overview]
Message-ID: <CAC20D2O6S+2gUFY827t21qqedrEaMWGOCEQ5pDW=iAU_R7=V6g@mail.gmail.com> (raw)
In-Reply-To: <7wy2wjke8k.fsf@junk.nocrew.org>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1443 bytes --]
On Wed, Nov 13, 2019 at 10:06 AM Lars Brinkhoff <lars at nocrew.org> wrote:
>
> And not just the PDP-10. I think just about every DEC computer had a version
> of TECO, right?
>
Very likely. There were a lot of implementations, but it had grown in
size, that address space was an issue. I do have memories of a simple
TECO for RT-11, but the EMACS macros did not load/could not run (I've
forgotten why). VAX/VMS eventually had a TECO which best I can tell,
begat EDT, but that was after my time.
BTW: I remembered the name of the line editor for the PDP-10 I had learned
before I used TECO: SOS - Son of Stopgap (I want to say the name of the
IBM/TSS text editor was REDIT, but that's probably wrong). I do remember
that going from the IBM system editor to SOS was very easy, the commands
were similar. And, a flavor of SOS also ran on VAX/VMS before TECO or EDT
arrived. As I had to relearn it, when we worked on the first VAX, since
SOS was the only editor. But by that time, I had learned ed (1) and the
UNIX tools and had mostly migrated away from the PDP-10. I remember being
annoyed because I wanted to use regular expressions on the VAX editor, and
had come to realize how much of the UNIX tool kit had become accustomed in
my workflow.
Clem
ᐧ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20191113/92509ce0/attachment-0001.html>
next prev parent reply other threads:[~2019-11-13 15:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201911112110.xABLAQfW004396@skeeve.com>
[not found] ` <d155d03e5177486fb1702add77ed540bebc3515a@webmail.yaccman.com>
[not found] ` <CAC20D2PjXNN-LTvpfTRvAzoCo-wMbf9tLuNTzs63_7VEGJUD0w@mail.gmail.com>
[not found] ` <08b6c7ce02adabe45f54621c3cbe9863@firemail.de>
2019-11-13 14:17 ` clemc
2019-11-13 15:06 ` lars
2019-11-13 15:32 ` clemc [this message]
2019-11-13 22:31 ` [COFF] TECO (was: History of m6?) grog
2019-11-14 5:47 ` [COFF] TECO lars
2019-11-14 14:40 ` clemc
2019-11-15 0:01 ` imp
2019-11-14 15:00 ` [COFF] TECO (was: History of m6?) clemc
[not found] ` <7w8sokklwp.fsf@junk.nocrew.org>
[not found] ` <f68fbf8dad43ac5e8314c094c1ece06f@firemail.de>
2019-11-14 10:53 ` [COFF] [TUHS] History of m6? lars
2019-11-14 16:35 ` paul.winalski
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='CAC20D2O6S+2gUFY827t21qqedrEaMWGOCEQ5pDW=iAU_R7=V6g@mail.gmail.com' \
--to=coff@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).