When running in crawl/traversal mode it would be useful to bypass
the history list. The reason is that during the process one isn't
going to use the history list built, and once the history list maximum
is exceeded one has to bear up with the delay while lynx reports the
error.
In fact, it might be useful to turn off error delays during crawl/traversal,
since user interaction is not available.
Finally, I have a structure where I have an index to a fixed series of
pages and feed this to lynx. For some reason, it appears to be
looping over and over, rather than stopping once the pages have all
been encountered. I'm having a difficult time trying to analyze
what is going wrong here - I thought that the traversal data files
would ensure that lynx only went into a file once.
--
Larry W. Virden <mailto:[EMAIL PROTECTED]>
<URL: http://www.purl.org/NET/lvirden/>
Unless explicitly stated to the contrary, nothing in this posting should
be construed as representing my employer's opinions.
-><-
