On Jan 14, 2:55 am, Tony Mechelynck wrote: > cmd.exe and command.com also can't handle the forward slash as a path > separator I don't know about command.com, but cmd.exe certainly CAN handle forward slash perfectly fine. Some things don't work, notably tab- completion of path names and the "copy" command, but other than that cmd.exe seems fully compatible with either '/' or '\' as path separators. At least in Windows XP and above. --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
- Re: shell quote shouldn't depend on shellslash on windo... Tony Mechelynck
- Re: shell quote shouldn't depend on shellslash on ... Yasuhiro MATSUMOTO
- Re: shell quote shouldn't depend on shellslash... Yasuhiro MATSUMOTO
- Re: shell quote shouldn't depend on shells... Bram Moolenaar
- Re: shell quote shouldn't depend on sh... Tony Mechelynck
- Re: shell quote shouldn't depend ... Yasuhiro MATSUMOTO
- Re: shell quote shouldn't dep... Yasuhiro MATSUMOTO
- RE: shell quote shouldn't dep... John Beckett
- Re: shell quote shouldn't dep... Bram Moolenaar
- Re: shell quote shouldn't dep... Yasuhiro MATSUMOTO
- Re: shell quote shouldn't depend on shellslash on ... Ben Fritz
- Re: shell quote shouldn't depend on shellslash... Tony Mechelynck