On Sun, 2005-11-06 at 20:15 +0100, Vincent Lefevre wrote:
> On 2005-11-05 22:35:10 -0500, Daniel Berlin wrote:
> > Url's starting with "rule://" will be tranformed according to the rules.
> Since this is configurable, why not transforming *any* URL-like string?
Okay, it's clear to me now that when i say "I've hooked this up to
rule:// as a prototype to play with easily", people think i mean more
than "I've hooked this up to rule:// as a prototype to play with easily"
> The end argument delimiter could be given in the rule, e.g.
Really ugly, IMHO.
> The * is a special character that matches anything up to the
> > 2. The rule:// text is deleted as part of processing.
> > 3. Where the occurrence of the text in the match part happens is of no
> > consequence (IE we don't require it occur right after a / or anything).
> > This would be easy to change
> There would be a problem with your example and something like that:
It will be a problem with a lot of things.
ItI'd rather see this written like this (following my comments above):
> ^rule://repo=svn://gcc.gnu.org/svn/gcc 3
> ^rule://branches=rule://repo/branches 2
> The special characters are the following ones:
> 1. At the beginning of the rule, ^ means that the match must occur
> at the beginning of the string.
> 2. * matches anything up to the separator (following *), if there is
> one. For instance, in the 3rd rule above, * would be equivalent
> to [^/]* in a regexp.
> 3. In the replacement text, $[1-9] is replaced by the corresponding
> matched text. $. is replaced by the URL given by svn info.
2 is non-easy without a regex library, we need to discover what it
I'm trying to avoid this.
Anyway, i'm just going to implement prepending transform rules for now,
and a -t syntax, and remove the current rule://
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Sun Nov 6 20:35:35 2005