Re: LYNX-DEV 2-8 help: Help!

[Nelson Henry Eric]

> That's not how it is supposed to work.  This is what's really weird.

Yes, I finally discovered in this discussion what configure's
*intentions* were.  I was thwarting them all along.

>    v
> #ifndef LYNX_CFG_FILE

I was aware of this, and often wondered what it was doing there
because it didn't seem to be doing anything.

> #define LYNX_CFG_FILE /usr/local/lib/lynx.cfg

I have always defined this to "/usr/opt/lynx/lynx.cfg", and that
is what I always got as a default.  Here's where my logic was at
fault, though.  I invariably have a backup -cfg command line switch
or environment variable, so LYNX_CFG_FILE was always "/usr/local/
lib/lynx.cfg", and I just never realized it.  "How stupid can you get!"

> --with-lynx-cfg=/path/to/foo/lynx.cfg, now is --libdir=/path/to/foo 
> so that the LYNX_CFG_FILE define jives with what make install does).
> 
> The only reason for the userdefs.h entry is for other platforms without
> autoconf.  There's no way that userdefs.h should be (or could be)

Once understood, I can see this is the way to go.

> can do a clean build and get the proper behavior back again.  I will
> try following the INSTALLATION instructions strictly as apparently two
> people who do so are getting the same behavior.  Is -DHAVE_CONFIG_H not 

INSTALLATION is wrong because my interpretation of "--libdir" was wrong.
I'll rewrite it as soon as I can.  Tom already clarified it, but in two
places still, my misunderstanding comes through pretty strong.

>  ] behavior I want [own customized lynx.cfg file to be read by default from
>  ] a non-standard directory, i.e., different from /usr/local/lib] under the
>  ] protocol you have implemented, I should copy my customized lynx.cfg into
>  ] the top directory overwriting the distribution one, set the "--libdir" op
[...]
> You can of course run make install and edit the installed lynx.cfg, or
> run lynx with lynx.cfg in the cwd prior to installing a config file at
> all, or any number of other things.  I always thought making Lynx look

This is the specific area that needs to be explained in INSTALLATION, not
so much for the first time user, who would edit the lynx.cfg file before
running configure (if they read the instructions), but for the longtime
user who has a customized lynx.cfg file that they have always just pointed
lynx to, without copying, editing or patching.

> for its config file in sensible places, like this order:
> 
>  * -cfg value,
>  * $LYNX_CFG,
>  * compiled-in location, 
[...]
> Will submit patch for either if people want it, but not for 2.8.  
> Don't let this delay the release.

Sounds good.

__Henry