On Wed, Jan 14, 2009 at 5:55 PM, Tony Mechelynck <antoine.mechely...@gmail.com> wrote: > > On 14/01/09 03:03, Yasuhiro MATSUMOTO wrote: >> Hi all. >> >> It seems that quoting arguments of shebang command depend on shellslash. >> but on windows, cmd.exe or command.com can't treat single quote. >> >> --- test.vimrc --- >> set nocompatible >> set shellslash >> ---------------------- >> > > cmd.exe and command.com also can't handle the forward slash as a path > separator, so you shouldn't set 'sellslash' if you're using them. The > single quote is to be used when using a Unix-like shell on Windows (and, > unlike what you seem to be assuming, a Unix-like shell can be used on > top of cmd.exe or command.com, in which case $COMSPEC will be set to the > Dos/Windows shell, not the Unix-like shell).
Hmm. No. cmd.exe can treat the forward slash as path separator. And shellslash had working good on windows with older version. I guess this is a bug or grade down. still more, netrw can't treat shellshash correctly on latest version. :e http://www.google.com/ the buffer name will be broken like a following with noshellslash. http:\\www.google.com\ Many users hope to use shellslash on windows. Best Regards. -- - Yasuhiro Matsumoto --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
