post 0.8 development

Jan Hudec bulb at
Thu May 11 11:19:26 BST 2006

On Wed, May 10, 2006 at 17:20:10 -0700, John A Meinel wrote:
> Jan Hudec wrote:
> > On Wed, May 10, 2006 at 08:27:33 -0700, John A Meinel wrote:
> >> At one point we started using /@, meaning path/to/branch/@1
> >> I don't remember the official reasons, but we decided to get rid of that
> >> syntax.
> >> I'm fine with the comma. I think we should support escaping it, (as in
> >> http://path/with\,comma/,1..2) But I'm not settled on that.
> > 
> > It's an *URL* -- so http://path/with%2ccomma/,1..2
> [...] 
> Except I am frequently testing bzr inside these temporary directories.
> And it is a little bit difficult to always write the full file:// url
> specifier, just because I have a comma in the path.
> But it isn't terrible.

I'd say relative path in this case is a relative resource pointer as per URL
definition and therefore can be partially URL-escaped. Thus it'd be:
It has the disadvantage that completion won't help you with this, but the
escape character and special character would have that problem no matter what
escaping you choose.

The problem would be a little smaller if escaping was done by doubling the
character, since that would only be one special character instead of two.

						 Jan 'Bulb' Hudec <bulb at>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 189 bytes
Desc: Digital signature
Url : 

More information about the bazaar mailing list