Thanks for the suggestion, Rupert. If you need this functionality right now, one way to achieve it is to set start_url to be a complete list of pages on your site (presumably using the <backquote>included-file<backquote> syntax) and then use max_hop_count. The list of pages on your site could be automatically generated by a perl script on the output of htdump.
In fact, you might like to write that script and send it to us for the /contrib directory. That will keep htdig from getting bloated with too many nice-but-rarely-used features. The limitation of only indexing within the start_url is only in the sample rundig script, which users are free to customise. On Fri, 26 Mar 2004 02:03, Rupert Jones wrote: > I was thinking about the functionality of ht://dig, and what I > would really like to see is the ability to index files one hop away > from the server. Max_hop_count is similar to this, except it counts > the hops away from the start point, not the server (and the > limitations of indexing within the start_url scope makes it awkward > too). -- [EMAIL PROTECTED] ht://Dig developer DownUnder (http://www.htdig.org) ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id70&alloc_id638&op=click _______________________________________________ ht://Dig Developer mailing list: [EMAIL PROTECTED] List information (subscribe/unsubscribe, etc.) https://lists.sourceforge.net/lists/listinfo/htdig-dev
