Brad wrote:
> > Doesn't all newer Windows versions support the use of forward-slash in
> > place of backslash?
>
> To a certain extent, yes. For instance, the following work at a DOS
> prompt in WinXP when at the root directory:
>
> C:\>cd some/directory/path
> C:\>cd /some/directory/path
>
> However, this second command above does *not* work if one is at any
> depth in the directory tree.
>
> C:\test>cd /some/directory/path
> "The system cannot find the path specified."
>
> The following *will* work from a child directory:
> C:\test>cd ../some/directory/path
That can be attributed to C:/ being the root of the filesystem on
Windows, not /.
I'm not on a Windows box right now, but my guess is that "cd
c:/some/directory/path" would work.
> Similarly, Windows explorer will navigate to any subdirectory of the
> current directory using slashes, buf it you try to go to the root using
> "/", it acts like it's trying to find a web page, and won't go there.
Ok. Since the discussion was based on using forward slash as a path
separator, not a pointer to root-of-fs, I don't think that's a
problem.
> It also sets my display to large icons, rather than the "Details" style,
> which is the default on my system. Closing Explorer and restarting it
> fixes that problem, though.
Ok.
> Support among applications is spotty. Those that use the "standard"
> Windows Open file dialog, or some descendant/variant of it, don't appear
> to recognize the "/" as a valid path separator. MS Word 2003 certainly
> doesn't.
Ok, there's potentially a real problem.
So much for that idea.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri Feb 3 15:04:36 2006