From: Scott Deerwester scott@cs.ust.hk
Subject: Sam and emacs
Date: Wed, 9 Feb 1994 21:16:06 -0500 [thread overview]
Message-ID: <19940210021606.nBFuTQE_uDEJBtEJu2nDrldW8o9J6khciuPJoI-bcIk@z> (raw)
I knew that I was going to regret bringing this up. :-)
Let's see if I've got this right: the Big Philosophical Reason
that the emacs page is blank in the Plan 9 manual is something
like:
Okay, fine, emacs has wonderful functionality, and is
extensible, etc, etc... but the things that make emacs
a wonderful tool ought to apply to a whole flinking operating
environment, not an editor, for Pete's sake. That's exactly what
Plan 9 was written for -- to be an operating system that does,
in a modular and sensible way, what emacs does in a horrible
monolithic way.
So I really ought to be comparing emacs with Plan 9 (and in
particular with acme, which is the part of the whole Plan that
meets the same goals that emacs-as-world-view meets), and not
with sam, which is a very nice *editor*, like God and Rob
intended.
Am I getting close?
Geez, I only just now realized that acme is a pun on "emacs".
Rob, can I buy a clue, please?
next reply other threads:[~1994-02-10 2:16 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-02-10 2:16 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-02-10 14:35 Bob
1994-02-09 17:02 rsalz
1994-02-09 11:42 Pete
1994-02-09 3:33 Ozan
1994-02-09 2:12 Scott
1994-02-09 1:04 Scott
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=19940210021606.nBFuTQE_uDEJBtEJu2nDrldW8o9J6khciuPJoI-bcIk@z \
--to=9fans@9fans.net \
/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).