Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!uunet!husc6!cmcl2!brl-adm!brl-smoke!gwyn From: gwyn@brl-smoke.ARPA (Doug Gwyn ) Newsgroups: comp.sources.wanted,comp.editors Subject: Re: wanted: very simple screen editor Message-ID: <6714@brl-smoke.ARPA> Date: Sun, 22-Nov-87 22:25:35 EST Article-I.D.: brl-smok.6714 Posted: Sun Nov 22 22:25:35 1987 Date-Received: Wed, 25-Nov-87 19:48:15 EST References: <296@ginger.UUCP> <6698@brl-smoke.ARPA> <1484@ttidca.TTI.COM> Reply-To: gwyn@brl.arpa (Doug Gwyn (VLD/VMB)) Organization: Ballistic Research Lab (BRL), APG, MD. Lines: 13 Xref: mnetor comp.sources.wanted:2910 comp.editors:28 In article <1484@ttidca.TTI.COM> kevin@ttidcb.UUCP (Kevin Carothers) writes: >Remember that EMACS, even in it's simplest executable state >(no windows, no multiple file opens, etc...) is a *HUGE* muhonga >(about a quarter mbyte?). Different implementations vary widely in their memory requirements. In fact, when I use EMACS it is usually an old version of Jove, small enough to run on a machine with a 64Kb process size limit (PDP-11). Anyway, on any reasonable system, only one copy of the executable code is resident in memory, no matter how many processes are current. The data space requirements depend on the size of the files being edited; if they're moderately small, there's plenty of memory.