lynx-dev dev.23: extended INCLUDE syntax broken for DOSPATH

[Leonid Pauzner]

> 1999-04-23 (2.8.2dev.23)
> * implement restrictions on options that can be set via the lynx.cfg "include"
>   directive -VH
>   For example, admins may specify
>     include:~/.lynx/colors:COLOR
>     include:~/.lynx/keymap:KEYMAP
>     include:~/.lynx/viewers:VIEWER
>   safely - and be sure that no critical options were altered by those files.
>   The syntax is
>     include:<filename>[:[<OPTNAME>* ] ]
>   More samples:
>     include:~/.lynx/rc:COLOR KEYMAP VIEWER SUFFIX
>     include:/usr/local/lib/lynx-cfg.part: #all settings can be changed

I had two configure files lynx_cfg.ok and included lynx.cfg
on my DOS system for a while.
With dev23 I got a nice *infinite* loop of error messages just on startup:

unknown option name \tools\lynx\lynx.cfg in c:\tools\lynx\lynx_cfg.ok
unknown option name \tools\lynx\lynx.cfg in c:\tools\lynx\lynx_cfg.ok
unknown option name \tools\lynx\lynx.cfg in c:\tools\lynx\lynx_cfg.ok
unknown option name \tools\lynx\lynx.cfg in c:\tools\lynx\lynx_cfg.ok
unknown option name \tools\lynx\lynx.cfg in c:\tools\lynx\lynx_cfg.ok
...

Apparently,
":" after drive letter was assumed as a separator before option name...
I still wonder why the loop is infinite.


>   The patch does this:
>   * It prints warnings to stderr about unknown options specified in the list 
> of
>     allowed options in include command.  When 'o'->'lynx.cfg'->'RELOAD THE
>     CHANGES' is activated, these warnings are also printed on stderr - so the
>     screen will be corrupted if lynx.cfg and included are incorrect.
>   * Only options, allowed for a given file are printed in
>     'o'->'lynx.cfg'->'RELOAD THE CHANGES'.
>   * Fully backward compatible - lines of the form
>       include:filename
>     will work as they did(i.e., if the list of allowed options is not
>     specified, then the included file can use the same set of options, as the
>     file that contained that 'include' command).
>   * If you wish to allow an included file to
>     include others, you must specify 'include' in the list of allowed options.
>     Sample:
>         include:~/.lynx/suffixes:INCLUDE SUFFIX
>     so that users will be able to use 'include' command in '~/.lynx/suffixes'
>     (otherwise included file will be unable to include anything).
>   * Option sets are ANDed. If file lynx.cfg contains:
>         include:/usr/lib/lynx.cfg.0:COLOR SUFFIX VIEWER INCLUDE
>     and /usr/lib/lynx.cfg.0 contains
>         include:/usr/lib/lynx.cfg.1:SUFFIX VIEWER INCLUDE STARTFILE HELPFILE
>     then /usr/lib/lynx.cfg.1 can use the following options:
>       SUFFIX VIEWER INCLUDE