Computer Old Farts Forum
 help / color / mirror / Atom feed
From: imp at bsdimp.com (Warner Losh)
Subject: [COFF] TECO
Date: Thu, 14 Nov 2019 17:01:00 -0700	[thread overview]
Message-ID: <CANCZdfqUDC7BD4_FhsL1ydvi0Bi2vcy0RSY7rkJK+JNhpCjQCA@mail.gmail.com> (raw)
In-Reply-To: <CAC20D2MubS4oQYTF0EjQFh8azp9qUY4nOHURpofUh5x5EQVz5Q@mail.gmail.com>

On Thu, Nov 14, 2019 at 7:40 AM Clem Cole <clemc at ccc.com> wrote:

>
>
> On Thu, Nov 14, 2019 at 12:47 AM Lars Brinkhoff <lars at nocrew.org> wrote:
>
>>
>>   Richard F. Lary and Stan Rabinowitz made OS/8 TECO more compatible
>>
> Oh boy - there are two names from the past ;-)
>
>
>>   with other versions of TECO, and the result of this work is the
>>   version distributed by DECUS (catalog number 110450 is the
>>   manual). RT-11 TECO for the PDP-11 is a port of this code."
>>
> I sent a message to Richie and Jack Burness.   The last statement is a
> little worrisome, as 'porting' PDP-8 assembler to the PDP-11 was really not
> done in my experience.  Jack (Graphics) and Richie (OS) worked for the late
> Lorin Gale on the SW for the PDP-12 - which was based on the PDP-8 and then
> later rewrote a lot of things for Strecker's PDP-11.   But, my experience
> is it was always a rewrite/modeled after more than a 'port'.  FWIW: I
> also thought it was the late Kent Blackett that did much of the RT-11 work,
> but I'm not sure which is why I asked Jack and Richie who should remember.
>

I used TECO on a RSTS/e system in the early 80s, but it's visual mode and
'line noise' mode (the visual mode was akin to Emacs, but it wasn't emacs
as it had funky key bindings). Had a huge teco-11 manual printed that I
marked up. Was all in on TECO. Went to college. The TECO on the TOPS-20
machine was so different I hardly recognized it. Didn't matter, though,
since I fell in love with Emacs and rarely needed to type in raw TECO
commands to get things done....

I don't know if we ran the RT-11 TECO under RSTS/e system or not. The
installation had an odd mix of RT-11 and RSX-11 binaries and sources and it
was kinda hard to understand what was going on with the system as a mere
user that tried to PIP everything he could to the DECWRITER for later
study... I'm  kinda disappointed that it wasn't a Unix shop, but at the
time AT&T made it far too expensive for small mom&pop shops like the one I
worked in to run Unix commercially... :(

Warner
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20191114/98881e03/attachment-0001.html>


  reply	other threads:[~2019-11-15  0:01 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 [this message]
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=CANCZdfqUDC7BD4_FhsL1ydvi0Bi2vcy0RSY7rkJK+JNhpCjQCA@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).