> On Friday 17 December 2010 23:51:27 Tom Link wrote:
>
>>> it's using over half of all startup time
>
>> In this case it won't work because you probably want to load the
>> plugin on every startup, but you can use plugins like asneeded,
>> tplugin to load plugins on demand (e.g. when invoking a command for
>> the first time) or vim-addon-manager or pathogen to enable a plugin
>> after startup. This way you have better control over which plugins
>> are loaded when.
>
> i'm not sure what you're saying won't work
>
> what does work is this: i removed CSApprox from my autoload, doc, and
> plugin paths, and my startup time for vim dropped from 194
> milliseconds to 60 ms -- the last thing i want is more plugins -- i'm
> down to just netrw now -- when i need to see pretty colors i'll use
> gvim
Unless you're starting and stopping Vim hundreds of times per day, the
amount of time it took to write that email and change the way you use
CSApprox dwarfs the time savings you'll ever see from removing it from
startup.
I can see the OP wanting to reduce Vim startup below three seconds --
that's a perceptible delay. But the difference in startup time between
.194 seconds and .060 seconds is barely noticeable.
Probably counter-productive to my case, but if you want to see the
difference:
$ perl -lwe 'print 1; select "","","",0.194; print 2'
$ perl -lwe 'print 1; select "","","",0.060; print 2'
It's only noticeable if you're really focusing on it. It's pretty
insignificant in the scope of other stuff that's happening (hitting
enter or double-clicking, waiting for the window to redraw, etc. etc.).
--
Best,
Ben
--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
No comments:
Post a Comment