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

[Vlad Harchev]

On Thu, 5 Aug 1999, Ilya Zakharevich wrote:

> >> 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.

Klaus, did you mean wrapping of tag names and attribute names here?

> 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.

 As for me (as the author of prettysrc mode), IMO it would be better to be
able to select from one of three source view modes via lynx.cfg settings (if 
it existed):

 NORMAL
 PREPARSED
 PRETTY

,rather than TRUE/FALSE (so the name of option can be SOURCE_MODE) 
 The reason for why there is no any configuration setting corresponding to it
is the following:
 when I was implementing it, -preparsed existed, and Klaus didn't add any
configuration setting to lynx.cfg to control it, so I didn't add configuration
of psrc mode too.

To Klaus: If you think there are bugs in the implementation of psrc mode,
please tell about them explicitly (rather than saying that it's almost
broken).

 And it would be good if someone added support for following switches in the 
'O'ption menu:
 -force-empty-hrefless-a
 -prettysrc
 -preparsed
 -justify
 -force-html
 -short-url
 -sticky-inputs
 -verbose

And to Klaus: 
 As I understand you, you mean that it will be impossible to request 'old'
source view if PRETTYSRC:TRUE is inserted in lynx.cfg (and seems this is your
most valuable objection)? If yes, then type of -prettysrc should be changed to
the one that allows such change (may be PARSE_SET)?
 
> It is not as if we are running of bits for additional keyactions.  ;-)

 '|' is free for this (shift-\ - sounds very attractive) or Meta-\.

> >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.

 This Klaus' note is correct only if packager set PRETTYSRC to TRUE. IMO
packagers can make much more harm (by seting stupid defaults to lynx.cfg
settings) - and the one we are discussing is not harmfull (provided the user
is able to override settings in lynx.cfg with commandline).
 
>[...] 

 Best regards,
  -Vlad