|
From: Eli Z. <el...@gn...> - 2012-10-26 07:15:24
|
> From: Renato Silva <br....@gm...> > Date: Thu, 25 Oct 2012 19:07:29 -0200 > > 2012/10/25 Eli Zaretskii <el...@gn...> > > > > From: Renato Silva <br....@gm...> > > > Date: Thu, 25 Oct 2012 16:46:35 -0200 > > > > > > Right, and even Windows understands forward slashes, for example: > > > cmd.exe> cd ../.. > > > > Only sometimes, so this is unreliable; caveat emptor! E.g.: > > > > D:\usr\eli\data>cd d:/usr > > The system cannot find the path specified. > > D:\usr\eli\data>cd /usr > > The system cannot find the path specified. > > > > (As you can see from the prompt, that directory does exist.) > > > > It looks like it only recognizes relative directory names with forward > > slashes. > > > > > That seems an specific (and annoying) bug with cmd.exe What bug are you alluding to? I see no bug in the examples I posted" "cd", the cmd.exe internal command, is not advertised as supporting forward slashes in file names. We are lucky it sometimes work. > since it seems to work only if you run cd from drive root. What "seems to work only if you run cd from drive root"? Can you show an example of what works and what doesn't work? > NTFS and Windows API, however, should handle them ok. If you mean forward slashes, yes. But the problem is, some commands interpret their arguments before passing them to the APIs. E.g., "cd" supports options, like "/d", so it looks at its argument to see if these switches are specified. |