Re: lynx-dev [PATCH 2.8.3.dev4] Make prettysrc available from lynx.cfg

[Ilya Zakharevich]

>> This makes prettysrc available from lynx.cfg
>> .
>> Btw, what is the logic?  Why some options cannot be set from lynx.cfg?
>
>Turning prettysrc on is more than "enabling" it.  It overrides
>the way '\' acts on text/html files, therefore it makes the normal
>SOURCE display unavailable.  If you 'P'rint from this 'source' view
>(e.g. to disk, to mail), you don't get in general valid text/html
>source.

If you so much concerned about lost possibilities, make it
configurable from Options page - and anyway, using "reload lynx.cfg"
option, my patch makes -prettysrc changable at runtime.  Yet another
reason *for* my patch.

>This is IMO a good reason for not making this configurable to be
>the default '\' behavior.  I was thinking along these lines when
>I implemented -preparsed, but only as a command line option.

I do not see this as a reason to make it not configurable.  If you
want the standard '\' behaviour *in addition* to fancy one, provide an
additional Lynx-keyaction, and bind some key to the action.

It is not as if we are running of bits for additional keyactions.  ;-)

>If lynx can be configured to make prettysrc the default '\' behavior,
>then there is also a much stronger reason to fully document the
>variant behavior in the Users Guide.  Your patch makes it possible
>to configure lynx in a way that breaks normal '\' behavior for
>unsuspecting users, without any warning.

Whoever does *this* can recompile the code with my patch applied ;-).
You propose a reason which looks pretty similar to security by
obscurity.

Ilya