On 08/06/09 07:33, Sergey Khorev wrote: > Hi, > >> It's not clear to me whether to repeat this after the sources change, >> I'll have to read the cscope manpage in more detail (it seems to say >> cscope is clever enough to update the database if the sources have >> changed, but can I rely on that?) > > No, Vim executes cscope with "<cscopeprg> -dl -f <databasename>" where > <cscopeprg> is the value of 'cscopeprg' option. > > -d option prevents cscope from rebuilding its database. > >
Ah, I see, thanks. If I invoke cscope -b again with the same arguments, and the database exists, will it "run faster" acording to which sources have been updated and which ones haven't, as mentioned near the top of the manpage? > cscope builds the symbol cross-reference the first time it is used on > the source files for the program being browsed. On a subsequent invoca- > tion, cscope rebuilds the cross-reference only if a source file has > changed or the list of source files is different. When the cross-refer- > ence is rebuilt, the data for the unchanged files are copied from the > old cross-reference, which makes rebuilding faster than the initial > build. If I got the list of files right, and since it is rather complex, it would be nice to have a "cscope" and/or "cscope.out" target in the src/Makefile, don't you think? -- Maybe I should define a user-command for it (:CscopeBuildVim or something) in my vimrc. Best regards, Tony. -- Really heard in court in the U.S.A.: Q.: So, the baby was conceived on 8 August? A.: Yes. Q.: And what were you doing then? A.: Fucking. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
