> 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
Or this (?) from the CSApprox web page:
'If for some reason this transparent method isn't suitable to you (for
instance if your environment can't be configured to meet the
|csapprox-requirements|, or you need to work in Vim 6), another option
is also available: using the |:CSApproxSnapshot| command to create a new
GUI/88-/256-color terminal colorscheme. To use this command, a user
would generally start GVim, choose a colorscheme that sets up the
desired colors, and then use |:CSApproxSnapshot| to create a new
colorscheme based on those colors that works in high color terminals.
This method is more flexible than the transparent mode and works in more
places, but also requires more user intervention, and makes it harder to
deal with colorschemes being updated and such.'
cj
--
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