From: grog at lemis.com (Greg 'groggy' Lehey)
Subject: [COFF] TECO (was: History of m6?)
Date: Thu, 14 Nov 2019 09:31:01 +1100 [thread overview]
Message-ID: <20191113223101.GA98220@eureka.lemis.com> (raw)
In-Reply-To: <7wy2wjke8k.fsf@junk.nocrew.org>
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.
Greg
--
Sent from my desktop computer.
Finger grog at lemis.com for PGP public key.
See complete headers for address and phone numbers.
This message is digitally signed. If your Microsoft mail program
reports problems, please read http://lemis.com/broken-MUA
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 163 bytes
Desc: not available
URL: <http://minnie.tuhs.org/pipermail/coff/attachments/20191114/419056cc/attachment.sig>
next prev parent reply other threads:[~2019-11-13 22:31 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 ` grog [this message]
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 ` [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=20191113223101.GA98220@eureka.lemis.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).