Author: Robert Hyatt
Date: 08:05:17 02/19/04
Go up one level in this thread
On February 19, 2004 at 04:06:22, Tony Werten wrote: >On February 18, 2004 at 16:09:03, Robert Hyatt wrote: > >>On February 18, 2004 at 15:06:09, Gian-Carlo Pascutto wrote: >> >>>On February 18, 2004 at 13:57:39, Robert Hyatt wrote: >>> >>>>I just typed "emacs" on my dual xeon and it took (according to the time >>>> command) 1.5 seconds to load the _first_ time (I don't use emacs, I use VI). >>>>The next time I typed emacs I hit return and it popped up instantly. >>>> >>>>I then went to one of our sun ultra-sparcs. It took about 3 seconds to pop up >>>>the first time, and then no time thereafter. >>>> >>>>Your 20 seconds nonsense is pure hyperbole with no factual basis, unless you >are using an old 8086 with a floppy disk for storage.. >>> >>>There's a joke that Emacs stands for "Eight megabytes >>>and continously swapping". I'm pretty sure when people >>>came up with it, it was true. Load time may be insignificant >>>these days, text editing is hardly a demanding application >>>either. >>> >>>>No editor under linux has problems either. I just vi'ed the "enormous.pgn" >file with no problems. Took49 seconds to open and close it. 945 megabytes of >>>>ASCII text. >>> >>>Your machine has more than 1G of RAM, I'd wager. Last time I tried, >>>vi performance with > RAM size files was bad. "Less" on the other hand >>>handles them well. It depends on the application. >> >>Right out of /proc/meminfo: >> >>MemTotal: 1030228 kB >> >>one gigabyte. And I had _not_ opened enormous.pgn previously so there was no >>file cached up... > >It is still a question wether or not it is actually loaded, or it just loaded >the first few MB and will load the rest when the editor needs to show it. It isn't a question with VI. It reads the entire file in, and writes it to a temp file. In this case the original was on one drive, the temp file was on another. > >Open the file, then go to the end. If it jumps there immediately it was loaded, >if it takes 3 minutes ... It is instant. ie "G" immediately jumps to the end of the file zero delay. :0 goes back to the beginning. > >That is how I wrote an editor under windows to handle these big files. > >Tony > >> >>> >>>>Let me know how your windows editor does when you open that file... >>> >>>Depends on which one you use. I'm sure there's a lot of ones that do >>>badly, and I know there's at least one that handles it perfectly. >>> >>>IMHO this discussion is as silly as usual. As far as I can gather, >>>Vincent is claiming there are no good editors for Linux, and Steven >>>is claiming all Windows software sucks. >>> >>>Of course they are both right :-) >>> >>>-- >>>GCP >> >>I'm just pointing out that while I don't use Emacs (I use VI because I can >>depend on it being on any unix system I have to deal with) it is not a bad >>editor at all. And it certainly doesn't take 20+ seconds to start up... unless >>you are running off a CD rom maybe...
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.