Re: LYNX-DEV Userdefs.h and Lynx.cfg consolidation

[Jim Spath (Webmaster Jim)]

On Wed, 5 Mar 1997, Roger Hill wrote:
> One of the projects I have been contemplating is the consolidation of
> userdefs.h and lynx.cfg.  By this I mean that there are many options in
> userdefs that "can be overridden in lynx.cfg".  That being so, then to my
> mind there is no point in setting them in userdefs.
> So...I want to move all the overridable stuff to the end of userdefs, and
> maybe concentrate the stuff that HAS to be set in userdefs to the top.
> 1. is this a sensible idea?
> 2. if so, is the order of options in userdefs significant?
> 3. if an option is multiply defined in userdefs (by accident, say), which
>    one takes precedence, the first or the last?

This overlaps a bit with our autoconfigure effort, so I'll comment from
that perspective.  Some options could be set by configure flags, so I'd
like to see some development in that direction.  Curses, language
preference, starting html page are some examples.  I went overboard in the
beginning of learning configure by suggesting too many flags, but some
should be there. 

There has also been discussion about inclusion of user preferences
overriding system settings beyond the options page.  See the recent
archives.

Creating an outline that parallels the userdefs sections is probably a
good idea: 

 *  Section 1.  Things you MUST change or verify
 *  Section 2.  Things you should probably check!
 *  Section 3.  Things you should only change after you have a good
 *              understanding of the program!

------
<http://www.cs.indiana.edu/picons/db/users/us/md/lib/bcpl/jspath/face.xbm>
Don't feel you have to take any notice of me.

;
; To UNSUBSCRIBE:  Send a mail message to address@hidden
;                  with "unsubscribe lynx-dev" (without the
;                  quotation marks) on a line by itself.
;