On Wed, Mar 30, 2011 at 1:07 PM, Ben Fritz <fritzophrenic@gmail.com> wrote:
I didn't quite get the tone of the "Wow!". But, yes, it does take a bit of time during the first load to parse through cscope database and build a cross-reference index. Note that its written in pure native Vimscript with no external tools or interpreters. Once serialized, subsequent loads will be extremely fast.
--
On Mar 30, 11:41 am, "hari.rangara...@gmail.com"
<hari.rangara...@gmail.com> wrote:Wow! Does the initial generation/load take more time than the
> Version 1.21 of CCTree allows serialization of loaded cscope databases. So,
> you could run a vim process
> in the background sourcing the script which goes something like:
>
> load_my_cscope.vim:
> :CCTreeLoadDB cscope.out
> :CCTreeSaveXRefDb cctree.out
>
> $ vim -S load_my_cscope.vim
>
> Once it's done, you can load it in your current session with
> :CCTreeLoadXRefDb cctree.out
>
> The second load will take a few minutes usually. I'm currently testing a
> version that allows tracing from disk, requiring
> no load time (If you would like to try that out, let me know).
>
>
>
secondary load (I hope it does)?
I didn't quite get the tone of the "Wow!". But, yes, it does take a bit of time during the first load to parse through cscope database and build a cross-reference index. Note that its written in pure native Vimscript with no external tools or interpreters. Once serialized, subsequent loads will be extremely fast.
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