From: Scott Deerwester scott@cs.ust.hk
Subject: Apology
Date: Thu, 10 Feb 1994 21:22:22 -0500 [thread overview]
Message-ID: <19940211022222.CBhJD_rbnfCU7h5ER4vkSd94SX56h9MHGbRMZBIxg0M@z> (raw)
I'd like to apologize for bringing up the topic of emacs here. My
intention was to try to better understand Plan 9 as a practical
system. The spirit of the original request was:
Emacs has all of this wonderful functionality... Plan 9 *must*, but
I don't see how. Could somebody explain it to me?
I'm a person who likes Plan 9 a *lot* in principle, but who is having
a lot of trouble putting that into practice. (I'm also having a lot
of trouble convincing anybody else at my institution to care, but
that's another issue.) My productivity as a hacker depends strongly
on things that emacs gives me. I (and presumably others who share my
"problem") need to see that moving to Plan 9 won't cut my productivity
in half.
The issue seemed to me to have a lot more to do with Plan 9 than emacs
-- I certainly had no intention to try to "convert" anybody to emacs.
The discussion has clarified the issue a lot; the thing wrong with
emacs (and *right* with Plan 9) is that emacs provides its
functionality in a nasty monolithic way instead of in a clean, modular
way. Plan 9 gives you functionality similar to that of emacs, but
without forcing an editor to be anything but a good editor.
In any case, the thread has obviously offended several of you, so I'll
drop it... and go back to trying to get Plan 9 running on my notebook.
_________________________________________________________________
Scott Deerwester | The Hong Kong University of
Internet: scott@cs.ust.hk | Science and Technology
Phone: (852) 358-6985 | Department of Computer Science
-----------------------------------------------------------------
next reply other threads:[~1994-02-11 2:22 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-02-11 2:22 Scott [this message]
1995-11-15 13:25 Apology Thomas
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=19940211022222.CBhJD_rbnfCU7h5ER4vkSd94SX56h9MHGbRMZBIxg0M@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).