From: Jonathan Gray <jsg@jsg.id.au>
To: Noel Chiappa <jnc@mercury.lcs.mit.edu>
Cc: tuhs@tuhs.org
Subject: [TUHS] Re: emacs
Date: Sat, 5 Aug 2023 14:34:08 +1000 [thread overview]
Message-ID: <ZM3RQDIFGnGaP9DX@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:
> 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.
1bsd has a bin/teco, which runs.
"teco which is of unknown origin (its mentioned in the Pascal
document so I threw it in.)"
Bill Joy, November 13, 1977
bin/READ_ME
at&t's unix system toolchest also included a teco, according
to various articles from 1985.
next prev parent reply other threads:[~2023-08-05 4:34 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
2023-08-05 4:34 ` Jonathan Gray [this message]
-- 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=ZM3RQDIFGnGaP9DX@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).