Thank you for your advice:). I did this by integrating some profiling command into 1 command/function, as an additional utility of my script. :D
BTW, I found that commented lines also cost some cpu-time. 2009/6/7 Stahlman Family <[email protected]> > > > dr-dr xp wrote: > > A ha It works! Thank you so much. > > > > The "profile! file **" command only affects to script loaded after this > > command. That is a bit inconvenient. > > You can always put the profile commands in your .vimrc if you're trying > to profile something that happens at startup. Alternatively, you could > specify the profile commands with --cmd. (:help --cmd) > > Brett S. > > > > 2009/6/7 Stahlman Family <[email protected]> > > > >> > ...snip... > > > > -- 要了几天饱饭就不记得西北风啥味了 --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
