Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.1 6/24/83; site mit-eddie.UUCP
Path: utzoo!watmath!clyde!burl!ulysses!allegra!mit-eddie!phr@UCB-VAX.Berkeley.EDU
From: phr@UCB-VAX.Berkeley.EDU
Newsgroups: net.emacs
Subject: re: worth switching from gosling/unipress?
Message-ID: <5449@mit-eddie.UUCP>
Date: Sat, 5-Oct-85 18:41:43 EDT
Article-I.D.: mit-eddi.5449
Posted: Sat Oct  5 18:41:43 1985
Date-Received: Mon, 7-Oct-85 02:47:54 EDT
Sender: daemon@mit-eddi.UUCP
Organization: MIT, Cambridge, MA
Lines: 27

From: phr@UCB-VAX.Berkeley.EDU (Paul Rubin)
If you are choosing an Emacs to start with, GNU Emacs is clearly superior.
Whether it is worth the effort of switching from Gosling/Unipress
depends on how much energy you have already invested in writing
extensions, etc.  (Note that GNU Emacs has an mlisp code translator
that does a lot of the work of converting mlisp code into Elisp for you).

I don't do many sophisticated-type things (for which GNU Emacs with its
Elisp would be the obvious win) but even for everyday editing I found
it well worth switching because (compared with Gosling Emacs #85, I
haven't used Unipress's), GNU Emacs:

	1) has better built-in documentation
	2) has a real manual that is very well written
	3) has sophiticated C mode which actually makes life *easier*
	4) has better process control, compile-command more powerful/useful
	5) starts up faster, runs faster, leaves fewer turds around
	6) you can interrupt runaway lisp commands, searches, etc.
	7) horizontal windows are sometimes useful
	8) etc.

I could think of more stuff.  On the minus side, the command set is
different enough to be annoying til you get used to it.  In my case
this took about 2 days.

	paul rubin
	(GNU collaborator, sometimes)