On 24/06/09 17:46, Ben Fritz wrote:
>
>
>
> On Jun 24, 10:02 am, Tony Mechelynck<[email protected]>
> wrote:
>> 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.
>>
>
> Hmm, it looks like Vim doesn't automatically add the " characters
> then. I assumed it would use 'shellquote' but apparently this is not
> the case. Is there a reason 'shellquote' is not used for csprg,
> makeprg, etc.?
>
> A user could include the quotes manually, correct? E.g. :set csprg="C:
> \Program\ Files\Vim\vimfiles\cscope.exe" would work fine, would it not?
I don't know. OTOH replacing Program Files by PROGRA~1 will work
correctly regardless of backslash-escaping, quoting, or whatever.
Best regards,
Tony.
--
When I was a boy I was told that anybody could become President. Now
I'm beginning to believe it.
-- Clarence Darrow
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
