Matt Wozniski wrote: > Of course, autoload functions aren't a silver bullet, either. If you > have a function that you use every time vim starts (either because > it's called by a plugin, or your vimrc, or a statusline, etc), then > it's almost certainly slower to put it in an autoload script, even if > that's nicer for organization.
[..] I really don't mind vim taking an extra couple of seconds starting up since I know that it will save me considerably more later on. Besides, with split windows and tabs, I tend to stick to a single vim instance that stays up for days or even weeks at a time. BTW, has anyone ever had vim crash on them? ;-) > Personally, I tend to put all the functions for my scripts into > plugins/ and then, once the scripts become too large, or I notice that > a lot of overhead goes into interpreting code that's rarely used, etc, > I start pushing things out to autoload functions. I try to keep my > vimrc free of functions that aren't directly used by it, though. Yes, the "tilde" toggle you and a few others helped me put together a week ago is a good example, since the function is very short and it's more of an extension of the mapping, and said mapping of the toggle to <F6> clearly belongs in my virmc. Gen-Paul. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
