From: Scott Deerwester scott@cs.ust.hk
Subject: Sam and emacs
Date: Tue, 8 Feb 1994 20:04:38 -0500 [thread overview]
Message-ID: <19940209010438.9Xig7u3ihaECnSeXWERP3LLISg1Vr65O34UCrgjS4wU@z> (raw)
Vijay writes:
>> However, I think Rob Pike has said that they are trying
>> to get Plan 9 publicly released. I assume he means as
>> free software along the lines of awk or sam. I believe
>> this is the only way Plan 9 will ever have a chance to see
>> the widespread use it deserves, and so I hope very much
>> that this happens.
>
> Oh god, I think the earth moved for me.
> I am drumming up support for plan 9 here, but when I say it
> doesn't run emacs, people lose all interest and the weird thing
> is that after about 2 weeks of running sam, I would hate to go
> back to emacs, and I am a die hard emacs/vi fan. But most people
> don't seem to be willing to take the time to learn sam properly.
> People I showed sam to... oh whats the point.
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. It's not that
I'm addicted to left-meta-shift-coke bottle style interfaces, but...
I really don't understand the "this page intentionally left blank"
attitude. I mean, the fact that you can build things like ange-ftp
and WWW mode is *really* nice! How do accomodate the same sort of
thing in sam? And I don't know how to function without emacs' gdb
mode! The fact that the editor itself can put me at the line where
the music stopped, and I've got a full honest-to-God editor under me
without having to go, "Uh.. lessee.. that was line 136 in file
blurfle.c..". And when I recompile, I have all of the error messages
in a buffer, and need two keystrokes per syntax error (which adds up
if you've got enough syntax errors ;-) to page through them and fix
them -- again, with a real editor.
And then there's guess-indent mode that does about as good a job as I
can at figuring out where I probably wanted the cursor after the line
wraps, and abbrev mode, which now auto-corrects all of my most common
typos -- watching somebody's face when I type "taht " and they see the
"a" and the "h" switch places as soon as I hit the space is kind of
fun.
There's lots that I don't like about emacs, but the fact that it's
*programmable* means that my productivity as a programmer and generic
computer professional is about an order of magnitude higher than it
would have been if I didn't have it.
The most common complaint that I hear about emacs is that there are
too many blasted things to learn -- and the learning curve *is* really
steep. But that doesn't seem to be the reason for the intentional
blank page in the Plan 9 manual. Would somebody please enlighten me?
next reply other threads:[~1994-02-09 1:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
1994-02-09 1:04 Scott [this message]
1994-02-09 2:12 Scott
1994-02-09 3:33 Ozan
1994-02-09 11:42 Pete
1994-02-09 17:02 rsalz
1994-02-10 2:16 Scott
1994-02-10 14:35 Bob
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=19940209010438.9Xig7u3ihaECnSeXWERP3LLISg1Vr65O34UCrgjS4wU@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).