On 24/06/09 16:43, Ben Fritz wrote:
>
>
>
> On Jun 23, 8:46 am, 枫林<[email protected]> wrote:
>> I have found the problem, it is that the "csprg" parameter is set up
>> error. I set it to "C:\Program Files\Vim\vimfiles\cscope.exe" but "csprg"
>> parameter can't include the space in the path name, so gvim can't find the
>> cscope.exe and gvim could work with cscope.
>>
>
> Why do you think csprg can't include the space? Have you tried setting
> it like "set csprg=C:\Program\ Files\Vim\vimfiles\cscope.exe" like
> you'd do with any other option in which you want to include a space?
> Or am I missing something?
I thought the OP had done either that or
let csprg='C:\Program Files\Vim\vimfiles\cscope.exe'
etc., and that it didn't work when trying to execute the 'csprg' setting
as an external prog. If you define it with no spaces in it, you won't
have all the problems I've seen recently on vim_use and/or vim_dev when
trying to invoke a program with a space in it, e.g., Vim would try to
execute
C:\Program Files\Vim\vimfiles\cscope.exe <something>
and Windows would try to execute the program "C:\Program.exe" or
"C:\Program.bat" with the parameters "Files\Vim\vimfiles\cscope.exe" and
"<something>". If you define 8.3 paths (with no spaces in them), or even
replace just the space-containing path component(s) with its/their 8.3
equivalent(s), you don't run into this kind of problems.
Best regards,
Tony.
--
Any stone in your boot always migrates against the pressure gradient to
exactly the point of most pressure.
-- Milt Barber
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
