Re: lynx-dev dev.18 patch: USE_PRETTYSRC, lynx.cfg

[Klaus Weide]

On Sun, 9 Jan 2000, Vlad Harchev wrote:

> PRETTYSRC.ATTRNAME_CASE:
> PRETTYSRC.TAGNAME_CASE:* 
> PRETTYSRC.NO_ANCHOR_NUMBERING:*
>   (ie "PRETTYSRC:NO_ANCHOR_NUMBERING" will directly go to table of options in
> lynx.cfg).
> 
>   This style IMO looks better than FOO_BAR (and may be even better than
> FOO:BAR), but doesn't requires new parsing routines.

Please noooooooo...

Or let's go a step further and write things as
  PRETTYSRC\ATTRNAME_CASE
  PRETTYSRC\TAGNAME_CASE
  PRETTYSRC\NO_ANCHOR_NUMBERING
which no doubt looks better to people with enough exposure to the Windows
registry.

>   Also it seems that such approach could be used for all lynx.cfg options.
>   We could make new synonims for old options, without dropping old options'
> names.

It has become altogether too quiet in lynx.cfg.  We have to shake
things up a bit, or users become too complacent.  Let's give them some
syntactical surprises.  One name per option? - how boring!  Actually,
let's make lynx.cfg look like perl, "there's more than one way to do
it" and all.

  Klaus