Re: [Lynx-dev] README.options
Thorsten Glaser wrote: Bela Lubkin dixit: different reasonable assumption would be that Save options to disk only writes out changes made during the _current_ [O]ptions session. No. It says Save options to disk not Save changes in configuration parametres to disc. My mistake, you're right, nobody could ever misunderstand a sentence or have experience with software that does anything differently from Lynx. Bela ___ Lynx-dev mailing list Lynx-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] README.options
It says in the generated .lynxrc: # This file contains options saved from the Lynx Options Screen (normally # with the '' key). There is normally no need to edit this file manually, # since the defaults here can be controlled from the Options Screen, and the # next time options are saved from the Options Screen this file will be # completely rewritten. You have been warned... '' does not do this AFAICT (it does in MBM menu). Did this become different when the save checkbox was introduced (I am not sure when either happened)? The text should either indicate that there is some point to making edits to .lynxrc since it won't get overwritten by default, and the implication that the overwrite occurs can be changed to reflect current behaviour. The text in .lynxrc could indicate this instead: # Warning: # Since you are reading this file you presumably are aware of its potential to # configure the behaviour of the lynx browser, and are able to use a unix text # editor. # You may edit this file to control the startup behaviour of the lynx browser, # but note well that if you choose to save settings to disk from [O]ptions # you will overwrite this file completely and lose any edits you have made. # # However, [O]ptions settings will not be saved to disk unless you select # Save options to disk: [_] before selecting Accept Changes. # This will replace this file and lynx will remember your new settings # and forget your old settings. # | Stef - http://caunter.ca/contact.html ___ Lynx-dev mailing list Lynx-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] README.options
On Sun, 1 May 2005, Stef Caunter wrote: It says in the generated .lynxrc: # This file contains options saved from the Lynx Options Screen (normally # with the '' key). There is normally no need to edit this file manually, # since the defaults here can be controlled from the Options Screen, and the # next time options are saved from the Options Screen this file will be # completely rewritten. You have been warned... '' does not do this AFAICT (it does in MBM menu). That's a reference to the old (non-forms) options screen. (Now that you point it out, I agree it should be updated). -- Thomas E. Dickey http://invisible-island.net ftp://invisible-island.net ___ Lynx-dev mailing list Lynx-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] README.options
Bela Lubkin dixit: different reasonable assumption would be that Save options to disk only writes out changes made during the _current_ [O]ptions session. No. It says Save options to disk not Save changes in configuration parametres to disc. //mirabile -- Hi, does anyone sell openbsd stickers by themselves and not packaged with other products? No, the only way I've seen them sold is for $40 with a free OpenBSD CD. -- Haroon Khalid and Steve Shockley in gmane.os.openbsd.misc ___ Lynx-dev mailing list Lynx-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/lynx-dev
Re: [Lynx-dev] README.options
The idea is to clarify for a new user. The fact that lynx can puzzle by not remembering [O]ptions settings is demystified by associating this with the disk write (or not) to .lynxrc. LYNXOPTIONS only handles a subset of possible config settings for the user. It will be helpful to point out that each of those few settings are overwritten for each Accept with Save to Disk POST to LYNXOPTIONS - reminds me of chmod 0700 rather than chmod u+x (change to follow) ... | Stef - On Wed, 27 Apr 2005, Bela Lubkin wrote: You might want to clarify one point about this. Hitting Accept Changes when Save options to disk is enabled writes out _all_ settings, not just the ones changes in the current [O]ptions dialog. That is, if you did: 1. [O]ptions 2. Change User mode to Advanced 3. Accept Changes 4. [O]ptions 5. Change VI keys to Off 6. Checkmark Save options to disk 7. Accept Changes -- the change made in step 2 has now been written to disk. This will be obvious to _current_ Lynx users, and may seem intuitively obvious to most readers on this list. It is much less obvious to a new user. A different reasonable assumption would be that Save options to disk only writes out changes made during the _current_ [O]ptions session. Bela ___ Lynx-dev mailing list Lynx-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/lynx-dev ___ Lynx-dev mailing list Lynx-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/lynx-dev
[Lynx-dev] README.options
Short howto on [O]ptions and MBM setup; comments/edits welcome. README.options Using the lynx browser [O]ptions configuration tool. General Usage on a unix system: Press O at any time in your lynx session to access this utility page. This is one of several custom system URLs that cause lynx to self-configure. Please note: Ensure and confirm that your [O]ptions session is flushed to disk, by selecting: Save options to disk: [_] before selecting Accept Changes. This freshens your .lynxrc file, which is your default personal configuration for the lynx browser. Otherwise you will only affect settings for your individual session; they aren't remembered next time you use lynx, (since you actually did not tell lynx to remember them). This disk write to .lynxrc is not default behaviour for [O]ptions configurations. The lynx browser tends to tread lightly at first. Note that you must first have permission on your system to create, write to and read from a .lynxrc file in your home directory. Using some of the menu items: User mode controls the amount of on screen help at the bottom of the screen. You get the familiar view of the link target you are on when you use ADVANCED user mode, and this also gives you the most top to bottom screen area. ADVANCED user mode also allows for sub bookmark functionality (see below). The (for now) command line only option --nomargins provides the largest readable left to right screen coverage. Editor is for jumping to vi or whatever you prefer during local file edits and for textarea editing with ^Xe if you are filling out a form while browsing. Please see README.cookies for a brief cookie handling discussion. Multi-bookmarks allows several files to be your bookmarks; it will introduce a browse list of them if they are defined as below. Once the Multi-bookmarks setup on Options is done and has been written out to your .lynxrc (remember to Accept Changes and to Save Changes to disk), in .lynxrc you will see a list of 25 possible other bookmark files (26 letters minus A) - you need to then associate some of them with (meaningful) filenames to get the Multi-bookmark menu. Note that the files must be relative to your home directory. The best way to create and manage them is by using the MultiBookmarkMenu (MBM) configuration tool selectable from the [O]ptions menu. The MBM allows you to describe the sub bookmark, and name a file relative to your home directory that will contain the html for the saved links. You populate one of the lettered sub bookmarks, describe it, and provide a filename. saves the edits, and ^G cancels edits. The sub bookmarks will be accessible by pressing the associated key from a menu when invoking the bookmark choice (lynx -book, or 'V' in a session), or when saving new bookmarks. You can directly access your sub bookmarks by letter key alone by defining sub_bookmarks=ADVANCED in .lynxrc or lynx.cfg, if you have ADVANCED general user mode selected as well. The Multi-bookmark submenu can still be seen in ADVANCED by pressing =, and is always seen in STANDARD mode. They are seen in your .lynxrc like so: multi_bookmarkB=cars,Cars multi_bookmarkC=news,News multi_bookmarkD=sports,Sports Filename precedes description in .lynxrc, whereas in the MBM configuration utility, the description is the left column, and the filename is in the right column displayed. Stef Caunter http://caunter.ca/contact.html http://caunter.ca/README.options ___ Lynx-dev mailing list Lynx-dev@nongnu.org http://lists.nongnu.org/mailman/listinfo/lynx-dev
