> I have run 'vim -u NONE' and 'gvim -u NONE' (without any files > opened). The runtime does not get improvement. Since they don't load > the .vimrc file and no files are opened. I think that there might be > due to some other reasons.
A couple other bits of information might help track things down: - what are your build options? Are you running a "huge" build of vim? Loads of add-ons such as python/perl/ruby interpreters included? including the output of ":version" might help. - though unlikely, are your executables on some sort of slow storage? (a network drive, slow CD drive, a USB 1.0 connection, etc) - is it faster if you have a pre-existing copy of (g)vim running at the time? (and thus the executable is in memory already) - if you run (non-g)vim with "-X", is it faster? - though it shouldn't matter *too* much, are you hard-pressed for memory? (memory has only been a problem for me when I was using a full-featured version of vim on an old laptop with only 32 megs of memory) - when you do start up with "-u NONE", what is the output of ":scriptnames" (*should* return nothing)? Hope this gets us enough information to track down the issue. -tim --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
