Computer Old Farts Forum
 help / color / mirror / Atom feed
From: clemc at ccc.com (Clem Cole)
Subject: [COFF] TECO (was: History of m6?)
Date: Thu, 14 Nov 2019 10:00:04 -0500	[thread overview]
Message-ID: <CAC20D2MFaTpEP-hgTAHEDaZzNL3FW=mBp748tcS594aPZp2Bqw@mail.gmail.com> (raw)
In-Reply-To: <20191113223101.GA98220@eureka.lemis.com>

On Wed, Nov 13, 2019 at 11:24 PM Greg 'groggy' Lehey <grog at lemis.com> wrote:

> On Wednesday, 13 November 2019 at 15:06:19 +0000, Lars Brinkhoff wrote:
> > I think just about every DEC computer had a version of TECO, right?
>
> I don't recall seeing it on our PDP-8 and -12.  Does anybody else?
> Presumably they were too small for it, but the -8 made up a large part
> of DEC's production.
>

Lar's comment about Richie and Stan having worked on a PDP-8 version sounds
reasonable.  I don't know Stan's full story as I never worked with him
closely, but Lorin Gale hired Richie and Jack into DEC out of Brooklyn Poly
to work on the PDP-12 in about 1972; where they had been PDP-10 hackers as
students/roommates (and nearly 50 years, multiple children and marriages
later, still nearly inseparable/often hard to tell apart).

Anyway, the PDP-8 was the development system for the 12.  So Richie wanting
a more compatible TECO would be something he could/would have created.

My memory is that TECO-8 was sort of like the PC's micro-emacs in that is
was written in the key/model after it's namesake, using TECO-10 in syntax
and commands, but very limited and much smaller and could run on a more
resource limited system.   It was certainly true for TECO-11 the PDP-10's
macros (EMACS) would not work there and I think the same was true for
TECO-8.

That said, I did not mess with either enough, as I came late the PDP-8/12
work, and really started with PDP-11s and Vaxen.   So we would need to talk
to a few people a little older, like Richie or Jack Burness who were there.

Clem
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20191114/f6ca95fa/attachment.html>


  parent reply	other threads:[~2019-11-14 15:00 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       ` [COFF] [TUHS] History of m6? clemc
2019-11-13 15:06         ` lars
2019-11-13 15:32           ` clemc
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             ` clemc [this message]
     [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='CAC20D2MFaTpEP-hgTAHEDaZzNL3FW=mBp748tcS594aPZp2Bqw@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).