'O' for options in application, then try to save 'Accept Changes'. Settings never saved. I use lynx not primarily for web work.. but for file navigation/file editing.. but a bug like this shouldn't be in stable. The only way I can make configuration changes is to make my own ~/.lynxrc file << And making this ~/.lynxrc is not clearly documented anywhere.. (not in /usr/share/doc.. and only hinted of it's existence from /etc/lynx-cur/lynx.cfg) eg: " show_dotfiles=on dir_list_style=directories_first file_editor=mcedit "
That's not a lot of information. A few possibilities: a) your home directory is writable by other users b) you're saving the options, but not seeing the ones that are configurable using ENABLE_LYNXRC c) you're attempting to use the same filename for settings (normally ~/.lynxrc) and the configuration (normally lynx.cfg).
That's not a lot of information. A few possibilities: a) your home directory is writable by other users b) you're saving the options, but not seeing the ones that are configurable using ENABLE_LYNXRC c) you're attempting to use the same filename for settings (normally ~/.lynxrc) and the configuration (normally lynx.cfg).
It's mentioned (14 times) in the user guide, for instance: /usr/share/doc/lynx-cur/lynx_help/Lynx_users_guide.html.gz The comments in .lynxrc also tell about it. Starting with no .lynxrc, and no $LYNX_CFG variable to confuse things, I am able to save my settings. Without more information, there's nothing to fix.
It's mentioned (14 times) in the user guide, for instance: /usr/share/doc/lynx-cur/lynx_help/Lynx_users_guide.html.gz The comments in .lynxrc also tell about it. Starting with no .lynxrc, and no $LYNX_CFG variable to confuse things, I am able to save my settings. Without more information, there's nothing to fix.
Thanks thomas.. apparently when i made the file.. i simply pasted " show_dotfiles=on dir_list_style=directories_first file_editor=mcedit " to a new file ~/.lynxrc .. which my default umask is 022 if it would help, there should be a note about this in /usr/share/doc, so that if one creates his own ~/.lynxrc from scratch, that he do a chmod 700 ~/.lynxrc later.. because there's no indication of hints of doing this.. i've had this problem on a few machines, where i'd like to use lynx as a local file navigator and simply make new files but by default i would make these confugration by hand and they would be made writable for the group..i simply would need to chmod them later.. Probaby this is the first application i ever heard of needing a configuration file in ~/ to be like this.. which is rather strange.. (it would be nice to get an explanation for this..)
Actually, I have fetchmail's configuration file, which has to be 400 (perhaps 0600), while ~/.ssh has to be 0700 on some machines (others allow 0750). It's in the changelog - now that I'm reminded, it's not in the manpage or in the generated .lynxrc file (though doing it in the latter wouldn't help much). Perhaps the best place to add details would be in the trace file, so that you could find the reason there. Lynx does say that it can't save the options in this particular case.