On Jan 1, 2008, at 4:58 PM, Zooko wrote:
> HACO wonwin-mcbrootles-computer:~/playground/allmydata/tahoe/trunk-
> hack$ darcs replace --token-
> chars="[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz_-]" \\-
> \\-root\\-uri \\-\\-dir\\-uri docs/configuration.txt
>
> darcs failed: Bad token spec:
> [ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz_-]
> HACO wonwin-mcbrootles-computer:~/playground/allmydata/tahoe/trunk-
> hack$ darcs replace --token-
> chars="[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz_-]"
> XXX YYY docs/configuration.txt
> HACO wonwin-mcbrootles-computer:~/playground/allmydata/tahoe/trunk-
> hack$
To be more explicit, I find it confusing that a bad token spec is not
bad when different OLD and NEW arguments are passed, and I am
doubtful that the problem with the first command-line quoted above is
actually that there is something wrong with its token spec.
I also tried the following variant:
-------
darcs replace --token-
chars="[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz_\-\.]" \
\-\\-root\\-uri \\-\\-dir\\-uri docs/configuration.txt
darcs failed: Bad token spec:
[ABCDEFGHIJKLMNOPQRSTUVWXYZabcdefghijklmnopqrstuvwxyz_\-\.]
-------
and then this:
-------
HACO wonwin-mcbrootles-computer:~/playground/allmydata/tahoe/trunk-
hack$ darcs replace --token-chars="[A-Za-z_0-9\-\.\\]" \\-\\-root\\-
uri \\-\\-dir\\-uri docs/configuration.txt
HACO wonwin-mcbrootles-computer:~/playground/allmydata/tahoe/trunk-hack$
HACO wonwin-mcbrootles-computer:~/playground/allmydata/tahoe/trunk-
hack$ darcs whatsnew docs/configuration.txt
What's new in "docs/configuration.txt":
{
replace ./docs/configuration.txt [A-Za-z_0-9\-\.\] \-\-root\-uri \-\-
dir\-uri
}
-------
which shows, I think, that the problem that yields "Bad token spec"
is that darcs is receiving a backslash in its OLD and NEW arguments
and, um, getting confused somehow.
Regards,
Zooko
_______________________________________________
darcs-devel mailing list
darcs-devel@darcs.net
http://lists.osuosl.org/mailman/listinfo/darcs-devel
