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

[Al Gilman]

see also <address@hidden>

>X-URL: http://www.flora.org/lynx-dev/html/month0399/msg00466.html
>
>   
>       Re: lynx-dev multiuser versus single user system use of lynx and
>     _________________________________________________________________
>   
>     * From: address@hidden (Mike Castle)
>     * Date: Thu, 11 Mar 1999 18:54:01 -0600 (CST)
>     * In-Reply-To: <address@hidden> from "Leonid
>       Pauzner" at Mar 1, 99 02:46:54 am

>When saving, the following would happen:
>
>If an item was changed at run time, the personal level would be set to that
>value and command line and run time levels would be cleared.
>
>If the user wanted to, personal level items would be set to command line
>items, and the command line items cleared (This would make command line
>switches pernament in the future... I doubt many would use this though).
>
>Finally, all config file items that are DIFFERENT from the system config
>file would be saved.  There would be two options here:  If wanted to, all
>options could be saved anyway (picture this as a way to generated a system
>file).  Also, all items originally read from config file would be saved
>(this way, if, say an NFS home dir served by various OSs that have slightly
>different system config files but you want an options that's set on one
>system config but not the other, you don't want to be caught by
>surprised... this would probably be the default).

The o)ptions screen had logic to distinguish transient settings from things
that should be that way the next time the program is run.  This should not
be lost.
Please don't just memorize the current settings on exit.  OK to do so on
one confirm, though.  s)ave or r)eview options could be choices.


Al