Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!caip!think!husc6!seismo!mcvax!enea!erix!erisun!hans
From: hans@erisun.UUCP (Hans J. Albertsson)
Newsgroups: net.emacs
Subject: Re: Why emacs?
Message-ID: <707@erisun.UUCP>
Date: Sun, 12-Oct-86 04:44:34 EDT
Article-I.D.: erisun.707
Posted: Sun Oct 12 04:44:34 1986
Date-Received: Tue, 14-Oct-86 07:29:44 EDT
References: <21600007@uiucuxc>
Reply-To: hans@erisun.UUCP (Hans J. Albertsson)
Organization: Ericsson Information Systems Sverige AB, Sundbyberg, Sweden
Lines: 25

[]

1) Emacs is multi-buffer + multi-window. Edit several texts in one single
   editor instance.

2) Modes are per buffer, so diverse editing related jobs can be handled
   in parallell.

3) Emacs runs subprocesses with I/O thru special mode edit buffers, which
   makes for nice program development support, or WYSIWIG simulation
   even for nroff/troff. At least one commercial Prolog uses emacs as
   a development environment, as does/did SUN Common Lisp. Comfortable,
   and travels well between terminal types.

4) Emacs-like editors exist for the most diverse systems, and has been
   around for a while, now.

5) On an ASCII terminal, there exists no better window-system emulator.

However, even I, who really find vi unbearable with it's dual modes, 
know one or two things that vi does better. Such as the implicit macro
in ".". However, try and ADD a word completion mode using current buffer
as abbreviation data base to vi... So:

6) Emacs is easily user extensible.