From: "Thomas Paulsen" <thomas.paulsen@firemail.de>
To: "Lars Brinkhoff" <lars@nocrew.org>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] History of m6?
Date: Thu, 14 Nov 2019 10:26:39 +0100 [thread overview]
Message-ID: <f68fbf8dad43ac5e8314c094c1ece06f@firemail.de> (raw)
In-Reply-To: <7w8sokklwp.fsf@junk.nocrew.org>
'Why not? TECO is both an editor and a programming language. The first
Emacs was written in TECO.'
Hic Rhodos - Hic Salta!
I have a account on a remote twenex PDP10. There is a editor named emacs. This is a very archaic piece of software. It doesn't know any teco commands no matter how I tried. I'm pretty sure that this is teco-emacs. I draw my own conclusions from these observations which are far away from all these myths.
next prev parent reply other threads:[~2019-11-14 9:27 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 21:10 Arnold Robbins
2019-11-11 22:18 ` Dennis Boone
2019-11-12 16:01 ` Leah Neukirchen
2019-11-11 22:31 ` Theodore Y. Ts'o
2019-11-11 22:58 ` Dave Horsfall
2019-11-12 0:07 ` Nemo Nusquam
2019-11-12 0:39 ` Dave Horsfall
2019-11-12 0:30 ` Clem cole
2019-11-16 16:27 ` SPC
2019-11-17 5:30 ` Dave Horsfall
2019-11-17 5:50 ` Larry McVoy
2019-11-17 18:12 ` Bakul Shah
2019-11-17 18:23 ` Michael Kjörling
2019-11-17 18:56 ` Bakul Shah
2019-11-17 22:46 ` Barry Stanly
2019-11-12 0:42 ` Dennis Boone
2019-11-11 22:37 ` Michael Kjörling
2019-11-12 1:09 ` Steve Johnson
2019-11-12 15:07 ` Clem Cole
2019-11-13 9:16 ` Thomas Paulsen
2019-11-13 12:20 ` Lars Brinkhoff
2019-11-13 12:50 ` Mike Markowski
2019-11-13 13:02 ` Lars Brinkhoff
2019-11-13 16:56 ` Paul Winalski
2019-11-13 19:19 ` Lars Brinkhoff
2019-11-13 19:21 ` Jon Steinhart
2019-11-14 9:26 ` Thomas Paulsen [this message]
2019-11-14 10:53 ` Lars Brinkhoff
2019-11-13 21:26 ` Dave Horsfall
2019-11-13 22:53 ` Jaap Akkerhuis
2019-11-12 15:15 Doug McIlroy
2019-11-13 7:38 ` arnold
2019-11-13 10:55 ` David Arnold
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=f68fbf8dad43ac5e8314c094c1ece06f@firemail.de \
--to=thomas.paulsen@firemail.de \
--cc=lars@nocrew.org \
--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).