Can you get away with removing the ${start_url} portion of your limit? Then
you could have:
limit_urls_to: DO_TOPIC \
DO_ROOT \
DO_COMMUNITY
This would provide the OR mechanism that you are looking for, but is
dependant on not needing anything else too specific.
Mike
> On Mon, 10 Jan 2005, Dan Langille wrote:
>
> > Each URL must contain one of the following (actually, there
> are more
> > values in this list, but they have been eliminated to
> simply things):
> >
> > DO_TOPIC
> > DO_ROOT
> > DO_COMMUNITY
> >
> > How can I use that on limit_urls_to? I've been trying this:
> >
> > limit_urls_to: ${start_url}*DO_TOPIC|DO_ROOT|DO_COMMUNITY*
> >
> > There are addiitonal restrictions, but once I get a
> starting point, I
> > think it'll all fall into place.
********************************************************************
This email may contain information which is privileged or confidential. If you
are not the intended recipient of this email, please notify the sender
immediately and delete it without reading, copying, storing, forwarding or
disclosing its contents to any other person
Thank you
Check us out at http://www.bt.com/consulting
********************************************************************
-------------------------------------------------------
The SF.Net email is sponsored by: Beat the post-holiday blues
Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek.
It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt
_______________________________________________
ht://Dig general mailing list: <[email protected]>
ht://Dig FAQ: http://htdig.sourceforge.net/FAQ.html
List information (subscribe/unsubscribe, etc.)
https://lists.sourceforge.net/lists/listinfo/htdig-general
