Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!husc6!think!ames!xanth!john
From: john@xanth.UUCP (John Owens)
Newsgroups: comp.emacs
Subject: Re: GNU Emacs performance
Message-ID: <1201@xanth.UUCP>
Date: Wed, 10-Jun-87 15:38:54 EDT
Article-I.D.: xanth.1201
Posted: Wed Jun 10 15:38:54 1987
Date-Received: Sat, 20-Jun-87 08:54:55 EDT
References: <8706091546.AA01577@icst-cmr.arpa.ARPA>
Organization: Old Dominion University, Norfolk Va.
Lines: 19
Summary: gnu emacs and vi both read in the entire file

In article <8706091546.AA01577@icst-cmr.arpa.ARPA>, rbj@ICST-CMR.ARPA (Root Boy Jim) writes:
> ? >>Is GNU Emacs a CPU hog (at least relative to vi, for example)?
> Paging or swapping is faster than going thru the file system. The only
> thing that would make emacs slower is if the entire file was read in
> before any of it was used.

Yes, but VI also reads in the entire file, as do all other UNIX
editors that I've used.  I would be interested to know of editors that
don't do this - there are times that I'd love to go through a huge
(megabytes) output file with an editor.

So: What editors that run on versions of UNIX only read in the file
when necessary?  How do they get around problems with the file
changing while it is being edited and the like?

-- 
John Owens		Old Dominion University - Norfolk, Virginia, USA
john@ODU.EDU		old arpa: john%odu.edu@RELAY.CS.NET
+1 804 440 4529		old uucp: {seismo,harvard,sun,hoptoad}!xanth!john