According to Gordon F. Crago:
> Only after that do I realize that my example config file had an upper case L
> on limit_urls_to:, removing the comment in front of it made me think I was
> enabling the config option but the case typo had another idea.
>
> Deleting limit_normalized and lowercasing limit_urls proved the true source
> of the problem.
>
> My question is, is there any verbose level or other diagnostic that would
> tell me that I had an unrecognized config file entry?
>
> Or is there some way to display the settings the program is actually using
> to build an index?
Both have been suggested before, but neither has been implemented yet.
Giving an error for an "unrecognized" config attribute is a little
tricky, because right now it's valid to define your own attributes for
use by other attributes, or for use in search forms and templates (see
allow_in_form). Changing it now would require a mechanism for declaring
new attributes, and it would also break many existing config files.
Having the programs dump out their attribute settings at a given verbosity
level would be very useful.
--
Gilles R. Detillieux E-mail: <[EMAIL PROTECTED]>
Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil
Dept. Physiology, U. of Manitoba Phone: (204)789-3766
Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930
_______________________________________________
htdig-general mailing list <[EMAIL PROTECTED]>
To unsubscribe, send a message to <[EMAIL PROTECTED]> with a
subject of unsubscribe
FAQ: http://htdig.sourceforge.net/FAQ.html
