On 14/01/09 16:41, Ben Fritz wrote:
>
>
> 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.
Well, actually in DOS with COMMAND.COM you had to change a byte
somewhere in DOS (in segment 40h IIRC) to have / recognized as a path
separator (instead of \ ) and - as a command-line switch prefix (instead
of / ); but many programs didn't check that byte (e.g. when interpreting
paths and options passed on the command-line) so it was better to leave
it at the default.
Best regards,
Tony.
--
FATHER: You only killed the bride's father - that's all -
LAUNCELOT: Oh dear, I didn't really mean to...
FATHER: Didn't mean to? You put your sword right through his head!
LAUNCELOT: Gosh - Is he all right?
"Monty Python and the Holy Grail" PYTHON (MONTY)
PICTURES LTD
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
