[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev a note on different lynx.cfg/commandline args syntax
From: |
Leonid Pauzner |
Subject: |
Re: lynx-dev a note on different lynx.cfg/commandline args syntax |
Date: |
Mon, 5 Apr 1999 14:41:33 +0400 (MSD) |
4-Apr-99 20:54 address@hidden wrote:
>> Fantastic!
>> I had a primary lynx_cfg.ok which set PARTIAL_THRES:3,
>> included lynx.cfg with PARTIAL_THRES:1,
>> and .lynxrc with partial_thres=-1
>>
>> Only first is active while the second and third ignored. Why?
> I'm not sure - suspect that the only way we'll know is to debug it.
It's incredible, but LIST_FORMAT only works from a primary cfg file only
but INFOSECS work from both primary and included files on my system.
Looks like initialization/re-allocation problem for child read_cfg()...
Does someone can recreate my symptoms?
I have no expirience with run-time debuging in this environment..
>>
>>
>> Lynx.cfg Information (Lynx Version 2.8.2dev.21)
>>
>> This is read from your lynx.cfg file,
>> please "read" distribution's lynx.cfg for more comments.
>>
>> #Your primary configuration c:\tools\lynx\lynx_cfg.ok
>> PARTIAL_THRES:3
>> INCLUDE:c:\tools\lynx\lynx.cfg
>>
>> #<begin c:\tools\lynx\lynx.cfg>
>> STARTFILE:http://lynx.browser.org/
>> HELPFILE:http://www.crl.com/~subir/lynx/lynx_help/lynx_help_main.html
>> DEFAULT_INDEX_FILE:http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html
>> PARTIAL_THRES:1
>> MINIMAL_COMMENTS:TRUE
>> LIST_FORMAT:%a
>> RULE:Fail http:*
>> #<end of c:\tools\lynx\lynx.cfg>
>>
>> STARTFILE:.
>> HELPFILE:file://localhost/c:/lynx/dist28/current/lynx_help/lynx_help_main.html
>> ASSUME_CHARSET:windows-1251
>>
>>
> --
> Thomas E. Dickey
> address@hidden
> http://www.clark.net/pub/dickey