Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!rochester!cornell!batcomputer!braner
From: braner@batcomputer.TN.CORNELL.EDU (braner)
Newsgroups: net.micro.atari16
Subject: Re: GNU_EMACS
Message-ID: <1085@batcomputer.TN.CORNELL.EDU>
Date: Tue, 23-Sep-86 23:15:18 EDT
Article-I.D.: batcompu.1085
Posted: Tue Sep 23 23:15:18 1986
Date-Received: Wed, 24-Sep-86 05:24:11 EDT
References: <8609221236.AA01198@ucbvax.Berkeley.EDU>
Reply-To: braner@batcomputer.UUCP (braner)
Organization: Theory Center, Cornell University, Ithaca NY
Lines: 22
Summary: The editor should be SMALL!

[]

When I use Megamax C on a 1040ST, I set up a 576K RAM disk which nicely
holds the compiler, linker, libraries, and a bunch of source and object
files.  I hate waiting for the disk, so I also have a communication
program in the RAM disk. The RAM disk cannot be much smaller for serious use.
In what's left (about 200K after GEMDOS and Micro-C-Shell take their tax)
I can run the compiler OR the linker OR the editor, one at a time.
Using microEMACS I can edit 2 or 3 source files simultaneously (about 20K
each) before I run out of memory.

	Everything just fits and I DON'T WANT A BIGGER EDITOR!

I want a smaller one!  My version of microEMACS, which includes decent
word wrap/fill and bracket-balance check, and RESIDENT help screens,
is about 42K.  Small for "real" editors, but a lot bigger than, say,
the 4K RAM-resident screen editor I wrote for the Apple II - in machine
language.  The communication program I usually use on the ST is the PD
"XMOTER(M)", because it has just the features I usually need, and is less
than 5K long!

- Moshe Braner