On 6/3/2010 7:47, Zsbán Ambrus wrote: > On Thu, Jun 3, 2010 at 1:03 PM, Alex Rufon<[email protected]> wrote: >> I tried doing: >> dir c:\\foo\bar >> - and Windows7 command prompt hanged >> >> But doing: >> cd c:\\foo\bar >> changes the directory correctly. >> >> Hehehhe, can we file a Windows 7 bug report? :P ;) LOL > > I don't thunk it's a bug. The backslash behaviour has been there for > ages. These days it's even necessary, because a pathname starting > with a double backslash means a file on the network. > > Note that the cd command could be special because it changes the > directory on only a single drive, so it's reasonable that it parses > the pathname itself to get the drive letter from it. On the other > hand, I just checked and "cd c:\\foo\bar" gives an "Invalid path" > error on DOS 6, so it's not clear to me if that behaviour you mention > is a feature or a bug. > > It might also be interesting what POSIX says about Pathname Resolution: > > A pathname consisting of a single slash shall resolve to the root > directory of the process. [...] A pathname that begins with two > successive slashes may be interpreted in an implementation-defined > manner, although more than two leading slashes shall be treated as a > single slash. > > That said, most unix systems don't use double slashes for special > notation and just take a double leading slash as the root directory > too. > > Ambrus
I tried this on Win7 and got this result: Microsoft Windows [Version 6.1.7600] Copyright (c) 2009 Microsoft Corporation. All rights reserved. C:\Users\me>dir c:\\foo\bar The network location cannot be reached. For information about network troubleshooting, see Windows Help. The response is probably dependent on your system settings. David Mitchell ---------------------------------------------------------------------- For information about J forums see http://www.jsoftware.com/forums.htm
