Re: lynx-dev multiuser versus single user system use of lynx and configuration

[Leonid Pauzner]

28-Feb-99 14:16 Mike Castle wrote:
> Amazingly enough Larry W. Virden said:
>> Is there a strategy for determining what parameters are put into 
>> $HOME/.lynxrc
>> versus only being in a lynx.cfg file?  On a single user system, the
>> [deleted]
>> Is this a matter of waiting for some code to be submitted for this, or is
>> it something that's being avoided?

> Well, I want to work on a new configuration mechanism for lynx.  A table
> driven setup that would tie together the global configuration file with
> local .lynxrc and command line options (ie, cookies=no on command line or
> any configuration file would have the same effect).  With ability to save
> in ~/.lynxrc only things that are different from global configuration file
> (to help keep it small), with gettext()'d comments that go into the file
> and possibly be used as a way of building a link off the options page on
> the fly that describes, in native language, what each option is for (or
> perhaps even a link per item).  Also, perhaps the ability to reread

This require a memory for command line switches (and we could not
change most of them on-line, yes?). Now we have in that order:
read_cfg();
read_rc();
<misc code for handling command line switches>

if we collect the latter to a single function, say, read_startup_flags()
we could call these three functions to reread configuration
when we change lynx.cfg from '=' Info Page screen (or new Options menu).

One problem I see - if we change lynx.cfg and change something from Options
Menu but not saved it to .lynxrc - we should update .lynxrc before rereading
the configuration or we got something messed. Well, there is a dependency
problem which may be not so obvious. Probably the whole mechanism
should be changed to make things consistent, you know.

> configuration file on the fly (ie, 2 copies of lynx open, change option in
> one and save to disk and have those new configurations picked up in the
> other session).

> I originally hoped to start on such a project at the beginning of March,
> but my current project at work, which is eating up most of my time, is
> running behind.  So I won't be able to get started as soon as I like.

> Plus, it seems that a new release is starting to settle down.  So perhaps
> holding off on this isn't such a bad thing.  (Some of the things I would
> like to do would be some fairly major changes to the code).

> mrc
> --
>        Mike Castle       Life is like a clock:  You can work constantly
>   address@hidden  and be right all the time, or not work at all
> www.netcom.com/~dalgoda/ and be right at least twice a day.  -- mrc
>     We are all of us living in the shadow of Manhattan.  -- Watchmen