From: Clem Cole <clemc@ccc.com>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@minnie.tuhs.org
Subject: Re: [TUHS] Old screen editors
Date: Tue, 29 Mar 2022 09:37:28 -0400 [thread overview]
Message-ID: <CAC20D2MjjBC88_bs1DNOLr5OAetjX-MCNmZkm=WCcPhHB5YWNQ@mail.gmail.com> (raw)
In-Reply-To: <20220329103902.42B9218C085@mercury.lcs.mit.edu>
[-- Attachment #1: Type: text/plain, Size: 2782 bytes --]
Check Paul Cantrell's VTECO - Video Teco Manual
<http://www.copters.com/teco.html> where has the sources here Video Teco
Sourceforge Masters <http://videoteco.sourceforge.net/>
Ward had a nice history here: TecoEditor
<http://c2.com/wiki/remodel/?TecoEditor> - worth reading - there are some
wonderful quotes. BTW I agree with Ward, while Ed Post was mostly right
in his "real Programmer' don't use Pascal" tome (also a classic read), but
real TECO users do know what typing their name will do ;-)
On Tue, Mar 29, 2022 at 6:39 AM Noel Chiappa <jnc@mercury.lcs.mit.edu>
wrote:
> > From: George Michaelson
>
> > Teco was painful.
>
> Some of us can recall when the _only_ choices for editing on UNIX (on the
> PWB1 systems at MIT) were 'ed' and TECO!
>
> But to add some real history (not just the usual low S/N flaming about
> people's opinions of various relatively recent software, which is way too
> common on this list), the guys at MIT in DSSR/RTS (the group which later
> did
> the 68K version of PCC), who had done the port of PDP-11 TECO (in MACRO-11)
> from the Delphi system at MIT (which preceded adoption of UNIX there) - a
> comment in one source file alludes to Delphi, so that's where it came
> from, to
> UNIX (I think this TECO was written there, and was not a port of a DEC one,
> since it's all in lower case, and doesn't have other DEC stylisms), after
> the
> port, added a '^R mode' similar to the one added to the PDP-10 ITS TECO and
> used there to write EMACS (in TECO's usual 'line noise' code - historical
> aside: at one point there was a whole 'Ivory' package for ITS TECO which
> could
> 'purify' ITS TECO code so that one copy in core [actual, real core!] could
> be
> shared by multiple processes). That was used to write an EMACS-like package
> for the PDP-11 UNIX TECO (but much simpler than real EMACS), which we used
> for
> quite a while before Montgomery EMACS for UNIX showed up.
>
> The full dump of the MIT-CSR PWB1 UNIX system which I retrieved has all the
> sources and documentation for that TECO, and the ^R-mode code, etc. If
> anyone
> is interested in seeing it (or maybe even playing with it, which will need
> the UNIX MACRO-11), let me know, and I'll upload it.
>
> Noel
>
> PS: Speaking of the full dump of the MIT-CSR PWB1 UNIX system, I was poking
> around it a couple of days ago, and I found V6 'multiplexor' kernel
> drivers -
> mpio.c and mpx.c, etc - I think thay 'fell off the back of a truck' at
> Bell,
> like a lot of other stuff we weren't supposed to have, like the circuit
> design
> tools, etc. I'm not sure if I have the user programs to go with them; I
> think
> I may have found some of them for Paul Ruizendaal a while back, but the
> memory
> has faded. Again, if interested, let me know.
>
[-- Attachment #2: Type: text/html, Size: 3606 bytes --]
next prev parent reply other threads:[~2022-03-29 13:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-29 10:39 Noel Chiappa
2022-03-29 11:05 ` Rob Pike
2022-03-29 13:37 ` Clem Cole [this message]
2022-03-29 15:43 ` Angelo Papenhoff
2022-03-30 5:36 ` Lars Brinkhoff
-- strict thread matches above, loose matches on Subject: below --
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
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 18:35 Noel Chiappa
2022-03-28 21:03 [TUHS] Alive? Warren Toomey via TUHS
2022-03-28 22:24 ` Bakul Shah
2022-03-28 23:23 ` Greg 'groggy' Lehey
2022-03-29 0:00 ` Bakul Shah
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
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
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='CAC20D2MjjBC88_bs1DNOLr5OAetjX-MCNmZkm=WCcPhHB5YWNQ@mail.gmail.com' \
--to=clemc@ccc.com \
--cc=jnc@mercury.lcs.mit.edu \
--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).