[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Possible bug regarding spaces in unc paths in 1.6.8

From: David Balažic <david.balazic_at_comtrade.com>
Date: Tue, 15 Jun 2010 11:20:39 +0200

Stefan Küng wrote:
>
> On 08.06.2010 18:20, David Carr wrote:
>
> >>>> Can you reproduce it with the command-line client?
> >>>>
> >>>> Can you reproduce it with an svn:// or http:// URL? The file://
> >>>> protocol on a UNC share isn't exactly a recommended
> configuration in
> >>>> the first place.
> >>>
> >>> Thanks for taking the time to reply. I've tried with the
> command line client and get exactly the same behaviour.
> >>
> >> Then if there is a bug, it's with the Subversion
> libraries, not Tortoise.
> >
> > Absolutely - I presume that's reportable somewhere else.
> I'll do that.
>
> The problem here is that urls must be escaped before they can
> be used by
> the svn library. And Windows doesn't work with file:/// urls on its
> paths if they're escaped.
>
> Imagine the following url:
>
> file:///c:/my folder/repo/trunk/my subfolder
> that url is not escaped. So it won't work with the svn lib.
>
> But if you escape that url, you get:
> file:///c:/my%20folder/repo/trunk/my%20subfolder
>
> which also doesn't work. What *would* work however is this url:
> file:///c:/my folder/repo/trunk/my%20subfolder

What part of Windows has trouble with escaped URLs?
(that would be a serious bug, by the way)

I just did a quicj check by trying file:///C:/Program%20files/
and file:///C:/Program%20files/deleteme.txt in the Windows Run
dialog and in the Explorer location bar, and it works fine.

Regards,
David

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=2621714

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-06-15 11:28:02 CEST

This is an archived mail posted to the TortoiseSVN Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.