On Tue, Sep 15, 2009 at 1:11 AM, Gary Johnson wrote: > > On 2009-09-15, pansz wrote: >> Tim Chase ??????: >> >> This could be a problem if you compiled vim with the X11 >> >> libraries and your display is not set properly. Try to start >> >> vim with a -X (that's a capital X) and see if there is a >> >> difference. >> > >> > This manifestation of slowness usually triggers a much longer >> > (20-30 second?) delay while vim hunts for X. When you get that >> > long console-vim startup, the -X is the first suggestion. >> >> It won't take 20-30 seconds, I've done an experiment right now: >> >> start vim, it starts instantly. (roughly 0.3 second) >> >> corrupt the X setting, then start vim, it takes 2 seconds to start. >> >> start vim with -X, it starts instantly, (roughly 0.2 second). >> >> repeat the test 3 times and I've got the same result. >> >> I use screen for this test, I corrupt X setting by attach to screen in >> another computer. > > It depends on your operating system. On HP-UX, it took a few > seconds. On Solaris, it took several tens of seconds.
Other env vars, like $SESSION_MANAGER, can contribute greatly to startup time as well, and are also bypassed with -X ~Matt --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
