>
>
> On Oct 1, 7:01 am, Timothy Madden<terminato...@gmail.com> wrote:
>> Hello
>>
>> Anyone has a solution for using cscope if your projects reside in a
>> directory whose name includes spaces ?
>>
>> Looks like cscope outputs in vim:
>> E609: Cscope error: cscope: cannot read trailer offset from
>> file cscope.out
>>
>> This issue is making me so nervous, it is so stupid to be unable to
>> search source code for this name-with-spaces reason.
>>
>> Any ideas ?
>>
>
> On Windows, when building the database, you can probably use short-
> path style names.
>
> E.g. C:\Progra~1\Vim\vim73
>
> I agree it really is annoying that Cscope cannot seem to handle paths
> with spaces. That, and the failure to find function calls like this,
> are my only two real gripes:
>
> var = myfunc
> ( arg1, arg2);
>
Did not know about that, but I have a lot of functions invoked and
written like this. This gets me the feeling that cscope is really such a
poor tool.
In the meantime I discovered Windows NTFS hard links and directory
junctions, created with mklink in cmd.exe, can be useful.
Timothy Madden
--
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