monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] Re: netsync connection info cleanup


From: Thomas Keller
Subject: Re: [Monotone-devel] Re: netsync connection info cleanup
Date: Wed, 28 Apr 2010 09:40:23 +0200
User-agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.1.9) Gecko/20100317 SUSE/3.0.4-1.1.1 Lightning/1.0b2pre Thunderbird/3.0.4

Am 28.04.2010 07:25, schrieb Derek Scherger:
> On Tue, Apr 27, 2010 at 5:54 PM, Zack Weinberg <address@hidden> wrote:
> 
>> On Tue, Apr 27, 2010 at 4:42 PM, Timothy Brownawell <address@hidden>
>> wrote:
>>>
>>> Is the occasional backslash really that bad? '%' conflicts with
>> urlencoding
>>> (and '*' would only actually glob things if you have some really weirdly
>>> named files), and '?' is probably necessary for file/ssh sync.
>>
>> I think it's more important to avoid characters that are meaningful in
>> URLs (*especially* %) than to avoid characters that are meaningful to
>> the shell.  People expect to have to quote URLs.  Also, I don't like /
>> as a separator when it's not traversing a directory-like hierarchy.
>>
> 
> Agreed, on all counts.
> 
> 
>> So, how about this?
>>
>>  protocol://
>> address@hidden/path/to/database?include,include,-exclude,-exclude
>>
>> should work equally well for mtn (with usher), ssh, and file.  Without
>> usher, you just leave out the /path part.
>>
> 
> +1 (nice and simple)

Ok, I see I get overruled here ;)

>> (Also, ~ in the path part should absolutely have the 'go to home
>> directory' semantic.)
>>
> 
> Agreed here too.
> 
> This proposal doesn't change the meaning of any URL-special characters which
> I think is important. Overloading % + ? = or & would be bad as people
> generally know what they mean in the context of a URL. We could consider
> using the fragment character # in place of the query string separator
> character ? but that's probably splitting hairs. This is a shell-special
> character too (for comments) but it doesn't seem to apply if there's
> non-whitespace immediately preceding it.

I think I have to find another shell...

$ echo mtn://foo.com#foo
zsh: no matches found: mtn://foo.com#foo

So if its only zsh and whatever I try here needs escaping anyways, we
can simply stick to the more common "?" then...

Thomas.

-- 
GPG-Key 0x160D1092 | address@hidden | http://thomaskeller.biz
Please note that according to the EU law on data retention, information
on every electronic information exchange might be retained for a period
of six months or longer: http://www.vorratsdatenspeicherung.de/?lang=en


Attachment: signature.asc
Description: OpenPGP digital signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]