Re: lynx-dev Config file reader [PATCH]

[Klaus Weide]

[about significant spaces in lynx.cfg]

On Tue, 24 Nov 1998 address@hidden wrote:

> >   TRUSTED_LYNXCGI:<tab>/usr/local/etc/httpd/cgi-bin/ 
> I don't understand this one - does it matter if someone typed a space
> instead of a tab?

add_trusted() looks specifically for '\t' as a separator.

> >   KEYMAP: :something 
> ok - this one would require some thought. 

Of course one could 0x20 instead.  But is it a good idea to make the
the syntax more restrictive?

> But we don't have anything
> like
>     KEYWORD:<tab><space>:something 
> which would not be doable, right?

Not that I know.  But why change it at all?  The top of lynx.cfg
still says

# NO spaces are allowed between the pair items.

and I don't think that is confusing at all.  If spaces happen
to be ignored in some places, that is using an undocumented
feature.

Some configuration values can be rather arbitrary strings, and
you don't need quotes around them (which makes things simpler
if the strings themselves contain quotes).  LIST_FORMAT: is a good
example where spaces are significant.  If you relax the syntax
now, you have to treat some things specially, and introducing new
such options in the future will be more complicated.


   Klaus