Re: lynx-dev about lynx.cfg

[Foteos Macrides]

David Combs <address@hidden> wrote:
>> From: address@hidden (Michael Sokolov)
><snip>
>>
>> Do something like:
>>
>> strings /usr/local/bin/lynx | grep "lynx.cfg"
>>[...]
>
>I just tried it, got nothing.

 If you start Lynx in TRACE mode (-trace), the
full paths for the cfg and the system and personal
mailcap and extension (suffix) configuration files
are included at the top of the trace log.  If the
user has ability to set those paths, then s/he also
has ability to invoke Lynx in TRACE mode and see how
they are presently set.  You also get information in
the trace log as to whether Lynx actually found and
processed the configuration files.

 This was intended to be the standard, efficient
and cross-platform way of getting this information,
without need to use less efficient, platform-specific,
utilities.

 The trace log output of this information in v2.8
unfortunately has gotten messy and intersperced with
other information, so that it takes more hunting to
find the paths in the trace log, but fortunately the
paths are still there.  Note also that trace logging
doesn't yet work with the lynx_w32 binary, and works
but can't be accessed via the ';' command in the MingW32
binary, but presumeably those problems will be dealt
with in future v2.8.1dev# WIN/NT binaries.

 This is a very Frequently Asked Question.  Since
neither the currently active developers nor the currently
active imparters of knowledge about Lynx appear to be
aware of this, and you, David, are looking for a way to
contribute back to Lynx, perhaps you can take on the
responsibility of answering this FAQ knowledgeably
whenever it comes up.

    Fote
-- 
Foteos Macrides