That doesn't sound right: ".lynxrc" normally contains only the data that
is written by the options form. Perhaps you are talking about doing
something like
export LYNX_CFG=$HOME/.lynxrc
That would work (I think) because the data that the reader for lynx.cfg
is in a different format, but it's not the expected behavior for lynx.
It isn't right at all (sorry all) ... I suppose I was thinking of
lynx -cfg=~/.lynxrc
which I've used as an alias when I don't like a shell provider's setup.
If you go the [O]ptions form route it overwrites .lynxrc, which is the main
reason it does not write to disk by default. This was discussed here last
year. Read the autogenerated .lynxrc file LYOPTIONS generates.
Most of the Options form selections are data that the user might want to
change during a session. I'm not sure that TEXTFIELDS_NEED_ACTIVATION fits
into that category, though arguably "any" setting is a candidate. However,
note that the options menu could grow as large as lynx.cfg if we added all
possibilities.
in which case using .lynxrc as a lynx.cfg surrogate will do nicely, and
bloating LYOPTIONS becomes unnecessary.
Stef
http://caunter.ca/contact.html
_______________________________________________
Lynx-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lynx-dev
