RE: [Issue 1291] Changed - Incorrect path in "not a working copy" error message.

> But it complicates those scripts by forcing them to convert
> to local before using paths. Secondly, users could no longer
> cut-n-paste from the output of "svn st" into a shell or
> file-selection dialog.

Paths with "/" work at shell, file-selection, and Windows Explorer
interfaces on my Windows box. I'm currently using XP, but I've been
doing that sort of thing since at least NT 4.0. All the scripting
languages I ever use are happy with "/" too (that would be: perl,
python, Java, sh, and bat).

The only place "/"s cause problems (that I know of) are when handed to
individual programs that use "/" for options. For example, the DOS
"find" command thinks any "/" is about options, and expects paths to use
"\". Visual Basic might be a problem too, I wouldn't know (but I'll bet
a cookie it's OK;-).

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Fri May 9 17:57:20 2003