On 18Jan2007 09:23, Tim Chase <[EMAIL PROTECTED]> wrote: | >It's running on the server, no network involved. Just a standard | >out-of-the box enterprise linux installation (ie installed from rpm) | | Other things one might want to investigate: | | - does it happen when you start with "vim -u NONE" (eliminate | possible plugin/script problems) | | - is your hard-drive set to spin-down after some idle period? | (have had this with a Win32 box, where the 2nd drive spins down | after periods of disuse--if you access it, it has to spin up | which takes a spell) | | - do other apps/editors have similar lag-times? (try ed, pico, | emacs, joe, or whatever and see if they too have problems) | | Answers to these might help narrow down where the problem resides.
One thing I often do is use strace to see where it's spending its time. Open two terminals. Run the "tty" command in one to find out its name. Let us pretent it says "/dev/pts/23". In the other terminal, go: strace -f -e trace=file vim some-text-file 2>/dev/pts/23 Then save the file and watch the second terminal to see where the pauses take place. Cheers, -- Cameron Simpson <[EMAIL PROTECTED]> DoD#743 http://www.cskk.ezoshosting.com/cs/ Life is pleasant. Death is peaceful. It's the transition that's troublesome. - Isaac Asimov
