[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lynx-dev Re: what to do about html help files.
From: |
Philip Webb |
Subject: |
Re: lynx-dev Re: what to do about html help files. |
Date: |
Thu, 3 Jun 1999 08:47:36 -0400 (EDT) |
990603 Bela Lubkin wrote:
> We have far too many runtime configuration mechanisms. There are
> internal defaults (some compiled in from userdefs.h or config.h, others
> are absolute Lynx defaults); a few environment variables; command-line
> options; lynx.cfg and its included files; .lynxrc; two different options
> menus; and a number of keyboard toggles (like '^V' -> SWITCH_DTD).
> Several of these mechanisms are essentially similar -- parsing of
> options from one place or another. Except that the names of the options
> vary. We have the "-popup" command-line option, "USE_SELECT_POPUPS" in
> lynx.cfg, and "select_popups" in .lynxrc.
> A big part of my vision is to unify these things so that they are
> synonyms, parsed by the same function, accepted in all places and forms.
> The actual names would be stored in structures, as they are now, except
> that each structure entry would have room for multiple strings.
> Furthermore, all of the documentation would be changed to refer only to
> one "preferred" name, except for a section that would explicitly
> document the deprecated names.
-- much useful & interesting detail snipped --
your project is excellent: be encouraged to pursue it as part of 2-8-3.
--
========================,,============================================
SUPPORT ___________//___, Philip Webb : address@hidden
ELECTRIC /] [] [] [] [] []| Centre for Urban & Community Studies
TRANSIT `-O----------O---' University of Toronto