From: Scott Schwartz schwartz@groucho.cse.psu.edu
Subject: Sam and emacs
Date: Tue, 8 Feb 1994 21:12:38 -0500 [thread overview]
Message-ID: <19940209021238.bXL-RfPtKo7llrREgXDieHWsASpG5J0lxiPNeM0qg2Q@z> (raw)
| I'm really hesitant to bring this up... but the main barrier to me to
| making Plan 9 my major environment is the disdain for emacs. I
| *really* appreciate having an editor that is programmable down to its
| bones, in something like a real programming language.
At Usenix Rob was kind enough to let me play with acme (running on a
laptop pc) for a while, and it seemed like acme is sufficiently
extensible to be able to do most of the interesting things that are
attractive about emacs. It was pretty impressive, really.
Acme is extensible by using external agents, more like XEDIT and REXX
under VM/CMS than like emacs, actually. So if someone ports a Scheme
interpreter to Plan 9, who needs elisp? :-)
next reply other threads:[~1994-02-09 2:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-02-09 2:12 Scott [this message]
-- strict thread matches above, loose matches on Subject: below --
1994-02-10 14:35 Bob
1994-02-10 2:16 Scott
1994-02-09 17:02 rsalz
1994-02-09 11:42 Pete
1994-02-09 3:33 Ozan
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=19940209021238.bXL-RfPtKo7llrREgXDieHWsASpG5J0lxiPNeM0qg2Q@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).