On Tue, Sep 27, 2011 at 5:19 PM, Thomas Dickey <address@hidden> wrote:
On Tue, 27 Sep 2011, Graham Lawrence wrote:
Thank you Halász Sándor, the problem is solved.  I did not know that the
file .lynxrc existed. Â I've made the changes I want in that file and lynx
now behaves as desired. Â So if I ever want to make further changes, I'll
do
so directly in .lynxrc
2011/9/27 Halász Sándor <address@hidden>
2011/09/26 11:37 -0700, Graham Lawrence >>>>
As user, I cannot save option changes to disk, so my changes remain in
effect only until the session closes.
As root there is no such problem. Â But I rarely work as root.
I've changed ~/lynx.cfg to have the options I want, but that has no
effect
on lynx's behavior
<<<<<<<<
This last file is read only if somehow you point it out to Lynx, through
environment variable LYNX_CFG or on the command line after "-cfg".
Furthermore, it is intended for general, not particular use. For
particular
use, for Options, the file usually named ".lynxrc" is the one.
If Lynx runs, though, somehwere it found a version of the configuration
file. On the option page there is a link to it from "View the file
lynx.cfg": follow the link and see the full path name.
yes... but lynx.cfg and .lynxrc are distinct files. Â It seems that it
would be nice to have a link to .lynxrc to view for reference, as well
as to reinforce the sense that they're distinct.
Indeed. Also the "order of precedence" in which lynx.cfg, command line
options, and .lynxrc are applied would be a good thing to point out.