From: Jonathan Gray <jsg@jsg.id.au>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: emacs
Date: Fri, 4 Aug 2023 15:03:02 +1000 [thread overview]
Message-ID: <ZMyGhu99Np6pDrbD@largo.jsg.id.au> (raw)
In-Reply-To: <20230804021728.14AD318C080@mercury.lcs.mit.edu>
On Thu, Aug 03, 2023 at 10:17:28PM -0400, Noel Chiappa wrote:
> > From: Will Senn
> > Was TECO ever on unix?
>
> I don't think it was widespread, but there was a TECO on the PDP-11 UNIXes at
> MIT; until Montgomery Emacs arrived, it was the primary editor used on those
> machines.
>
> Not that most people used TECO commands for editing; early on, they added '^R
> mode' to the UNIX TECO, similar to the one on ITS TECO, and a macro package
> was written for it (in TECO - so again, the source looks like line noise);
> the command set was like a stripped down EMACS - about a dozen command
> characters total; see the table about a page down here:
>
> http://ana-3.lcs.mit.edu/~jnc/tech/unix/teco/help
>
> All the source, and documentation, such as it is, it available, here:
>
> http://ana-3.lcs.mit.edu/~jnc/tech/unix/teco/
>
> but don't even think about running it. It's written in MACRO-11, and it used
> a version of that hacked at MIT to run on UNIX. To build new versions of
> that, you need a special linker - written in BCPL. So you also need the UNIX
> BCPL compiler.
>
> Noel
The HRSTS version of it can be found in the UNSW tapes.
The usenix 77 tape has h/help/teco and a 0-sized h/teco/cont.a
Matt Fichtenbaum's TECO for Ultrix appears in
tuhs/Applications/Shoppa_Tapes/usenix878889.tar.gz
usenix87/Editors/Teco/
"Harvard UNIX TECO runs under the UNIX operating system on a
PDP-11. It was written by Bob Case, Peter Langston, Bruce Borden,
Brent Byer, and Tucker Taft using the Harvard-Radcliffe Student
Timesharing System (HRSTS)."
"Harvard UNIX TECO is based on a 1973 version of MIT TECO and is
written in MACRO-11. There is a possibility that this TECO will
be expanded and recoded into C in the near future."
https://bitsavers.org/pdf/dec/teco/MobyMunger_%233part2_Nov79.pdf
"HRSTS (new)Teco V_3p"
https://www.tuhs.org/Archive/Distributions/UNSW/88/
hp14/source/L/teco/
https://www.tuhs.org/Archive/Distributions/UNSW/90/
L/teco/
"BBN has a TECO for Unix."
tuhs/Documentation/AUUGN/AUUGN-V01.5.pdf pg 57
SOFTWARE TOOLS and UNIX Users Group Conference Report
by David M. Phillips, 26 June 1979
next prev parent reply other threads:[~2023-08-04 5:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-04 2:17 Noel Chiappa
2023-08-04 5:03 ` Jonathan Gray [this message]
2023-08-05 4:34 ` Jonathan Gray
-- strict thread matches above, loose matches on Subject: below --
2023-08-04 2:36 Noel Chiappa
2023-08-04 2:42 ` Rob Pike
2023-08-04 16:19 ` Clem Cole
2023-08-05 4:09 ` George Michaelson
2023-08-04 0:04 [TUHS] emacs Will Senn
2023-08-04 0:19 ` [TUHS] emacs Adam Thornton
2023-08-04 0:27 ` Rob Pike
2023-08-04 0:49 ` Larry McVoy
2023-08-04 1:00 ` Rich Salz
2023-08-04 13:25 ` Lars Brinkhoff
2023-08-04 0:32 ` Warner Losh
2023-08-04 1:23 ` Larry Stewart
2023-08-04 13:38 ` Ronald Natalie
2023-08-04 1:59 ` Will Senn
2023-08-04 2:26 ` Erik E. Fair
2023-08-04 0:39 ` Greg 'groggy' Lehey
2023-08-04 0:44 ` Clem Cole
2023-08-04 0:47 ` Clem Cole
2023-08-04 0:53 ` Warner Losh
2023-08-04 2:14 ` Dan Halbert
2023-08-04 2:18 ` Bakul Shah
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=ZMyGhu99Np6pDrbD@largo.jsg.id.au \
--to=jsg@jsg.id.au \
--cc=jnc@mercury.lcs.mit.edu \
--cc=tuhs@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).