From: dave at horsfall.org (Dave Horsfall)
Subject: [COFF] [TUHS] History of m6? (fwd)
Date: Sun, 17 Nov 2019 01:36:35 +1100 (EST) [thread overview]
Message-ID: <alpine.BSF.2.21.9999.1911170133330.408@aneurin.horsfall.org> (raw)
Meant to go to the list...
-- Dave
---------- Forwarded message ----------
Date: Fri, 15 Nov 2019 07:23:19 +1100 (EST)
From: Dave Horsfall <dave at horsfall.org>
To: Paul Winalski
Subject: Re: [COFF] [TUHS] History of m6?
On Thu, 14 Nov 2019, Paul Winalski wrote:
> I used to think that "Emacs" stood for
> "escape-meta-alt-control-shift". :-) It's too finger-busy with all
> that alt, escape, and meta stuff for my taste.
Hey, that's a bit old :-)
Date: Sat, 2 Aug 2014 17:28:41 +0000
From: Benjamin Huntsman
To: "tuhs at minnie.tuhs.org" <tuhs at minnie.tuhs.org>
Subject: Re: [TUHS] Unix taste (Re: terminal - just for fun)
>> EMACS - eight megs and constantly swapping :)
>I like my own version: "Enough Memory? A Concept Strange!"
I thought it stood for Escape-Meta-Alt-Control-Shift :)
I thought I came up with it independently, but obviously it was in the back of
my mind.
-- Dave
reply other threads:[~2019-11-16 14:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=alpine.BSF.2.21.9999.1911170133330.408@aneurin.horsfall.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).