Subrepository remapping plan
mg at lazybytes.net
Wed Sep 1 05:08:56 CDT 2010
Dan Villiom Podlaski Christiansen <danchr at gmail.com> writes:
> On 31 Aug 2010, at 13:46, Martin Geisler wrote:
>> Mads said he would like to see the above syntax, i.e., a syntax where
>> users are required to enter correct regular expressions by doubling
>> the backslashes on Windows or by using forward slashes.
>>> OK, I understand. I think that as long as the documentation is clear
>>> in that there may be collisions with folders named "\NN" and that to
>>> avoid them you should use backslashes instead, then there should be
>>> no problem.
>> After thinking about it, I also find it bad that we will have such
>> exceptions to the rules. So I propose we remove the automatic
>> escaping I put in and let people use backslahes at their own risk.
> Wouldn't it be better, usability-wise, to error out when seeing
> backslash-separated paths? It seems to me that it isn't terribly
> helpful to leave users “at their own risk” if what they are doing
> isn't obviously risky ;)
I wanted to simplify things by telling users that this is a normal
regular expression with no funny tricks.
> The backslash is a valid filename character in many operating systems,
> but you could work around that by restricting the check to systems
> where it's the directory separator.
That would be one of the funny tricks I'm trying to avoid... and since
the patterns are (to be) shared between machines on different platforms
this is not a good idea.
Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 197 bytes
Desc: not available
More information about the Mercurial-devel