On Sep 15, 11:03 pm, Ben Fritz <[email protected]> wrote:
> But when I then try to use it within Vim with the following command:
>
> cscope add C:/Temp/projname.cscope.out -i C:/Temp/
> projname.cscope.files
>
> I get:
>
> E563: stat(C:/Temp/projname.cscope.out) error: 2
>
> and no cscope connection is made.
>
> C:/Temp/projname.cscope.files contains a list, one per line, of
> absolute paths to every file in the project (generated via script of
> course).
>
> I have cscopeprg set to the absolute path to my cscope executable, and
> cscopeverbose turned on.
>
> If I don't try to specify a file list with -i, I am able to connect to
> and use cscope as long as I call the cscope add command from a
> directory containing code, but with the project code in several
> different directories, this will not work very well for me.
>
Perhaps I don't need the -i at all when using "cscope add" within Vim?
After building the database with cscope.exe, all that information is
in the database file. The text "taken from a version of the cscope man
page" contained in :help cscope-intro says:
> On a subsequent call, cscope
> rebuilds the database only if a source file has changed or the list of
> source files is different.
Does this apply only to cscope.exe, but not to cscope called through
Vim? If Vim never rebuilds the database, there is probably no need for
the -i flag at all.
This should probably be mentioned in the help if it's the case.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
