Uh, why are they loading ~/.lynxrc in place of the default
lynx.cfg file? An alternate config file makes sense, but
not .lynxrc . The two files have different formats, and
[somewhat] different purposes; one defines system-wide defaults,
while the other contains user-defined variations on those
defaults.
Try opening both in a text editor; you'll notice lynx.cfg uses
`THIS_SETTING:VALUE' and .lynxrc uses `this_setting=value' -- an
equals sign, not a colon. A lot of items from one file don't
match the equivalent item in the other, if there even is an
equivalent [and in many cases, there isn't].
I've often lamented this difference, as well as the third set (command
line flags). It wouldn't be super hard to merge the formats (I'm
talking about "definition of format", not necessarily the code, which I
haven't checked in a few years). Ignore case, accept '=' and ':',
accept all spellings of options which exist in more than one place.
Then eventually deprecate each option down to a single name (remove
specific documentation of the alternates, replaced with a single table
showing all deprecated names and the current equivalents they're
documented under); change anything which generates one or the other file
to use the one consistent name for each option + a single format.
Something along these lines happened with command line flags some years
back -- options which previously existed in forms like "-this" "-nothis"
were regularized so that "-nowhatever" should work, as well as
"-whatever=0" or "-whatever:0" or "--whatever:0". Hmmm, quick check
shows that "-nowhatever" doesn't work, but lots of other variants do.