On Sep 16, 6:46 am, "John Beckett" <[email protected]> wrote:
>
> It looks like a severe problem so I will blurt out some thoughts
> despite not having used Cscope for a few years (and not really
> having a clue).
>
> I think the '2' is error ENOENT
> No such file or directory.
> A component of a specified pathname did not exist,
> or the pathname was an empty string.
>
> so I guess that cscope (or Vim?) thinks that file
> C:/Temp/projname.cscope.out does not exist.
:echo filereadable('C:/Temp/projname.cscope.out') displays 1 in Vim.
>
> I wonder what cscope does with a path like C:/Temp/whatever
> (will the forward slashes work?).
The forward slashes seem to work, they do from cmd.exe anyway.
Just to try it though, I tried connecting in gvim launched with -N -u
NONE so that 'shellslash' and anything else I may have set do not
apply.
Same error.
>
> You might fiddle with setting verbose levels in Vim to see if
> more info is displayed.
>
Nothing more shows with 'verbose' set to 20. Just the E563.
> You say you can navigate the code using cscope.exe, so I assume
> you have used -b to build the database.
I did, using "cscope -b -f projname.cscope.out -i
projname.cscope.files". Is this correct?
Actually, first I tried it without the -b, which (I think) built the
database but also went into the cscope interface.
While we're on this note, does Vim rebuild the database, or provide a
command to do so, or will I need to periodically regenerate it like
with ctags?
> I wonder what directory
> that database is in. I would be inclined to make a new directory
> and put a few test source files in it, then try all your
> commands while working in that directory (so there is no need
> for a path to anything). I would make sure the directory path is
> short with no spaces just for safety, and I would copy
> cscope.exe and sort.exe into that directory so there is no risk
> of any dodgy files coming first in the PATH.
Good idea! I tried it but unfortunately nothing changed. Thinking that
maybe it didn't like the absolute paths in the .files file, I modified
it to make the paths relative. This did not work either.
>
> My old notes include a cryptic message that I obtained file
> env.exe from unxtools and put it early in my PATH. It sets the
> environment for a spawned program and is used by the 2004
> version of Cscope I last used (to call sort.exe?). By the way,
> unxtools is obsolete; if I were looking now I would go
> tohttp://gnuwin32.sourceforge.net/
>
Hmm, I don't see a mention of this anywhere else. I doubt this is an
issue since cscope.exe by itself works fine.
Is there a way to see the exact cscope command that Vim uses with
"cscope add"? Perhaps I should try THAT in cmd.exe to see if I get
more information.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
