From: lars at nocrew.org (Lars Brinkhoff)
Subject: [COFF] [TUHS] History of m6?
Date: Thu, 14 Nov 2019 10:53:21 +0000 [thread overview]
Message-ID: <7wblteiva6.fsf@junk.nocrew.org> (raw)
In-Reply-To: <f68fbf8dad43ac5e8314c094c1ece06f@firemail.de> (Thomas Paulsen's message of "Thu, 14 Nov 2019 10:26:39 +0100")
I suggest continuing this on COFF.
Thomas Paulsen wrote:
> 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.
Yes, it should be TECO Emacs. Normal use of Emacs rarely needs TECO
commands.
To get a TECO minibuffer type Meta-Altmode (Esc Esc). You should get a
small window at the top of the terminal in which you can enter TECO
commands. Execute them with double altmode as you would in any TECO.
> I draw my own conclusions from these observations which are far away
> from all these myths.
I try to stay with the facts. I actually use TECO Emacs almost daily,
and I have built it from sources. Some other information is based on
email conversations among those who wrote Emacs.
next prev parent reply other threads:[~2019-11-14 10:53 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 ` clemc
2019-11-13 15:06 ` lars
2019-11-13 15:32 ` clemc
2019-11-13 22:31 ` [COFF] TECO (was: History of m6?) grog
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 ` lars [this message]
2019-11-14 16:35 ` [COFF] [TUHS] History of m6? 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=7wblteiva6.fsf@junk.nocrew.org \
--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).