I'm running gvim 7.2.245 on Windows XP (the "cream" build). I was recently assigned a new project at work and decided to give cscope a try to more readily find my way around the new code base.
I downloaded the latest cscope native Windws build from the google code page that has replaced (and is linked from) http://iamphet.nm.ru/cscope/index.html (mentioned in :help cscope near the bottom). >From the cmd.exe prompt, I can successfully navigate the code using: cscope.exe -f C:/Temp/projname.cscope.out -i C:/Temp/ projname.cscope.files 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. I could find no mention of this or any other error code in :help cscope, :help E563, or the cscope man page accessed online at http://cscope.sourceforge.net/cscope_man_page.html. What am I doing wrong? Since cscope works OK by itself, my only thought is that I must be using the Vim interface incorrectly, but I cannot see anything wrong with the commands I issued. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_use" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
