diff options
author | Thomas E. Dickey <dickey@invisible-island.net> | 2018-03-02 21:32:08 +0000 |
---|---|---|
committer | Thomas E. Dickey <dickey@invisible-island.net> | 2018-03-02 21:32:08 +0000 |
commit | 2095e86b2f479242f635b1a3fbd95b5f1ad0ab8f (patch) | |
tree | 183478fb00fda77f2ffeb8592aab4d3843c4442b | |
parent | 952761081f2a2a9631352a3edf2f410e0e36c9be (diff) | |
download | lynx-snapshots-2095e86b2f479242f635b1a3fbd95b5f1ad0ab8f.tar.gz |
snapshot of project "lynx", label v2-8-9dev_16l
-rw-r--r-- | CHANGES | 7 | ||||
-rw-r--r-- | lynx.cfg | 8 | ||||
-rw-r--r-- | lynx_help/Lynx_users_guide.html | 3637 | ||||
-rw-r--r-- | src/LYShowInfo.c | 15 |
4 files changed, 2212 insertions, 1455 deletions
diff --git a/CHANGES b/CHANGES index d75779c8..936c3781 100644 --- a/CHANGES +++ b/CHANGES @@ -1,9 +1,12 @@ --- $LynxId: CHANGES,v 1.936 2018/03/01 22:28:02 tom Exp $ +-- $LynxId: CHANGES,v 1.938 2018/03/02 21:32:08 tom Exp $ =============================================================================== Changes since Lynx 2.8 release =============================================================================== -2018-03-01 (2.8.9dev.17) +2018-03-02 (2.8.9dev.17) +* add a note in lynx.cfg telling how to remove a default key-mapping -TD +* modify "=" command to make it possible to disable margins for the URL string, + by first disabling wrapping using "|" -TD * several fixes for Windows version -TH + fix an abnormal terminate when pressing 'd'(download) on no action button. + work around incompatibility in move() between POSIX and Windows. diff --git a/lynx.cfg b/lynx.cfg index 17e7b82c..ca1d4f88 100644 --- a/lynx.cfg +++ b/lynx.cfg @@ -1,4 +1,4 @@ -# $LynxId: lynx.cfg,v 1.290 2017/08/08 22:34:10 tom Exp $ +# $LynxId: lynx.cfg,v 1.291 2018/03/02 21:30:34 tom Exp $ # lynx.cfg file. # The default placement for this file is /usr/local/lib/lynx.cfg (Unix) # or Lynx_Dir:lynx.cfg (VMS) @@ -2436,6 +2436,9 @@ MINIMAL_COMMENTS:TRUE # (see below). See LYKeymap.c for the complete key mapping. Use the # 'K'eymap command when running Lynx for a list of the _current_ keymappings. # +# You can disable any of the default key-mappings by mapping the key to +# "UNMAPPED". +# # (However, in contrast to the output of 'K' command, # 'H'elp (lynx_help/*.html and lynx_help/keystrokes/*.html files) shows # the default mapping unless you change that files manually, @@ -2476,8 +2479,7 @@ MINIMAL_COMMENTS:TRUE .fi # Other codes not listed above may be available for additional keys, # depending on operating system and libraries used to compile Lynx. -# On some systems, if compiled with recent versions of slang or ncurses -# (if macro USE_KEYMAPS was in effect during compilation), an additional +# On Unix-like systems, if compiled with slang or ncurses, an additional # level of key mapping is supported via an external ".lynx-keymaps" file. # This file, if found in the home directory at startup, will always be # used under those conditions; see lynx-keymaps distributed in the samples diff --git a/lynx_help/Lynx_users_guide.html b/lynx_help/Lynx_users_guide.html index 824d68a5..eec78c54 100644 --- a/lynx_help/Lynx_users_guide.html +++ b/lynx_help/Lynx_users_guide.html @@ -1,4 +1,4 @@ -<!-- $LynxId: Lynx_users_guide.html,v 1.132 2017/10/31 00:32:43 tom Exp $ --> +<!-- $LynxId: Lynx_users_guide.html,v 1.139 2018/03/02 20:34:59 tom Exp $ --> <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> <html> @@ -161,16 +161,18 @@ help</a></h2> <p>Online help is available while viewing any document. Press the - “<em>?</em>” or “<em>H</em>” key (or the - “<em>h</em>” key if vi-like key movement is not on) - to see a list of help topics. See the section titled <a href= - "#IntraDocNav">Navigating hypertext documents with Lynx</a> for - information on navigating through the help files.</p> + “<samp>?</samp>” or “<samp>H</samp>” key + (or the “<samp>h</samp>” key if vi-like key movement + is not on) to see a list of help topics. See the section titled + <a href="#IntraDocNav">Navigating hypertext documents with + Lynx</a> for information on navigating through the help + files.</p> <p>In addition, a summary description of all the Lynx keystroke commands and their key bindings is available by pressing the - “<em>K</em>” key (or the “<em>k</em>” key - if vi-like key movement is not on).</p> + “<samp>K</samp>” key (or the + “<samp>k</samp>” key if vi-like key movement is not + on).</p> <p>If you want to recall recent status-line messages, you can do so by entering the “g” command, followed by @@ -262,16 +264,16 @@ file) for initial display and should you select the link again. If you do select a link again and have reason to desire a new fetch and rendering of the file, use the NOCACHE command, - normally mapped to “<em>x</em>” and - “<em>X</em>”, instead of the <em>right-arrow</em> or - <em>Return</em> key when positioned on the link. You also can + normally mapped to “<samp>x</samp>” and + “<samp>X</samp>”, instead of the <em>right-arrow</em> + or <em>Return</em> key when positioned on the link. You also can force a new fetch and rendering of the currently displayed document via the RELOAD command, normally mapped to <em>Control-R</em>.</p> <p>When a binary file is encountered Lynx will ask the user if he/she wishes to download the file or cancel. If the user selects - “<em>D</em>” for download, Lynx will transfer the + “<samp>D</samp>” for download, Lynx will transfer the file into a temporary location and present the user with a list of options. The only default option is <em>Save to disk</em>, which is disabled if Lynx is running in anonymous mode. @@ -284,12 +286,12 @@ <h2 id="id-Leaving"><a name="Leaving" id="Leaving">Leaving Lynx</a></h2> - <p>To exit Lynx use the “<em>q</em>” command. You + <p>To exit Lynx use the “<samp>q</samp>” command. You will be asked whether you really want to quit. Answering - “<em>y</em>” will exit and “<em>n</em>” - will return you to the current document. Use - “<em>Q</em>” or <em>Control-D</em> to quit without - verification.</p> + “<samp>y</samp>” will exit and + “<samp>n</samp>” will return you to the current + document. Use “<samp>Q</samp>” or <em>Control-D</em> + to quit without verification.</p> <p>[<a href="#ToC-Leaving">ToC</a>]</p> @@ -302,27 +304,35 @@ identify that file by using a Uniform Resource Locator (URL). URLs take the general form:</p> - <p><code>PROTOCOL :// HOST / PATH</code></p> + <blockquote> + <p><code>PROTOCOL :// HOST / PATH</code></p> + </blockquote> <p>where</p> <dl> <dt><code>PROTOCOL</code></dt> - <dd>identifies the communications protocol (<em>scheme</em>) - used by the server that will provide the file. As mentioned - earlier, Lynx (and any WWW client) can interact with a variety - of servers, each with its own protocol.</dd> + <dd> + <p>identifies the communications protocol (<em>scheme</em>) + used by the server that will provide the file. As mentioned + earlier, Lynx (and any WWW client) can interact with a + variety of servers, each with its own protocol.</p> + </dd> <dt><code>HOST</code></dt> - <dd>is the Internet address of the computer system on which the - server is running, and</dd> + <dd> + <p>is the Internet address of the computer system on which + the server is running, and</p> + </dd> <dt><code>PATH</code></dt> - <dd>is a scheme-specific field which for some schemes may - correspond to a directory path and/or filename.</dd> + <dd> + <p>is a scheme-specific field which for some schemes may + correspond to a directory path and/or filename.</p> + </dd> </dl> <p>Here are some sample URLs.</p> @@ -353,7 +363,7 @@ <p>Lynx also will attempt to create a complete URL if you include adequate portions of it in the startfile argument. For - example:<br></p> + example:</p> <pre> 1234.6789.1234.6789.1234.6789.1234.6789.1234.6789.1234.6789.1234.6789.1234.6789 <em>wfbr</em> will be expanded to: @@ -429,31 +439,50 @@ <p>There are also a few other keyboard commands to aid in navigation. The Control and Function keys used for navigation within the current document are described in <a href= - "#MiscKeys"><em>Scrolling and Other useful commands</em></a>. - Some additional commands depend on the fact that Lynx keeps a + "#MiscKeys"><em>Scrolling and Other useful commands</em></a>.</p> + + <p>Some additional commands depend on the fact that Lynx keeps a list of each link you visited to reach the current document, called the <a href="keystrokes/history_help.html">History Page</a>, and a list of all links visited during the current Lynx session, called the <a href= - "keystrokes/visited_help.html">Visited Links Page</a>. The - HISTORY keystroke command, normally mapped to <em>Backspace</em> - or <em>Delete</em>, will show you the <em>History Page</em> of - links leading to your access of the current document. Any of the - previous documents shown in the list may be revisited by - selecting them from the history screen. The VLINKS keystroke - command, normally mapped to uppercase “<em>V</em>”, - will show the <em>Visited Links Page</em>, and you similarly can - select links in that list. The MAIN_MENU keystroke command, - normally mapped to “<em>m</em>” and - “<em>M</em>”, will take you back to the starting - document unless you specified the <em>-homepage=URL</em> option - at the command line. Also, the LIST and ADDRLIST keystroke - commands, normally mapped to “<em>l</em>” and - “<em>A</em>” respectively, will create a compact - lists of all the links in the current document, and they can be - selected via those lists.</p> - - <p>The “<em>i</em>” key presents an index of + "keystrokes/visited_help.html">Visited Links Page</a>.</p> + + <ul> + <li> + <p>The HISTORY keystroke command, normally mapped to + <em>Backspace</em> or <em>Delete</em>, will show you the + <em>History Page</em> of links leading to your access of the + current document. Any of the previous documents shown in the + list may be revisited by selecting them from the history + screen.</p> + </li> + + <li> + <p>The VLINKS keystroke command, normally mapped to uppercase + “<samp>V</samp>”, will show the <em>Visited Links + Page</em>, and you similarly can select links in that + list.</p> + </li> + + <li> + <p>The MAIN_MENU keystroke command, normally mapped to + “<samp>m</samp>” and + “<samp>M</samp>”, will take you back to the + starting document unless you specified the + <em>-homepage=URL</em> option at the command line.</p> + </li> + + <li> + <p>Also, the LIST and ADDRLIST keystroke commands, normally + mapped to “<samp>l</samp>” and + “<samp>A</samp>” respectively, will create a + compact lists of all the links in the current document, and + they can be selected via those lists.</p> + </li> + </ul> + + <p>The “<samp>i</samp>” key presents an index of documents. The default index offered contains many useful links, but can be changed in <em>lynx.cfg</em> or on the command line using the <em>-index=URL</em> switch.</p> @@ -472,17 +501,17 @@ disk.</a></h2> <p>Rendered HTML documents, and plain text files, may be printed - using the “<em>p</em>” command while viewing the - document. After pressing the “<em>p</em>” key a menu - of <em>Print Options</em> will be displayed. The menu will vary - according to several factors. First, some sites set up special - accounts to let users run Lynx to access local information - systems. Typically these accounts require no passwords and do not - require users to identify themselves. As a result such accounts - are called "anonymous" accounts, and their users are considered - "anonymous" users. In most configurations, all Lynx users - (including anonymous users) are able to mail files to themselves - and print the entire file to the screen.</p> + using the “<samp>p</samp>” command while viewing the + document. After pressing the “<samp>p</samp>” key a + menu of <em>Print Options</em> will be displayed. The menu will + vary according to several factors. First, some sites set up + special accounts to let users run Lynx to access local + information systems. Typically these accounts require no + passwords and do not require users to identify themselves. As a + result such accounts are called "anonymous" accounts, and their + users are considered "anonymous" users. In most configurations, + all Lynx users (including anonymous users) are able to mail files + to themselves and print the entire file to the screen.</p> <p>Additional print options are available for users who are using Lynx from their own accounts (that is, so-called "non-anonymous @@ -509,7 +538,7 @@ <p>When viewing HTML documents it is possible to retrieve and display the unrendered (i.e., the original HTML) source of the - document by pressing the “<em>\</em>” (backslash) + document by pressing the “<samp>\</samp>” (backslash) key. Lynx usually caches only the rendering of the document and does not keep the source (unless it is configured to do so in the <a href="#lynx.cfg">lynx.cfg</a> file), so to display the source @@ -543,8 +572,8 @@ <p>In addition, the user must also specify an editor in the <em>Options Menu</em> so that Lynx knows which editor to use. If the file is specified correctly and an editor is defined, then - you may edit documents by using the “<em>e</em>” - command. When the “<em>e</em>” command is entered + you may edit documents by using the “<samp>e</samp>” + command. When the “<samp>e</samp>” command is entered your specified editor is spawned to edit the file. After changes are completed, exit your editor and you will return to Lynx. Lynx will reload and render the file so that changes can be @@ -555,13 +584,13 @@ <h2 id="id-RemoteSource"><a name="RemoteSource" id= "RemoteSource">Downloading and Saving source files.</a></h2> - <p>If the DOWNLOAD keystroke command (“<em>d</em>” or - “<em>D</em>”) is used when positioned on a link for - an HTML, plain text, or binary file, Lynx will transfer the file, - without rendering, into a temporary location and present the user - with a list of options, just as it does when a link for a binary - file of a type for which no viewer has been mapped is - activated.</p> + <p>If the DOWNLOAD keystroke command + (“<samp>d</samp>” or “<samp>D</samp>”) is + used when positioned on a link for an HTML, plain text, or binary + file, Lynx will transfer the file, without rendering, into a + temporary location and present the user with a list of options, + just as it does when a link for a binary file of a type for which + no viewer has been mapped is activated.</p> <p>There is a default <em>Download option</em> of <em>Save to disk</em>. This is disabled if Lynx is running in anonymous mode. @@ -569,11 +598,11 @@ defined in addition to this default in the <em>lynx.cfg</em> file. Using the <em>Save to disk</em> option under the PRINT command after viewing the source of an HTML with the VIEW SOURCE - (<em>\</em>) command will result in a file which differs from the - original source in various ways such as tab characters expanded - to spaces. Lynx formats the source presentation in this mode. On - the other hand, if the DOWNLOAD command is used, the only change - will be that Lynx optionally puts</p> + (<samp>\</samp>) command will result in a file which differs from + the original source in various ways such as tab characters + expanded to spaces. Lynx formats the source presentation in this + mode. On the other hand, if the DOWNLOAD command is used, the + only change will be that Lynx optionally puts</p> <blockquote> <p><!--X-URL: http://www.site.foo/path/to/file.html @@ -602,16 +631,17 @@ or wipe the screen to remove or correct any errors that may be caused by operating system or other messages.</p> - <p>The NOCACHE (“<em>x</em>” or - “<em>X</em>”) command can be used in lieu of ACTIVATE - (<em>Return</em> or <em>right-arrow</em>) to request an uncached - copy and new rendition for the current link, or resubmission of a - FORM, if a cache from a previous request or submission exits. The - request or submission will include <em>Pragma: no-cache</em> and - <em>Cache-Control: no-cache</em> in its headers. Note that FORMs - with POST content will be resubmitted regardless of whether the - NOCACHE or ACTIVATE command is used (see <a href= - "#Forms"><em>Lynx and HTML Forms</em></a>).</p> + <p>The NOCACHE (“<samp>x</samp>” or + “<samp>X</samp>”) command can be used in lieu of + ACTIVATE (<em>Return</em> or <em>right-arrow</em>) to request an + uncached copy and new rendition for the current link, or + resubmission of a FORM, if a cache from a previous request or + submission exits. The request or submission will include + <em>Pragma: no-cache</em> and <em>Cache-Control: no-cache</em> in + its headers. Note that FORMs with POST content will be + resubmitted regardless of whether the NOCACHE or ACTIVATE command + is used (see <a href="#Forms"><em>Lynx and HTML + Forms</em></a>).</p> <p>[<a href="#ToC-ReDo">ToC</a>]</p> @@ -619,23 +649,25 @@ commands</a></h2> <p>Two commands activate searching in Lynx: - “<em>/</em>” and “<em>s</em>”.</p> + “<samp>/</samp>” and + “<samp>s</samp>”.</p> <p>While viewing a normal document use the - “<em>/</em>” command to find a word or phrase within - the current document. The search type will depend on the search - option setting in the <a href="#InteractiveOptions">Options - Menu</a>. The search options are case sensitive and case - insensitive. These searches are entirely local to Lynx.</p> + “<samp>/</samp>” command to find a word or phrase + within the current document. The search type will depend on the + search option setting in the <a href= + "#InteractiveOptions">Options Menu</a>. The search options are + case sensitive and case insensitive. These searches are entirely + local to Lynx.</p> <p>Some documents are designated <em>index documents</em> by virtue of an ISINDEX element in their HEAD section. These documents can be used to retrieve additional information based on searches using words or phrases submitted to an index server. The Lynx statusline will indicate that you are viewing such a - document, and if so, the “<em>s</em>” key will invoke - a statusline prompt to enter a query string. The prompt can be - specified via a PROMPT attribute in the ISINDEX element. + document, and if so, the “<samp>s</samp>” key will + invoke a statusline prompt to enter a query string. The prompt + can be specified via a PROMPT attribute in the ISINDEX element. Otherwise, Lynx will use an internally configured prompt. The address for submitting the search can be specified via an HREF or ACTION attribute. Otherwise, Lynx will use the current document's @@ -646,14 +678,14 @@ Lynx session are saved in a circular buffer, and can be retrieved for re-use by pressing the <em>up-arrow</em> or <em>down-arrow</em> keys at the prompt for a search word or - string. Also, you can use the “<em>n</em>”ext command - to repeat a search with the last-entered search word or phrase, - starting from the current position in the document. The word or - phrase matches will be highlighted throughout the document, but - such highlighting will not persist for new documents, or if the - current document is reloaded. The search cycles to the top of the - document if the word or phrase is not located below your current - position.</p> + string. Also, you can use the “<samp>n</samp>”ext + command to repeat a search with the last-entered search word or + phrase, starting from the current position in the document. The + word or phrase matches will be highlighted throughout the + document, but such highlighting will not persist for new + documents, or if the current document is reloaded. The search + cycles to the top of the document if the word or phrase is not + located below your current position.</p> <p>Although <a href="#Forms">HTML Forms</a> have largely replaced index documents for searches via http servers, they are still @@ -662,7 +694,7 @@ servers. For example, an HTML index document can act as a <em>cover page</em> describing a WAIS database and how to formulate query strings for searching it, and include an element - such as:<br></p> + such as:</p> <pre> <em><ISINDEX PROMPT="Enter WAIS query:" HREF="wais://net.bio.net/biologists-addresses"></em> @@ -677,11 +709,11 @@ "InteractiveOptions">Lynx Options Menu</a></h2> <p>The Lynx <em>Options Menu</em> may be accessed by pressing the - “<em>o</em>” key. It allows you to change options at - runtime, if you need to. Most changes are read from & saved - to your .lynxrc file; those which are not are marked (!) in the - form-based menu (as below). Many other options are stored in the - <a href="#lynx.cfg">lynx.cfg</a> file.</p> + “<samp>o</samp>” key. It allows you to change options + at runtime, if you need to. Most changes are read from & + saved to your .lynxrc file; those which are not are marked (!) in + the form-based menu (as below). Many other options are stored in + the <a href="#lynx.cfg">lynx.cfg</a> file.</p> <p>Lynx supports two styles of Options Menu, key-based & form-based. The form-based menu shown below is an HTML file @@ -798,13 +830,13 @@ <p>An option can be changed by entering the capital letter or character in parentheses for the option you wish to change (e.g., - “<em>E</em>” for Editor or “<em>@</em>” - for show cursor). For fields where text must be entered, simply - enter the text by typing on the keyboard. The <a href= - "keystrokes/edit_help.html">Line Editor</a> can be used to - correct mistakes, and <em>Control-U</em> can be used to erase the - line. When you are done entering a change press the - <em>Return</em> key to get back to the <em>Command?</em> + “<samp>E</samp>” for Editor or + “<samp>@</samp>” for show cursor). For fields where + text must be entered, simply enter the text by typing on the + keyboard. The <a href="keystrokes/edit_help.html">Line Editor</a> + can be used to correct mistakes, and <em>Control-U</em> can be + used to erase the line. When you are done entering a change press + the <em>Return</em> key to get back to the <em>Command?</em> prompt.</p> <p>For fields where you must choose one of two choices, press any @@ -821,8 +853,8 @@ change.</p> <p>When you are done changing options use the - “<em>r</em>” command to return to Lynx or the - “<em>></em>” command to save the options to a + “<samp>r</samp>” command to return to Lynx or the + “<samp>></samp>” command to save the options to a <em>.lynxrc</em> file and return to Lynx.</p> <p>The following table describes the options available on the @@ -831,504 +863,622 @@ <dl> <dt>Assumed document character set</dt> - <dd>This option changes the handling of documents which do not - explicitly specify a charset. Normally Lynx assumes that 8-bit - characters in those documents are encoded according to - iso-8859-1 (the official default for the HTTP protocol). - Unfortunately, many non-English web pages "forget" to include - proper charset info; this option helps you to browse those - broken pages if you know by some means what the charset is. - When the value given here or by an -assume_charset command line - flag is in effect, Lynx will treat documents as if they were - encoded accordingly. This option active when “Raw 8-bit - or CJK Mode” is OFF.</dd> + <dd> + <p>This option changes the handling of documents which do not + explicitly specify a charset. Normally Lynx assumes that + 8-bit characters in those documents are encoded according to + iso-8859-1 (the official default for the HTTP protocol). + Unfortunately, many non-English web pages "forget" to include + proper charset info; this option helps you to browse those + broken pages if you know by some means what the charset + is.</p> + + <p>When the value given here or by an -assume_charset command + line flag is in effect, Lynx will treat documents as if they + were encoded accordingly. This option active when “Raw + 8-bit or CJK Mode” is OFF.</p> + </dd> <dt>Auto Session</dt> - <dt>Lynx can save and restore useful information about your - browsing history. Use this setting to enable or disable the - feature.</dt> + <dd> + <p>Lynx can save and restore useful information about your + browsing history. Use this setting to enable or disable the + feature.</p> + </dd> <dt>Bad HTML messages</dt> <dd> - Suppress or redirect Lynx's messages about "Bad HTML": + <p>Suppress or redirect Lynx's messages about "Bad HTML":</p> <dl> <dt>Ignore</dt> - <dd>do not warn; no details are written to the - trace-file.</dd> + <dd> + <p>do not warn; no details are written to the + trace-file.</p> + </dd> <dt>Add to trace-file</dt> - <dd>add the detailed warning message to the - trace-file.</dd> + <dd> + <p>add the detailed warning message to the + trace-file.</p> + </dd> <dt>Add to LYNXMESSAGES</dt> - <dd>add the detailed warning message to the message page at - "LYNXMESSAGES:".</dd> + <dd> + <p>add the detailed warning message to the message page + at "LYNXMESSAGES:".</p> + </dd> <dt>Warn, point to trace-file</dt> - <dd>show a warning message on the status line; the complete - message is written to the trace-file.</dd> + <dd> + <p>show a warning message on the status line; the + complete message is written to the trace-file.</p> + </dd> </dl> </dd> <dt>Bookmark file</dt> <dd> - When multi-bookmarks is OFF, this is the filename and + <p>When multi-bookmarks is OFF, this is the filename and location of your default personal bookmark file. Enter - “<em>B</em>” to modify the filename and/or + “<samp>B</samp>” to modify the filename and/or location via the <a href="keystrokes/edit_help.html">Line Editor</a>. Bookmark files allow frequently traveled links to - be stored in personal easy to access files. + be stored in personal easy to access files.</p> - <p>Using the “<em>a</em>”dd bookmark link command - (see <a href="#Bookmarks">Lynx bookmarks</a>) you may save - any link that does not have associated POST content into a - bookmark file. All bookmark files must be in or under your + <p>Using the “<samp>a</samp>”dd bookmark link + command (see <a href="#Bookmarks">Lynx bookmarks</a>) you may + save any link that does not have associated POST content into + a bookmark file. All bookmark files must be in or under your account's home directory. If the location specified does not begin with a dot-slash (./), its presence will still be assumed, and referenced to the home directory.</p> <p>When multi-bookmarks is STANDARD or ADVANCED, entering - “<em>B</em>” will invoke a menu of up to 26 + “<samp>B</samp>” will invoke a menu of up to 26 bookmark files (associated with the letters of the English alphabet), for editing their filenames and locations (<em>filepath</em>), and descriptions.</p> <p>Lynx will create bookmark files, if they do not already - exist, when you first “<em>a</em>”dd a bookmark - link to them. However, if you've specified a subdirectory - (e.g., ./BM/lynx_bookmarks.html), that subdirectory must - already exist. Note that on VMS you should use the URL syntax - for the filepath (e.g., <em>not</em> + exist, when you first “<samp>a</samp>”dd a + bookmark link to them. However, if you've specified a + subdirectory (e.g., ./BM/lynx_bookmarks.html), that + subdirectory must already exist. Note that on VMS you should + use the URL syntax for the filepath (e.g., <em>not</em> [.BM]lynx_bookmarks.html).</p> </dd> <dt>Collapse BR tags</dt> - <dd>If <em>Collapse BR tags</em> is turned off, Lynx will not - collapse serial <code>BR</code> tags. If turned on, i.e., - “collapse”, two or more concurrent <code>BR</code>s - will be collapsed into a single line break. Note that the valid - way to insert extra blank lines in HTML is via a - <code>PRE</code> block with only newlines in the block.</dd> + <dd> + <p>If <em>Collapse BR tags</em> is turned off, Lynx will not + collapse serial <code>BR</code> tags. If turned on, i.e., + “collapse”, two or more concurrent + <code>BR</code>s will be collapsed into a single line break. + Note that the valid way to insert extra blank lines in HTML + is via a <code>PRE</code> block with only newlines in the + block.</p> + </dd> <dt>Cookies</dt> - <dd>This option allows you to tell how to handle cookies: - <em>ignore</em>, prompt (<em>ask user</em>) or <em>accept - all</em>.</dd> + <dd> + <p>This option allows you to tell how to handle cookies: + <em>ignore</em>, prompt (<em>ask user</em>) or <em>accept + all</em>.</p> + </dd> <dt>Display Character set</dt> - <dd>This option allows you to set up the default character set - for your specific terminal. The display character set provides - a mapping from the character encodings of viewed documents and - from HTML entities into viewable characters. It should be set - according to your terminal's character set so that characters - other than 7-bit ASCII can be displayed correctly, using - approximations if necessary. You must have the selected - character set installed on your terminal. (Since Lynx now - supports a wide range of platforms it may be useful to note - that cpXXX codepages used within IBM PC computers, and - windows-xxxx within native MS-Windows apps.)</dd> + <dd> + <p>This option allows you to set up the default character set + for your specific terminal. The display character set + provides a mapping from the character encodings of viewed + documents and from HTML entities into viewable characters. It + should be set according to your terminal's character set so + that characters other than 7-bit ASCII can be displayed + correctly, using approximations if necessary. You must have + the selected character set installed on your terminal. (Since + Lynx supports a wide range of platforms it may be useful to + note that cpXXX codepages used within IBM PC computers, and + windows-xxxx within native MS-Windows apps.)</p> + </dd> <dt>Editor</dt> - <dd>The editor to be invoked when editing browsable files, when - sending mail or comments, when preparing a news article for - posting, and for external TEXTAREA editing. The full pathname - of the editor command should be specified when possible.</dd> + <dd> + <p>The editor to be invoked when editing browsable files, + when sending mail or comments, when preparing a news article + for posting, and for external TEXTAREA editing. The full + pathname of the editor command should be specified when + possible.</p> + </dd> <dt>Emacs keys</dt> <dd> - If set to ON then the CTRL-P, CTRL-N, CTRL-F, and CTRL-B keys - will be mapped to up-arrow, down-arrow, right-arrow, and + <p>If set to ON then the CTRL-P, CTRL-N, CTRL-F, and CTRL-B + keys will be mapped to up-arrow, down-arrow, right-arrow, and left-arrow, respectively. Otherwise, they remain mapped to their configured bindings (normally UP_TWO lines, DOWN_TWO - lines, NEXT_PAGE, and PREV_PAGE, respectively). + lines, NEXT_PAGE, and PREV_PAGE, respectively).</p> <p>Note: this has no direct effect on the line-editor's key bindings.</p> </dd> - <dt>Execution links<br> - This deals with execution of local scripts or links:</dt> - - <dd>Local execution is activated when Lynx is first set up. If - it has not been activated you will not see this option in the - <em>Options Menu</em>.</dd> + <dt>Execution links<br></dt> <dd> - When a local execution script is encountered Lynx checks the - users options to see whether the script can be executed. - Users have the following options: + <p>This deals with execution of local scripts or links. Local + execution is activated when Lynx is first set up. If it has + not been activated you will not see this option in the + <em>Options Menu</em>.</p> + + <p>When a local execution script is encountered Lynx checks + the users options to see whether the script can be executed. + Users have the following options:</p> <dl> <dt>Always off</dt> - <dd>Local execution scripts will never be executed</dd> + <dd> + <p>Local execution scripts will never be executed</p> + </dd> <dt>For Local files only</dt> - <dd>Local execution scripts will only be executed if the - script to be executed resides on the local machine, and is - referenced by a URL that begins with - <em>file://localhost</em></dd> + <dd> + <p>Local execution scripts will only be executed if the + script to be executed resides on the local machine, and + is referenced by a URL that begins with + <em>file://localhost</em></p> + </dd> <dt>Always on</dt> - <dd>All local execution scripts will be executed</dd> + <dd> + <p>All local execution scripts will be executed</p> + </dd> </dl> </dd> - <dd>If the users options permit the script to be executed Lynx - will spawn a shell and run the script. If the script cannot be - executed Lynx will show the script within the Lynx window and - inform the user that the script is not allowed to be executed - and will ask the user to check his/her options.</dd> + <dd> + <p>If the users options permit the script to be executed Lynx + will spawn a shell and run the script. If the script cannot + be executed Lynx will show the script within the Lynx window + and inform the user that the script is not allowed to be + executed and will ask the user to check his/her options.</p> + </dd> <dt>FTP sort criteria</dt> - <dd>This option allows you to specify how files will be sorted - within FTP listings. The current options include "<code>By - Filename</code>", "<code>By Size</code>", "<code>By - Type</code>", and "<code>By Date</code>".</dd> + <dd> + <p>This option allows you to specify how files will be sorted + within FTP listings. The current options include "<code>By + Filename</code>", "<code>By Size</code>", "<code>By + Type</code>", and "<code>By Date</code>".</p> + </dd> <dt>HTML error recovery</dt> - <dd>Select the <a href= - "keystrokes/option_help.html#tagsoup">recovery mode</a> used by - Lynx.</dd> + <dd> + <p>Select the <a href= + "keystrokes/option_help.html#tagsoup">recovery mode</a> used + by Lynx.</p> + </dd> <dt>HTTP protocol</dt> - <dd>Normally Lynx negotiates HTTP/1.0, because it does not - support chunked transfer (a requirement for all HTTP/1.1 - clients), although it supports several other features of - HTTP/1.1. You may encounter a server which does not support - HTTP/1.0 which can be used by switching to the later - protocol.</dd> + <dd> + <p>Normally Lynx negotiates HTTP/1.0, because it does not + support chunked transfer (a requirement for all HTTP/1.1 + clients), although it supports several other features of + HTTP/1.1. You may encounter a server which does not support + HTTP/1.0 which can be used by switching to the later + protocol.</p> + </dd> <dt>Invalid-Cookie Prompting</dt> - <dd>This allows you to tell how to handle invalid cookies: - <em>prompt normally</em> to prompt for each cookie, <em>force - yes-response</em> to reply "yes" to each prompt, <em>force - no-response</em> to reply "no" to each prompt.</dd> + <dd> + <p>This allows you to tell how to handle invalid cookies: + <em>prompt normally</em> to prompt for each cookie, <em>force + yes-response</em> to reply "yes" to each prompt, <em>force + no-response</em> to reply "no" to each prompt.</p> + </dd> <dt>Keypad mode</dt> - <dd>This option gives the choice among navigating with the - arrow keys, or having every link numbered so that the links may - be selected or made current by numbers as well as using the - arrow keys, or having every link as well as every form field - numbered so that they can be selected or sought by numbers. See - the<br> - <a href="keystrokes/follow_help.html">Follow link - (or page) number:</a> and<br> - <a href= - "keystrokes/follow_help.html#select-option">Select option (or - page) number:</a><br> - help for more information.</dd> + <dd> + <p>This option gives the choice among navigating with the + arrow keys, or having every link numbered so that the links + may be selected or made current by numbers as well as using + the arrow keys, or having every link as well as every form + field numbered so that they can be selected or sought by + numbers. See the<br> + <a href="keystrokes/follow_help.html">Follow link + (or page) number:</a> and<br> + <a href= + "keystrokes/follow_help.html#select-option">Select option (or + page) number:</a><br> + help for more information.</p> + </dd> <dt>Line edit style</dt> - <dd>This option allows you to set alternative key bindings for - the built-in line editor, if alternative line-edit bindings - have been compiled in. Otherwise, Lynx uses the <a href= - "keystrokes/edit_help.html">Default Binding</a>.</dd> + <dd> + <p>This option allows you to set alternative key bindings for + the built-in line editor, if alternative line-edit bindings + have been compiled in. Otherwise, Lynx uses the <a href= + "keystrokes/edit_help.html">Default Binding</a>.</p> + </dd> <dt>Local directory sort criteria</dt> <dd> - This applies to directory editing. Files and directories can - be presented in the following ways: + <p>This applies to directory editing. Files and directories + can be presented in the following ways:</p> <dl> <dt>Mixed style</dt> - <dd>Files and directories are listed together in - alphabetical order.</dd> + <dd> + <p>Files and directories are listed together in + alphabetical order.</p> + </dd> <dt>Directories first</dt> - <dd>Files and directories are separated into two - alphabetical lists. Directories are listed first.</dd> + <dd> + <p>Files and directories are separated into two + alphabetical lists. Directories are listed first.</p> + </dd> <dt>Files first</dt> - <dd>Files and directories are separated into two - alphabetical lists. Files are listed first.</dd> + <dd> + <p>Files and directories are separated into two + alphabetical lists. Files are listed first.</p> + </dd> </dl> </dd> <dt>Local directory sort order</dt> <dd> - The Options Form also allows you to sort by the file - attributes. + <p>The Options Form also allows you to sort by the file + attributes.</p> <dl> <dt>By name</dt> - <dd>by filename (the default)</dd> + <dd> + <p>by filename (the default)</p> + </dd> <dt>By size</dt> - <dd>by file size, in descending order</dd> + <dd> + <p>by file size, in descending order</p> + </dd> <dt>By date</dt> - <dd>by file modification time, in descending order</dd> + <dd> + <p>by file modification time, in descending order</p> + </dd> <dt>By mode</dt> - <dd>by file protection</dd> + <dd> + <p>by file protection</p> + </dd> <dt>By type</dt> - <dd>by filename suffix, e.g., the text beginning with - “.”</dd> + <dd> + <p>by filename suffix, e.g., the text beginning with + “.”</p> + </dd> <dt>By user</dt> - <dd>by file owner's user-id</dd> + <dd> + <p>by file owner's user-id</p> + </dd> <dt>By group</dt> - <dd>by file owner's group-id</dd> + <dd> + <p>by file owner's group-id</p> + </dd> </dl> </dd> <dt>Multi-bookmarks</dt> - <dd>Lynx supports a default bookmark file, and up to 26 total - bookmark files (see below). When multi-bookmarks is OFF, the - default bookmark file is used for the - “<em>v</em>”iew bookmarks and - “<em>a</em>”dd bookmark link commands. If - multi-bookmark support is available in your account, the - setting can be changed to STANDARD or ADVANCED. In STANDARD - mode, a menu of available bookmarks always is invoked when you - seek to view a bookmark file or add a link, and you select the - bookmark file by its letter token (see <em>Bookmark file</em>, - below) in that menu. In ADVANCED mode, you instead are prompted - for the letter of the desired bookmark file, but can enter - “<em>=</em>” to invoke the STANDARD selection menu, - or <em>RETURN</em> for the default bookmark file.</dd> + <dd> + <p>Lynx supports a default bookmark file, and up to 26 total + bookmark files (see below). When multi-bookmarks is OFF, the + default bookmark file is used for the + “<samp>v</samp>”iew bookmarks and + “<samp>a</samp>”dd bookmark link commands. If + multi-bookmark support is available in your account, the + setting can be changed to STANDARD or ADVANCED. In STANDARD + mode, a menu of available bookmarks always is invoked when + you seek to view a bookmark file or add a link, and you + select the bookmark file by its letter token (see + <em>Bookmark file</em>, below) in that menu. In ADVANCED + mode, you instead are prompted for the letter of the desired + bookmark file, but can enter “<samp>=</samp>” to + invoke the STANDARD selection menu, or <em>RETURN</em> for + the default bookmark file.</p> + </dd> <dt>Password for anonymous ftp</dt> - <dd>If this is blank, Lynx will use your personal mail address - as the anonymous ftp password. Though that is the convention, - some users prefer to use some other string which provides less - information. If the given value lacks a "@", Lynx also will use - your computer's hostname as part of the password. If both this - field and the personal mail address are blank, Lynx will use - your $USER environment variable, or "WWWuser" if even the - environment variable is unset.</dd> + <dd> + <p>If this is blank, Lynx will use your personal mail address + as the anonymous ftp password. Though that is the convention, + some users prefer to use some other string which provides + less information. If the given value lacks a "@", Lynx also + will use your computer's hostname as part of the password. If + both this field and the personal mail address are blank, Lynx + will use your $USER environment variable, or "WWWuser" if + even the environment variable is unset.</p> + </dd> <dt>Pause when showing message</dt> - <dd>If set to "off", this overrides the INFOSECS setting in - lynx.cfg, to eliminate pauses when displaying informational - messages, like the "-nopause" command line option.</dd> + <dd> + <p>If set to "off", this overrides the INFOSECS setting in + lynx.cfg, to eliminate pauses when displaying informational + messages, like the "-nopause" command line option.</p> + </dd> <dt>Personal mail address</dt> - <dd>This mail address will be used to help you send files to - yourself and will be included as the From: address in any mail - or comments that you send. It will also be sent as the From: - field in HTTP or HTTPS requests if inclusion of that header has - been enabled via the NO_FROM_HEADER definition in <a href= - "#lynx.cfg">lynx.cfg</a> (the compilation default is not to - send the header), or via the <em>-from</em> command line - toggle.</dd> + <dd> + <p>This mail address will be used to help you send files to + yourself and will be included as the From: address in any + mail or comments that you send. It will also be sent as the + From: field in HTTP or HTTPS requests if inclusion of that + header has been enabled via the NO_FROM_HEADER definition in + <a href="#lynx.cfg">lynx.cfg</a> (the compilation default is + not to send the header), or via the <em>-from</em> command + line toggle.</p> + </dd> <dt>Personal mail name</dt> - <dd>This mail name will be included as the "X-Personal_Name" - field in any mail or comments that you send if that header has - not been disabled via the NO_ANONYMOUS_EMAIL definition in - <a href="#lynx.cfg">lynx.cfg</a>.</dd> + <dd> + <p>This mail name will be included as the "X-Personal_Name" + field in any mail or comments that you send if that header + has not been disabled via the NO_ANONYMOUS_EMAIL definition + in <a href="#lynx.cfg">lynx.cfg</a>.</p> + </dd> <dt>Popups for select fields</dt> - <dd>Lynx normally uses a popup window for the OPTIONs in form - SELECT fields when the field does not have the MULTIPLE - attribute specified, and thus only one OPTION can be selected. - The use of popup windows can be disabled by changing this - setting to OFF, in which case the OPTIONs will be rendered as a - list of radio buttons. Note that if the SELECT field does have - the MULTIPLE attribute specified, the OPTIONs always are - rendered as a list of checkboxes.</dd> + <dd> + <p>Lynx normally uses a popup window for the OPTIONs in form + SELECT fields when the field does not have the MULTIPLE + attribute specified, and thus only one OPTION can be + selected. The use of popup windows can be disabled by + changing this setting to OFF, in which case the OPTIONs will + be rendered as a list of radio buttons. Note that if the + SELECT field does have the MULTIPLE attribute specified, the + OPTIONs always are rendered as a list of checkboxes.</p> + </dd> <dt>Preferred document language</dt> - <dd>The language you prefer if multi-language files are - available from servers. Use RFC 1766 abbreviations, e.g., en - for English, fr for French, etc. Can be a comma-separated list, - which may be interpreted by servers as descending order of - preferences. You can also make your order of preference - explicit by using q factors as defined by the HTTP protocol, - for servers which understand it, for example: - da, en-gb;q=0.8, en;q=0.7</dd> + <dd> + <p>The language you prefer if multi-language files are + available from servers. Use RFC 1766 abbreviations, e.g., en + for English, fr for French, etc. Can be a comma-separated + list, which may be interpreted by servers as descending order + of preferences. You can also make your order of preference + explicit by using q factors as defined by the HTTP protocol, + for servers which understand it, for example: + da, en-gb;q=0.8, en;q=0.7</p> + </dd> <dt>Preferred document charset</dt> - <dd>The character set you prefer if sets in addition to - ISO-8859-1 and US-ASCII are available from servers. Use MIME - notation (e.g., ISO-8859-2) and do not include ISO-8859-1 or - US-ASCII, since those values are always assumed by default. Can - be a comma-separated list, which may be interpreted by servers - as descending order of preferences. You can also make your - order of preference explicit by using q factors as defined by - the HTTP protocol, for servers which understand it, for - example: iso-8859-5, utf-8;q=0.8</dd> + <dd> + <p>The character set you prefer if sets in addition to + ISO-8859-1 and US-ASCII are available from servers. Use MIME + notation (e.g., ISO-8859-2) and do not include ISO-8859-1 or + US-ASCII, since those values are always assumed by default. + Can be a comma-separated list, which may be interpreted by + servers as descending order of preferences. You can also make + your order of preference explicit by using q factors as + defined by the HTTP protocol, for servers which understand + it, for example: iso-8859-5, utf-8;q=0.8</p> + </dd> <dt>Preferred encoding</dt> - <dd>When doing a GET, lynx tells what types of compressed data - it can decompress (the "Accept-Encoding:" string). This is - determined by compiled-in support for decompression or external - decompression programs. Use this option to select none, one or - all of the supported decompression types.</dd> + <dd> + <p>When doing a GET, lynx tells what types of compressed data + it can decompress (the "Accept-Encoding:" string). This is + determined by compiled-in support for decompression or + external decompression programs. Use this option to select + none, one or all of the supported decompression types.</p> + </dd> <dt>Preferred media type</dt> <dd> - When doing a GET, lynx lists the MIME types which it knows + <p>When doing a GET, lynx lists the MIME types which it knows how to present (the "Accept:" string). Depending on your system configuration, the mime.types or other data given by the GLOBAL_EXTENSION_MAP may include many entries that lynx really does not handle. Use this option to select one of the built-in subsets of the MIME types that lynx could list in - the Accept. + the Accept.</p> <dl> <dt>Accept lynx's internal types</dt> - <dd>list only the types that are compiled into lynx.</dd> + <dd> + <p>list only the types that are compiled into lynx.</p> + </dd> <dt>Also accept lynx.cfg's types</dt> - <dd>lists types defined in lynx.cfg, e.g., the VIEWER and - Cern RULE or RULESFILE settings.</dd> + <dd> + <p>lists types defined in lynx.cfg, e.g., the VIEWER and + Cern RULE or RULESFILE settings.</p> + </dd> <dt>Also accept user's types</dt> - <dd>lists types from the PERSONAL_EXTENSION_MAP setting in - lynx.cfg</dd> + <dd> + <p>lists types from the PERSONAL_EXTENSION_MAP setting in + lynx.cfg</p> + </dd> <dt>Also accept system's types</dt> - <dd>lists types from the GLOBAL_EXTENSION_MAP setting in - lynx.cfg</dd> + <dd> + <p>lists types from the GLOBAL_EXTENSION_MAP setting in + lynx.cfg</p> + </dd> <dt>Accept all types</dt> - <dd>adds the types that are in lynx's built-in tables for - external programs that may be used to present a - document.</dd> + <dd> + <p>adds the types that are in lynx's built-in tables for + external programs that may be used to present a + document.</p> + </dd> </dl> </dd> <dt>Raw 8-bit or CJK Mode</dt> - <dd>Whether 8-bit characters are assumed to correspond with the - display character set and therefore are processed without - translation via the chartrans conversion tables. Should be ON - by default when the display character set is one of the Asian - (CJK) sets and the 8-bit characters are Kanji multibytes. - Should be OFF for the other display character sets, but can be - turned ON when the document's charset is unknown (e.g., is not - ISO-8859-1 and no charset parameter was specified in a reply - header from an HTTP server to indicate what it is) but you know - by some means that you have the matching display character set - selected. Should be OFF when an Asian (CJK) set is selected but - the document is ISO-8859-1 or another “assumed document - character set”. The setting also can be toggled via the - RAW_TOGGLE command, normally mapped to - “<em>@</em>”, and at startup via the <em>-raw</em> - switch.</dd> + <dd> + <p>Tells Lynx whether 8-bit characters are assumed to + correspond with the display character set and therefore are + processed without translation via the chartrans conversion + tables:</p> + + <ul> + <li>Should be ON by default when the display character set + is one of the Asian (CJK) sets and the 8-bit characters are + Kanji multibytes.</li> + + <li>Should be OFF for the other display character sets, but + can be turned ON when the document's charset is unknown + (e.g., is not ISO-8859-1 and no charset parameter was + specified in a reply header from an HTTP server to indicate + what it is) but you know by some means that you have the + matching display character set selected.</li> + + <li>Should be OFF when an Asian (CJK) set is selected but + the document is ISO-8859-1 or another “assumed + document character set”.</li> + </ul> + + <p>The setting also can be toggled via the RAW_TOGGLE + command, normally mapped to “<samp>@</samp>”, and + at startup via the <em>-raw</em> switch.</p> + </dd> <dt>Send User-Agent header</dt> - <dd>Controls whether the user-agent string will be sent.</dd> + <dd> + <p>Controls whether the user-agent string will be sent.</p> + </dd> <dt>Session file</dt> - <dd>Define the file name where lynx will store user sessions. - This setting is used only when <em>Auto Session</em> is - enabled.</dd> + <dd> + <p>Define the file name where lynx will store user sessions. + This setting is used only when <em>Auto Session</em> is + enabled.</p> + </dd> <dt>Show color</dt> - <dd>This option will be present if color support is available. - If set to ON or ALWAYS, color mode will be forced on if - possible. If (n)curses color support is available but cannot be - used for the current terminal type, selecting ON is rejected - with a message. If set to OFF or NEVER, color mode will be - turned off.<br> - ALWAYS and NEVER are not offered in anonymous accounts. If - saved to a <em>.lynxrc</em> file in non-anonymous accounts, - ALWAYS will cause Lynx to set color mode on at startup if - supported. If Lynx is built with the slang library, this is - equivalent to having included the <em>-color</em> command line - switch or having the <em>COLORTERM</em> environment variable - set. If color support is provided by curses or ncurses, this is - equivalent to the default behavior of using color when the - terminal type supports it. If (n)curses color support is - available but cannot be used for the current terminal type, the - preference can still be saved but will have no effect.<br> - A saved value of NEVER will cause Lynx to assume a monochrome - terminal at startup. It is similar to the <em>-nocolor</em> - switch, but (when the slang library is used) can be overridden - with the <em>-color</em> switch.<br> - If the setting is OFF or ON when the current options are saved - to a <em>.lynxrc</em> file, the default startup behavior is - retained, such that color mode will be turned on at startup - only if the terminal info indicates that you have a - color-capable terminal, or (when the slang library is used) if - forced on via the <em>-color</em> switch or <em>COLORTERM</em> - variable. This default behavior always is used in anonymous - accounts, or if the <em>option_save</em> restriction is set - explicitly. If for any reason the startup color mode is - incorrect for your terminal, set it appropriately on or off via - this option.</dd> + <dd> + <p>This option will be present if color support is available. + If set to ON or ALWAYS, color mode will be forced on if + possible. If (n)curses color support is available but cannot + be used for the current terminal type, selecting ON is + rejected with a message. If set to OFF or NEVER, color mode + will be turned off.</p> + + <p>ALWAYS and NEVER are not offered in anonymous accounts. If + saved to a <em>.lynxrc</em> file in non-anonymous accounts, + ALWAYS will cause Lynx to set color mode on at startup if + supported. If Lynx is built with the slang library, this is + equivalent to having included the <em>-color</em> command + line switch or having the <em>COLORTERM</em> environment + variable set. If color support is provided by curses or + ncurses, this is equivalent to the default behavior of using + color when the terminal type supports it. If (n)curses color + support is available but cannot be used for the current + terminal type, the preference can still be saved but will + have no effect.</p> + + <p>A saved value of NEVER will cause Lynx to assume a + monochrome terminal at startup. It is similar to the + <em>-nocolor</em> switch, but (when the slang library is + used) can be overridden with the <em>-color</em> switch.</p> + + <p>If the setting is OFF or ON when the current options are + saved to a <em>.lynxrc</em> file, the default startup + behavior is retained, such that color mode will be turned on + at startup only if the terminal info indicates that you have + a color-capable terminal, or (when the slang library is used) + if forced on via the <em>-color</em> switch or + <em>COLORTERM</em> variable. This default behavior always is + used in anonymous accounts, or if the <em>option_save</em> + restriction is set explicitly. If for any reason the startup + color mode is incorrect for your terminal, set it + appropriately on or off via this option.</p> + </dd> <dt>Show cursor</dt> - <dd>Lynx normally hides the cursor by positioning it to the - right and if possible the very bottom of the screen, so that - the current link or OPTION is indicated solely by its - highlighting or color. If show cursor is set to ON, the cursor - will be positioned at the left of the current link or OPTION. - This is helpful when Lynx is being used with a speech or - braille interface. It also is useful for sighted users when the - terminal cannot distinguish the character attributes used to - distinguish the current link or OPTION from the others in the - screen display.</dd> + <dd> + <p>Lynx normally hides the cursor by positioning it to the + right and if possible the very bottom of the screen, so that + the current link or OPTION is indicated solely by its + highlighting or color. If show cursor is set to ON, the + cursor will be positioned at the left of the current link or + OPTION. This is helpful when Lynx is being used with a speech + or braille interface. It also is useful for sighted users + when the terminal cannot distinguish the character attributes + used to distinguish the current link or OPTION from the + others in the screen display.</p> + </dd> <dt>Show dot files</dt> - <dd>If display/creation of hidden (dot) files/directories is - enabled, you can turn the feature on or off via this - setting.</dd> + <dd> + <p>If display/creation of hidden (dot) files/directories is + enabled, you can turn the feature on or off via this + setting.</p> + </dd> <dt>Show images</dt> <dd> - This allows you to select the way in which Lynx shows image - links. These are the available selections: + <p>This allows you to select the way in which Lynx shows + image links. These are the available selections:</p> <ul> <li><em>ignore</em> to suppress the links altogether,</li> @@ -1338,21 +1488,23 @@ <li><em>as links</em>, which allows you to use an external viewer</li> - </ul> + </ul><br> </dd> <dt>Show scrollbar</dt> - <dd>This allows you to enable (show) or disable (hide) the - scrollbar on the right-margin of the display. This feature is - available with ncurses or slang libraries.</dd> + <dd> + <p>This allows you to enable (show) or disable (hide) the + scrollbar on the right-margin of the display. This feature is + available with ncurses or slang libraries.</p> + </dd> <dt>Show transfer rate</dt> <dd> - This allows you to select the way in which Lynx shows its + <p>This allows you to select the way in which Lynx shows its progress in downloading large pages. It displays its progress - in the status line. These are the available selections: + in the status line. These are the available selections:</p> <ul> <li>Do not show rate</li> @@ -1366,121 +1518,147 @@ <li>Pause when showing message</li> <li>Show transfer rate</li> - </ul> + </ul><br> </dd> <dt>SSL Prompting</dt> - <dd>This allows you to tell how to handle errors detected in - SSL connections <em>prompt normally</em> to prompt for each - cookie, <em>force yes-response</em> to reply "yes" to each - prompt, <em>force no-response</em> to reply "no" to each - prompt.</dd> + <dd> + <p>This allows you to tell how to handle errors detected in + SSL connections <em>prompt normally</em> to prompt for each + cookie, <em>force yes-response</em> to reply "yes" to each + prompt, <em>force no-response</em> to reply "no" to each + prompt.</p> + </dd> <dt>Trim blank lines</dt> - <dd>If <em>Trim blank lines</em> is turned off, Lynx will not - trim trailing blank lines from the document. Also, Lynx will - not collapse <code>BR</code>-tags onto the previous line when - it happens to be empty as part of the <em>Collapse BR tags</em> - feature.</dd> + <dd> + <p>If <em>Trim blank lines</em> is turned off, Lynx will not + trim trailing blank lines from the document. Also, Lynx will + not collapse <code>BR</code>-tags onto the previous line when + it happens to be empty as part of the <em>Collapse BR + tags</em> feature.</p> + </dd> <dt>Type of Search</dt> - <dd>Searching type has two possible values: CASE INSENSITIVE - (default) and CASE SENSITIVE. The searching type effects - inter-document searches only, and determines whether searches - for words within documents will be done in a case-sensitive or - case-insensitive manner.</dd> + <dd> + <p>Searching type has two possible values: CASE INSENSITIVE + (default) and CASE SENSITIVE. The searching type effects + inter-document searches only, and determines whether searches + for words within documents will be done in a case-sensitive + or case-insensitive manner.</p> + </dd> <dt>Use HTML5 charset replacements</dt> - <dd>This option allows lynx to treat pages with ISO-8859-1 - (Latin1) or ASCII encoding as if they were Windows 1252. That - allows a few punctuation characters to be shown.</dd> + <dd> + <p>This option allows lynx to treat pages with ISO-8859-1 + (Latin1) or ASCII encoding as if they were Windows 1252. That + allows a few punctuation characters to be shown.</p> + </dd> <dt>Use locale-based character set</dt> - <dd>This option allows you to request lynx to obtain a MIME - name from the operating system which corresponds to your locale - setting. If successful, it overrides the normal setting of the - display character set.</dd> + <dd> + <p>This option allows you to request lynx to obtain a MIME + name from the operating system which corresponds to your + locale setting. If successful, it overrides the normal + setting of the display character set.</p> + </dd> <dt>Underline links</dt> - <dd>Use underline-attribute rather than bold for links.</dd> + <dd> + <p>Use underline-attribute rather than bold for links.</p> + </dd> <dt>Use Passive FTP</dt> - <dd>This allows you to change whether Lynx uses passive ftp - connections.</dd> + <dd> + <p>This allows you to change whether Lynx uses passive ftp + connections.</p> + </dd> <dt>User Agent header</dt> - <dd>The header string which Lynx sends to HTTP servers to - indicate the User-Agent is displayed here. Changes may be - disallowed via the <em>-restrictions</em> switch. Otherwise, - the header can be changed temporarily to a string such as - <em>L_y_n_x/2.8.8</em> for access to sites which discriminate - against Lynx based on checks for the presence of "Lynx" in the - header. If the User-Agent header has been changed, it can be - restored to the built-in default value by deleting the modified - string in the Options Menu. Whenever the User-Agent header is - changed, the current document is reloaded, with the no-cache - flags set, on exit from the Options Menu. Changes of the header - are not saved in the RC file.</dd> - - <dd><em id="noteUA">NOTE:</em> Some sites may regard - misrepresenting the browser as fraudulent deception, or as - gaining unauthorized access, if it is used to circumvent - blocking that was intentionally put in place. Some browser - manufacturers may find the transmission of their product's name - objectionable. If you change the User-Agent string, it is your - responsibility. The Options Menu issues a reminder whenever the - header is changed to one which does not include "Lynx" or - "L_y_n_x".</dd> + <dd> + <p>The header string which Lynx sends to HTTP servers to + indicate the User-Agent is displayed here. Changes may be + disallowed via the <em>-restrictions</em> switch. Otherwise, + the header can be changed temporarily to a string such as + <em>L_y_n_x/2.8.8</em> for access to sites which discriminate + against Lynx based on checks for the presence of "Lynx" in + the header. If the User-Agent header has been changed, it can + be restored to the built-in default value by deleting the + modified string in the Options Menu. Whenever the User-Agent + header is changed, the current document is reloaded, with the + no-cache flags set, on exit from the Options Menu. Changes of + the header are not saved in the RC file.</p> + </dd> + + <dd> + <p><em id="noteUA">NOTE:</em> Some sites may regard + misrepresenting the browser as fraudulent deception, or as + gaining unauthorized access, if it is used to circumvent + blocking that was intentionally put in place. Some browser + manufacturers may find the transmission of their product's + name objectionable. If you change the User-Agent string, it + is your responsibility. The Options Menu issues a reminder + whenever the header is changed to one which does not include + "Lynx" or "L_y_n_x".</p> + </dd> <dt>User Mode</dt> <dd> - There are three possible choices: Novice, Intermediate, and - Advanced. + <p>There are three possible choices: Novice, Intermediate, + and Advanced.</p> <dl> <dt>Novice</dt> - <dd>In Novice mode two lines of help are displayed at the - bottom of the screen.</dd> + <dd> + <p>In Novice mode two lines of help are displayed at the + bottom of the screen.</p> + </dd> <dt>Intermediate</dt> - <dd>Intermediate mode turns off the help lines.</dd> + <dd> + <p>Intermediate mode turns off the help lines.</p> + </dd> <dt>Advanced</dt> - <dd>Advanced mode displays the URL of the currently - selected link at the bottom of the screen.</dd> + <dd> + <p>Advanced mode displays the URL of the currently + selected link at the bottom of the screen.</p> + </dd> </dl> </dd> <dt>Verbose Images</dt> - <dd>Controls whether or not Lynx replaces the [LINK], [INLINE] - and [IMAGE] comments (for images without ALT) with filenames of - these images. This is extremely useful because now we can - determine immediately what images are just decorations - (button.gif, line.gif) and what images are important. This - setting can also be toggled on startup via the - <em>-verbose</em> switch.</dd> + <dd> + <p>Controls whether or not Lynx replaces the [LINK], [INLINE] + and [IMAGE] comments (for images without ALT) with filenames + of these images. This is extremely useful because now we can + determine immediately what images are just decorations + (button.gif, line.gif) and what images are important. This + setting can also be toggled on startup via the + <em>-verbose</em> switch.</p> + </dd> <dt>VI keys</dt> <dd> - If set to ON then the lowercase h, j, k, and l keys will be - mapped to left, down, up, and right arrow, respectively. The - uppercase H, J, K, and L keys remain mapped to their + <p>If set to ON then the lowercase h, j, k, and l keys will + be mapped to left, down, up, and right arrow, respectively. + The uppercase H, J, K, and L keys remain mapped to their configured bindings (normally HELP, JUMP, KEYMAP, and LIST, - respectively). + respectively).</p> <p>Note: this has no effect on the line-editor's key bindings.</p> @@ -1489,7 +1667,7 @@ <dt>Visited Pages</dt> <dd> - Enable several different views of the visited links: + <p>Enable several different views of the visited links:</p> <dl> <dt>By First Visit</dt> @@ -1501,15 +1679,17 @@ <dt>By Last Visit</dt> <dt>By Last Visit Reversed</dt> - </dl> + </dl><br> </dd> <dt>X Display</dt> - <dd>This option is only relevant to X Window users. The DISPLAY - (Unix) or DECW$DISPLAY (VMS) variable is picked up - automatically from the environment if it has been previously - set.</dd> + <dd> + <p>This option is only relevant to X Window users. The + DISPLAY (Unix) or DECW$DISPLAY (VMS) variable is picked up + automatically from the environment if it has been previously + set.</p> + </dd> </dl> <p>[<a href="#ToC-InteractiveOptions">ToC</a>]</p> @@ -1518,13 +1698,13 @@ links</a></h2> <p>At any time while viewing documents within Lynx, you may use - the “<em>c</em>” command to send a mail message to - the owner of the current document if the author of the document - has specified ownership. (Note to authors: if you want to assign - the ownership to your document, you need to add into HEAD section - a LINK element with appropriate value for REV attribute. Two - values are recognized: <em>owner</em> and <em>made</em> (these - are case insensitive). For example,</p> + the “<samp>c</samp>” command to send a mail message + to the owner of the current document if the author of the + document has specified ownership. (Note to authors: if you want + to assign the ownership to your document, you need to add into + HEAD section a LINK element with appropriate value for REV + attribute. Two values are recognized: <em>owner</em> and + <em>made</em> (these are case insensitive). For example,</p> <pre> <HEAD> … @@ -1555,14 +1735,14 @@ <p>To finish sending the message, exit your spawned editor or, if you are using the simple line mode input scheme, type a - “<em>.</em>” (period) on a line by itself. You will - be asked a final time whether to send the message. If you press - “<em>y</em>”, you will be prompted whether to append - your signature file if one was defined in <a href= + “<samp>.</samp>” (period) on a line by itself. You + will be asked a final time whether to send the message. If you + press “<samp>y</samp>”, you will be prompted whether + to append your signature file if one was defined in <a href= "#lynx.cfg">lynx.cfg</a> and is accessible, and then the message - will be sent, whereas if you press “<em>n</em>” the - message will be deleted. Entering Control-G in response to any - prompts also will cancel the mailing.</p> + will be sent, whereas if you press “<samp>n</samp>” + the message will be deleted. Entering Control-G in response to + any prompts also will cancel the mailing.</p> <p>[<a href="#ToC-Mail">ToC</a>]</p> @@ -1579,26 +1759,30 @@ <dl> <dt>Reply to user@host</dt> - <dd>user@host will correspond to the mail address of the person - who posted the news article. Selecting the link will allow you - to send a message to the person who wrote the message you are - currently viewing. You will be given the option of including - the original message in your reply.</dd> + <dd> + <p>user@host will correspond to the mail address of the + person who posted the news article. Selecting the link will + allow you to send a message to the person who wrote the + message you are currently viewing. You will be given the + option of including the original message in your reply.</p> + </dd> <dt>Followup to newsgroup(s)</dt> - <dd>Selecting this link will allow you to post back to the - newsgroup that you are currently reading and any newsgroups to - which the message was cross-posted. You will be given the - option of including the original message in your reply. Once - you have typed in your message, you will be asked for - confirmation of whether to proceed with the posting, and - whether to append your signature file if one was defined in - <a href="#lynx.cfg">lynx.cfg</a> and is accessible. See - <a href="lynx_url_support.html">Supported URLs</a> for more - information about the URL schemes for posting or sending - followups (replies) to nntp servers with Lynx. [<a href= - "#ToC-News">ToC</a>]</dd> + <dd> + <p>Selecting this link will allow you to post back to the + newsgroup that you are currently reading and any newsgroups + to which the message was cross-posted. You will be given the + option of including the original message in your reply. Once + you have typed in your message, you will be asked for + confirmation of whether to proceed with the posting, and + whether to append your signature file if one was defined in + <a href="#lynx.cfg">lynx.cfg</a> and is accessible. See + <a href="lynx_url_support.html">Supported URLs</a> for more + information about the URL schemes for posting or sending + followups (replies) to nntp servers with Lynx. [<a href= + "#ToC-News">ToC</a>]</p> + </dd> </dl> <p>See also <a href= @@ -1615,35 +1799,35 @@ Menu</em>.</p> <p>To save a bookmark to the document you wish to place in the - bookmark file press the “<em>a</em>” key and you will - be asked:</p> + bookmark file press the “<samp>a</samp>” key and you + will be asked:</p> <blockquote> <p>Save D)ocument or L)ink to bookmark file or C)ancel? (d,l,c):</p> </blockquote> - <p>Answer “<em>d</em>” to save a link to the document - you are currently viewing or “<em>l</em>” to save the - link that is currently selected on the page. Selecting - “<em>c</em>” will cancel without saving anything to - your bookmark file.</p> + <p>Answer “<samp>d</samp>” to save a link to the + document you are currently viewing or + “<samp>l</samp>” to save the link that is currently + selected on the page. Selecting “<samp>c</samp>” will + cancel without saving anything to your bookmark file.</p> <p>A bookmark file will be created in conjunction with acting on - the “<em>a</em>”dd command if it does not already + the “<samp>a</samp>”dd command if it does not already exist. Otherwise, the link will be added to the bottom of the pre-existing bookmark file. You must have created a bookmark file - via the “<em>a</em>”dd command before you can view - it.</p> + via the “<samp>a</samp>”dd command before you can + view it.</p> - <p>Use the “<em>v</em>” command to view the list of - bookmarks you have saved. While viewing the bookmark list you may - select a bookmark as you would any other link.</p> + <p>Use the “<samp>v</samp>” command to view the list + of bookmarks you have saved. While viewing the bookmark list you + may select a bookmark as you would any other link.</p> <p>You can remove a link from the bookmark list by pressing the - “<em>r</em>” key when positioned on that link. You - also can use a standard text editor (e.g., via the - “<em>e</em>”dit command while viewing a bookmark + “<samp>r</samp>” key when positioned on that link. + You also can use a standard text editor (e.g., via the + “<samp>e</samp>”dit command while viewing a bookmark file, if an external editor has been defined via the <em>Options menu</em>) to delete or re-order links in the bookmark file, or to modify a link name by editing the content of the @@ -1661,8 +1845,9 @@ markup to the bookmark file. If the format and spacing (other than the <em>A</em>nchor content or <em>HREF</em> value) within lines is changed or other HTML markup is added, the - “<em>a</em>”dd and “<em>r</em>”emove - commands may not work properly.</p> + “<samp>a</samp>”dd and + “<samp>r</samp>”emove commands may not work + properly.</p> <p>When multi-bookmarks (see <a href= "#InteractiveOptions">Options Menu</a>) is OFF, you will always @@ -1670,7 +1855,7 @@ STANDARD, a menu of up to 26 bookmark files will be invoked, and you select the bookmark file by entering its letter token. When it is ADVANCED, you will be prompted for the letter token, but - can enter “<em>=</em>” to invoke the STANDARD + can enter “<samp>=</samp>” to invoke the STANDARD selection menu, or <em>RETURN</em> for the default bookmark file. [<a href="#ToC-Bookmarks">ToC</a>]</p> @@ -1682,12 +1867,12 @@ distribution package. To use the jumps command, create a <em>jumps file</em> with the same format as the sample file, but containing your own URLs & short-cut names. Once you have - done that, typing “<em>j</em>” prompts you to enter a - short-cut name, which will take you straight to the URL + done that, typing “<samp>j</samp>” prompts you to + enter a short-cut name, which will take you straight to the URL associated with the short-cut in the jumps file, much like using - “<em>g</em>”. If you want to check which short-cuts - are available, type “<em>?</em>” at the jump prompt - for the full list.</p> + “<samp>g</samp>”. If you want to check which + short-cuts are available, type “<samp>?</samp>” at + the jump prompt for the full list.</p> <p>You can set up a jumps file which makes Lynx prompt for parameters, e.g., as part of a search. Do this by putting a "%s" @@ -1696,9 +1881,10 @@ you for the parameters, one by one.</p> <p>All jump short-cuts you have entered are saved in a circular - buffer in the same way as with “<em>g</em>” and - “<em>/</em>” (search):<br> - previous entries can be retrieved with <em>up-arrow</em> or + buffer in the same way as with “<samp>g</samp>” and + “<samp>/</samp>>” (search):</p> + + <p>previous entries can be retrieved with <em>up-arrow</em> or <em>down-arrow</em>.</p> <p>The jumps feature is especially useful for system @@ -1728,50 +1914,66 @@ <dl> <dt><code>C)reate</code></dt> - <dd>Type “<em>c</em>” to create a new file. New - file will be empty.</dd> + <dd> + <p>Type “<samp>c</samp>” to create a new file. + New file will be empty.</p> + </dd> <dt><code>D)ownload</code></dt> - <dd>Type “<em>d</em>” to download using one of the - pre-defined options.</dd> + <dd> + <p>Type “<samp>d</samp>” to download using one of + the pre-defined options.</p> + </dd> <dt><code>E)dit</code></dt> - <dd>Type “<em>e</em>” to spawn the editor defined - in <em>Options Menu</em> and load a selected file for - editing.</dd> + <dd> + <p>Type “<samp>e</samp>” to spawn the editor + defined in <em>Options Menu</em> and load a selected file for + editing.</p> + </dd> <dt><code>F)ull Menu</code></dt> - <dd>Type “<em>f</em>” to show full menu of options - available for selection. Menu may vary according to type of - file selected and compression facilities available. - <!-- List of full menu options --></dd> + <dd> + <p>Type “<samp>f</samp>” to show full menu of + options available for selection. Menu may vary according to + type of file selected and compression facilities available. + <!-- List of full menu options --></p> + </dd> <dt><code>M)odify</code></dt> - <dd>Type “<em>m</em>” to modify the name or - location of file. Then type “<em>n</em>” to rename - the file or “<em>l</em>” to move the file to a - different location.</dd> + <dd> + <p>Type “<samp>m</samp>” to modify the name or + location of file. Then type “<samp>n</samp>” to + rename the file or “<samp>l</samp>” to move the + file to a different location.</p> + </dd> <dt><code>R)emove</code></dt> - <dd>Type “<em>r</em>” to remove the selected file - or directory.</dd> + <dd> + <p>Type “<samp>r</samp>” to remove the selected + file or directory.</p> + </dd> <dt><code>T)ag</code></dt> - <dd>Type “<em>t</em>” to tag highlighted file. - Further operations will be performed on tagged files instead of - highlighted ones.</dd> + <dd> + <p>Type “<samp>t</samp>” to tag highlighted file. + Further operations will be performed on tagged files instead + of highlighted ones.</p> + </dd> <dt><code>U)pload</code></dt> - <dd>Type “<em>u</em>” to upload a file to the - present directory. An uploading method must have been - pre-defined in <a href="#lynx.cfg">lynx.cfg</a> .</dd> + <dd> + <p>Type “<samp>u</samp>” to upload a file to the + present directory. An uploading method must have been + pre-defined in <a href="#lynx.cfg">lynx.cfg</a> .</p> + </dd> </dl> <p>[<a href="#ToC-DirEd">ToC</a>]</p> @@ -1788,234 +1990,355 @@ <p>A summary of all the keystroke commands and their key bindings can be invoked via the KEYMAP command, normally mapped to - “<em>k</em>” and “<em>K</em>”. The - following describes some of the most commonly used commands.</p> + “<samp>k</samp>” and “<samp>K</samp>”. + The following describes some of the most commonly used + commands.</p> <dl> - <dt><em>^A</em></dt> - - <dd><em>Control-A</em> jumps you to the beginning of the - current document. It is a synonym for the Keypad <em>Home</em> - key, and can be used also when <em>Links are numbered</em> mode - is on. The <em>Find</em> Function key also is a synonym, and - ideally the latter has been mapped to the Function key labeled - <em>Home</em> if you are using an IBM Enhanced Keyboard.</dd> - - <dt><em>^E</em></dt> - - <dd><em>Control-E</em> jumps you to the end of the current - document. It is a synonym for the Keypad <em>End</em> key, and - can be used also when <em>Links are numbered</em> mode is on. - The <em>Select</em> Function key also is a synonym, and ideally - the latter has been mapped to the Function key labeled - <em>End</em> if you are using an IBM Enhanced Keyboard.</dd> - - <dt><em>^B</em></dt> - - <dd><em>Control-B</em> normally jumps you to the previous page - of the current document, and thus is a synonym for the Keypad - and Function <em>Page-Up</em> keys. However, <em>Control-B</em> - acts as <em>right-arrow</em> when emacs-like key movement is - enabled (see <a href="#InteractiveOptions">Lynx Options - Menu</a>).</dd> - - <dt><em>^F</em></dt> - - <dd><em>Control-F</em> normally jumps you to the next page of - the current document, and thus is a synonym for the Keypad and - Function <em>Page-Down</em> keys. However, <em>Control-F</em> - becomes <em>right-arrow</em> when emacs-like key movement is - enabled.</dd> - - <dt><em>^N</em></dt> - - <dd><em>Control-N</em> normally jumps you forward two lines in - the current document. The <em>Remove</em> Function key (labeled - <em>Delete</em> on IBM Enhanced keyboards, and distinct from - their <em>Backspace</em> key) is a synonym. <em>Control-N</em> - becomes <em>down-arrow</em> when emacs-like key movement is - enabled.</dd> - - <dt><em>^P</em></dt> - - <dd><em>Control-P</em> normally jumps you back two lines in the - current document. The <em>Insert</em> Function key is a - synonym. <em>Control-P</em> becomes <em>up-arrow</em> when - emacs-like key movement is enabled.</dd> - - <dt><em>)</em></dt> - - <dd>The <em>)</em> command jumps you forward half a page in the - current document.</dd> - - <dt><em>(</em></dt> - - <dd>The <em>(</em> command jumps you back half a page in the - current document.</dd> - - <dt><em>#</em></dt> - - <dd>The “<em>#</em>” command jumps you to the - pseudo Toolbar or Banner if present in the current document. - Use <em>left-arrow</em> to return from there to your previous - position in the document.</dd> - - <dt><em>!</em></dt> - - <dd>When “<em>!</em>” is pressed your default shell - will be spawned. When you quit or exit the shell you will - return to Lynx (usually <em>exit</em> under Unix and - <em>logout</em> under VMS). This command is usually disabled - for anonymous users. On VMS, “<em>$</em>” normally - is a synonym. On Win32, this has no effect [???].</dd> - - <dt><em>g</em></dt> - - <dd>The “<em>g</em>” command allows any URL to be - viewed. Pressing the “<em>g</em>” command will - bring up a prompt asking for a URL. Type in the URL that you - wish to view. All previously entered goto URLs are saved in a - circular buffer, and can be accessed at the prompt by pressing - the <em>up-arrow</em> or <em>down-arrow</em> keys.</dd> - - <dt><em>G</em></dt> - - <dd>The “<em>G</em>” command allows you to edit the - URL of the current document and then use that as a goto URL. - Pressing the “<em>G</em>” command will bring up a - prompt asking you to edit the current document's URL. If you do - not modify it, or completely delete it, or enter Control-G, the - command will be cancelled. If the current document has POST - content associated with it, an Alert will be issued. If you do - edit that URL, and it does not simply involve a fragment change - (for seeking a position in the current document), the modified - URL will be submitted with method GET and no POST content. If a - modification of the current document's URL results in a - submission, that modified URL will be entered into the circular - buffer for goto URLs, and can be accessed for further - modification via the “<em>g</em>” command.</dd> - - <dt><em>E</em></dt> - - <dd>The “<em>E</em>” command allows you to edit the - URL (or ACTION) of the current link and then use that as a goto - URL. Pressing the “<em>E</em>” command will bring - up a prompt asking you to edit the current link's URL. If you - do not modify it, or completely delete it, or enter Control-G, - the command will be cancelled. Otherwise, the request for the - “E”dited URL will be sent with method GET, and will - be entered into the circular buffer for goto URLs so that it - can be accessed for further modification via the - “<em>g</em>” command. Note that lower case - “e” invokes the external editor for the current - document.</dd> - - <dt><em>=</em></dt> - - <dd>The “<em>=</em>” command shows information - about the current document and the currently selected link if - there is one. The number of lines in the file, URL, title, - owner, and type are shown.</dd> - - <dt><em>^T</em></dt> - - <dd><em>Control-T</em> toggles Lynx trace mode on and off. This - is useful for diagnosing bad html. If you get a <em>Bad - HTML</em> statusline message when loading a document, enter - <em>Control-T</em> and then <em>Control-R</em> to reload the - document in trace mode. You may then examine the <em>Lynx Trace - Log</em> file with the <em>;</em> command if enabled (see - below), watch out especially for lines marked with a number of - asterisks “<code>*****</code>”. You also can submit - the document for validation via links in the online help menu. - If you are able to diagnose the problem, send a message about - it to the document's author.</dd> - - <dt><em>;</em></dt> - - <dd>The <em>;</em> command shows the <em>Lynx Trace Log</em> - (<em>Lynx.trace</em> in the home directory) if one has been - started for the current session. If a log has not been started, - any trace messages will be sent to the screen (and will disturb - the normal display) unless the system supports piping and that - was used to redirect stderr messages to a file. The log is - started when Lynx trace mode is turned on via the - <em>-trace</em> command line switch, or via the - <em>Control-T</em> toggle, if Lynx has been compiled to log the - trace and other stderr messages by default. If not, ability to - create a log can be toggled on with the <em>-tlog</em> switch. - Note that this ability is probably disabled in anonymous or - validation accounts.</dd> + <dt><strong><em>^A</em></strong></dt> + + <dd> + <p><em>Control-A</em> jumps you to the beginning of the + current document. It is a synonym for the Keypad + <em>Home</em> key, and can be used also when <em>Links are + numbered</em> mode is on. The <em>Find</em> Function key also + is a synonym, and ideally the latter has been mapped to the + Function key labeled <em>Home</em> if you are using an IBM + Enhanced Keyboard.</p> + </dd> + + <dt><strong><em>^E</em></strong></dt> + + <dd> + <p><em>Control-E</em> jumps you to the end of the current + document. It is a synonym for the Keypad <em>End</em> key, + and can be used also when <em>Links are numbered</em> mode is + on. The <em>Select</em> Function key also is a synonym, and + ideally the latter has been mapped to the Function key + labeled <em>End</em> if you are using an IBM Enhanced + Keyboard.</p> + </dd> + + <dt><strong><em>^B</em></strong></dt> + + <dd> + <p><em>Control-B</em> normally jumps you to the previous page + of the current document, and thus is a synonym for the Keypad + and Function <em>Page-Up</em> keys. However, + <em>Control-B</em> acts as <em>right-arrow</em> when + emacs-like key movement is enabled (see <a href= + "#InteractiveOptions">Lynx Options Menu</a>).</p> + </dd> + + <dt><strong><em>^F</em></strong></dt> + + <dd> + <p><em>Control-F</em> normally jumps you to the next page of + the current document, and thus is a synonym for the Keypad + and Function <em>Page-Down</em> keys. However, + <em>Control-F</em> becomes <em>right-arrow</em> when + emacs-like key movement is enabled.</p> + </dd> + + <dt><strong><em>^N</em></strong></dt> + + <dd> + <p><em>Control-N</em> normally jumps you forward two lines in + the current document. The VT220 <em>Remove</em> Function key + (labeled <em>Delete</em> on IBM Enhanced keyboards, and + distinct from their <em>Backspace</em> key) is a synonym. + <em>Control-N</em> becomes <em>down-arrow</em> when + emacs-like key movement is enabled.</p> + </dd> + + <dt><strong><em>^P</em></strong></dt> + + <dd> + <p><em>Control-P</em> normally jumps you back two lines in + the current document. The <em>Insert</em> Function key is a + synonym. <em>Control-P</em> becomes <em>up-arrow</em> when + emacs-like key movement is enabled.</p> + </dd> + + <dt><strong><em>^K</em></strong></dt> + + <dd> + <p><em>Control-K</em> invokes the <a href= + "keystrokes/cookie_help.html">Cookie Jar Page</a> if it + contains cookies.</p> + </dd> + + <dt><strong><em>^T</em></strong></dt> + + <dd> + <p><em>Control-T</em> toggles Lynx trace mode on and off. + This is useful for diagnosing bad html. If you get a <em>Bad + HTML</em> statusline message when loading a document, enter + <em>Control-T</em> and then <em>Control-R</em> to reload the + document in trace mode. You may then examine the <em>Lynx + Trace Log</em> file with the <samp>;</samp> command if + enabled (see below), watch out especially for lines marked + with a number of asterisks “<code>*****</code>”. + You also can submit the document for validation via links in + the online help menu. If you are able to diagnose the + problem, send a message about it to the document's + author.</p> + </dd> + + <dt><strong><em>^X</em></strong></dt> + + <dd> + <p><em>Control-X</em> invokes the <a href="#Cache">Cache Jar + Page</a> if it contains cached documents.</p> + </dd> + + <dt><strong><samp>E</samp></strong></dt> + + <dd> + <p>The “<samp>E</samp>” command allows you to + edit the URL (or ACTION) of the current link and then use + that as a goto URL. Pressing the “<samp>E</samp>” + command will bring up a prompt asking you to edit the current + link's URL. If you do not modify it, or completely delete it, + or enter Control-G, the command will be cancelled. Otherwise, + the request for the “E”dited URL will be sent + with method GET, and will be entered into the circular buffer + for goto URLs so that it can be accessed for further + modification via the “<samp>g</samp>” command. + Note that lower case “e” invokes the external + editor for the current document.</p> + </dd> + + <dt><strong><samp>g</samp></strong></dt> + + <dd> + <p>The “<samp>g</samp>” command allows any URL to + be viewed. Pressing the “<samp>g</samp>” command + will bring up a prompt asking for a URL. Type in the URL that + you wish to view. All previously entered goto URLs are saved + in a circular buffer, and can be accessed at the prompt by + pressing the <em>up-arrow</em> or <em>down-arrow</em> + keys.</p> + </dd> + + <dt><strong><samp>G</samp></strong></dt> + + <dd> + <p>The “<samp>G</samp>” command allows you to + edit the URL of the current document and then use that as a + goto URL. Pressing the “<samp>G</samp>” command + will bring up a prompt asking you to edit the current + document's URL. If you do not modify it, or completely delete + it, or enter Control-G, the command will be cancelled. If the + current document has POST content associated with it, an + Alert will be issued. If you do edit that URL, and it does + not simply involve a fragment change (for seeking a position + in the current document), the modified URL will be submitted + with method GET and no POST content. If a modification of the + current document's URL results in a submission, that modified + URL will be entered into the circular buffer for goto URLs, + and can be accessed for further modification via the + “<samp>g</samp>” command.</p> + </dd> + + <dt><strong><samp>z</samp></strong></dt> + + <dd> + <p>Lynx supports completely interruptible I/O processes. + Press the “<samp>z</samp>” key at any time during + a connect or transfer process and the process will be halted. + If any data was transferred before the interrupt, it will be + displayed.</p> + </dd> + + <dt><strong><samp>)</samp></strong></dt> + + <dd> + <p>The <samp>)</samp> command jumps you forward half a page + in the current document.</p> + </dd> + + <dt><strong><samp>(</samp></strong></dt> + + <dd> + <p>The <samp>(</samp> command jumps you back half a page in + the current document.</p> + </dd> + + <dt><strong><samp>#</samp></strong></dt> + + <dd> + <p>The “<samp>#</samp>” command jumps you to the + pseudo Toolbar or Banner if present in the current document. + Use <em>left-arrow</em> to return from there to your previous + position in the document.</p> + </dd> + + <dt><strong><samp>!</samp></strong></dt> + + <dd> + <p>When “<samp>!</samp>” is pressed your default + shell will be spawned. When you quit or exit the shell you + will return to Lynx (usually <em>exit</em> under Unix and + <em>logout</em> under VMS). This command is usually disabled + for anonymous users. On VMS, “<samp>$</samp>” + normally is a synonym.</p> + </dd> + + <dt><strong><samp>=</samp></strong></dt> + + <dd> + <p>The “<samp>=</samp>” command shows information + about the current document and the currently selected link if + there is one. The number of lines in the file, URL, title, + owner, and type are shown.</p> + + <p>Normally the information is shown formatted (with margins) + for readability. You can make Lynx show the URL wrapped + without margins, e.g., making it convenient for select/paste, + by doing this:</p> + + <ul> + <li>toggle line-wrapping off using + “<samp>|</samp>”</li> + + <li>when line-wrapping is off, use the + “<samp>=</samp>” command</li> + </ul> + </dd> + + <dt><strong><samp>;</samp></strong></dt> + + <dd> + <p>The <samp>;</samp> command shows the <em>Lynx Trace + Log</em> (<em>Lynx.trace</em> in the home directory) if one + has been started for the current session. If a log has not + been started, any trace messages will be sent to the screen + (and will disturb the normal display) unless the system + supports piping and that was used to redirect stderr messages + to a file. The log is started when Lynx trace mode is turned + on via the <em>-trace</em> command line switch, or via the + <em>Control-T</em> toggle, if Lynx has been compiled to log + the trace and other stderr messages by default. If not, + ability to create a log can be toggled on with the + <em>-tlog</em> switch. Note that this ability is probably + disabled in anonymous or validation accounts.</p> + </dd> <dt><a name="asterisk-key" id= - "asterisk-key"><em>*</em></a></dt> + "asterisk-key"><strong><samp>*</samp></strong></a></dt> - <dd>The “<em>*</em>” command toggles image_links - mode on and off. When on, links will be created for all images, - including inline images. If you have an image viewer mapped to - the image's MIME type, you can activate such links to view an - inline image. You should normally have this mode toggled - off.</dd> + <dd> + <p>The “<samp>*</samp>” command toggles + image_links mode on and off. When on, links will be created + for all images, including inline images. If you have an image + viewer mapped to the image's MIME type, you can activate such + links to view an inline image. You should normally have this + mode toggled off.</p> + </dd> - <dt><em>@</em></dt> + <dt><strong><samp>@</samp></strong></dt> - <dd>The “<em>@</em>” command toggles raw 8-bit or - CJK mode on and off. When on, the charset is assumed to match - the selected character set and 8-bit characters are not reverse - translated with respect to the ISO-8859-1 conversion - tables.</dd> + <dd> + <p>The “<samp>@</samp>” command toggles raw 8-bit + or CJK mode on and off. When on, the charset is assumed to + match the selected character set and 8-bit characters are not + reverse translated with respect to the ISO-8859-1 conversion + tables.</p> + </dd> <dt><a name="lbracket-key" id= - "lbracket-key"><em>[</em></a></dt> + "lbracket-key"><strong><samp>[</samp></strong></a></dt> - <dd>The “<em>[</em>” command toggles pseudo_inlines - mode on and off. When on, inline images which have no ALT - string specified will have an <em>[INLINE]</em> pseudo-ALT - string inserted in the Lynx display. When off, they will be - treated as having ALT="" (i.e., they will be ignored). If - image_links mode is toggled on, the pseudo-ALT strings will be - restored, to serve as links to the inline images' sources.</dd> + <dd> + <p>The “<samp>[</samp>” command toggles + pseudo_inlines mode on and off. When on, inline images which + have no ALT string specified will have an <em>[INLINE]</em> + pseudo-ALT string inserted in the Lynx display. When off, + they will be treated as having ALT="" (i.e., they will be + ignored). If image_links mode is toggled on, the pseudo-ALT + strings will be restored, to serve as links to the inline + images' sources.</p> + </dd> - <dt><em>]</em></dt> + <dt><strong><samp>]</samp></strong></dt> - <dd>The “<em>]</em>” command is used to send HEAD - requests for the current document or link. It applies only to - documents or links (or form submit buttons) of http servers. A - statusline message will notify you if the context for this - command was inappropriate. The HEAD requests always are sent to - the http server, i.e., Lynx does not retrieve any previous - server replies from its cache. Note that for form submissions, - http servers vary in whether they'll treat HEAD requests as - valid and return the CGI script's headers, or treat it as - invalid and return an error message.</dd> + <dd> + <p>The “<samp>]</samp>” command is used to send + HEAD requests for the current document or link. It applies + only to documents or links (or form submit buttons) of http + servers. A statusline message will notify you if the context + for this command was inappropriate. The HEAD requests always + are sent to the http server, i.e., Lynx does not retrieve any + previous server replies from its cache. Note that for form + submissions, http servers vary in whether they'll treat HEAD + requests as valid and return the CGI script's headers, or + treat it as invalid and return an error message.</p> + </dd> - <dt><em>^K</em></dt> + <dt><strong><samp>{</samp></strong></dt> - <dd><em>Control-K</em> invokes the <a href= - "keystrokes/cookie_help.html">Cookie Jar Page</a> if it - contains cookies.</dd> + <dd> + <p>If the line-wrapping margin is wider than the terminal's + display, scroll left by half of the display's width.</p> - <dt><em>^X</em></dt> + <p>This feature is not available when Lynx is built using the + slang library.</p> + </dd> - <dd><em>Control-X</em> invokes the <a href="#Cache">Cache Jar - Page</a> if it contains cached documents.</dd> + <dt><strong><samp>|</samp></strong></dt> - <dt><em>z</em></dt> + <dd> + <p>“<samp>|</samp>” toggles Lynx line-wrapping + on/off. Normally Lynx fits text onto the screen, wrapping + lines. With this feature, Lynx provides the ability to + eliminate line-wrapping (up to an internal line-limit of 1000 + characters). Lynx uses the curses “pad” feature + to support left/right scrolling. You can scroll left and + right in the screen to view the wide lines.</p> + + <p>The popup menu for the command shows the other choices + which extend the wrapping margin:</p> + + <blockquote> + <pre> +/----------------------------------\ +| Try to fit screen width | +| No line wrap in columns | +| Wrap columns at screen width | +| Wrap columns at 3/4 screen width | +| Wrap columns at 2/3 screen width | +| Wrap columns at 1/2 screen width | +| Wrap columns at 1/3 screen width | +| Wrap columns at 1/4 screen width | +\----------------------------------/ +</pre> + </blockquote> - <dd>Lynx supports completely interruptible I/O processes. Press - the “<em>z</em>” key at any time during a connect - or transfer process and the process will be halted. If any data - was transferred before the interrupt, it will be - displayed.</dd> + <p>This feature is not available when Lynx is built using the + slang library.</p> + </dd> + + <dt><strong><samp>}</samp></strong></dt> + + <dd> + <p>If the line-wrapping margin is wider than the terminal's + display, scroll right by half of the display's width.</p> + + <p>This feature is not available when Lynx is built using the + slang library.</p> + </dd> <dt><em>numbers</em></dt> - <dd>Lynx offers other, advanced navigation features when - numbers are used to invoke the <a href= - "keystrokes/follow_help.html">Follow Link (or goto link or - page) number:</a> or <a href= - "keystrokes/follow_help.html#select-option">Select Pop-up - Option Number:</a> prompts.</dd> + <dd> + <p>Lynx offers other, advanced navigation features when + numbers are used to invoke the <a href= + "keystrokes/follow_help.html">Follow Link (or goto link or + page) number:</a> or <a href= + "keystrokes/follow_help.html#select-option">Select Pop-up + Option Number:</a> prompts.</p> + </dd> </dl> <p>[<a href="#ToC-MiscKeys">ToC</a>]</p> @@ -2037,50 +2360,58 @@ <dl> <dt>Buttons:</dt> - <dd>Buttons are displayed in the same way that Lynx displays - links in a document. To "push" the button press the - <em>right-arrow</em> or <em>Return</em> key. If it is a form - submission button, you also can use the NOCACHE - (“<em>x</em>”) or DOWNLOAD - (“<em>d</em>”) keystroke commands to "push" the - button (see below).</dd> + <dd> + <p>Buttons are displayed in the same way that Lynx displays + links in a document. To "push" the button press the + <em>right-arrow</em> or <em>Return</em> key. If it is a form + submission button, you also can use the NOCACHE + (“<samp>x</samp>”) or DOWNLOAD + (“<samp>d</samp>”) keystroke commands to "push" + the button (see below).</p> + </dd> <dt>Checkboxes and Radio buttons</dt> - <dd>Checkboxes are displayed as square brackets: <em>[ ]</em> - and radio buttons are displayed as parenthesis: <em>( )</em>. - When a box is checked or a button selected, an <em>x</em> - appears in the brackets: <em>[x]</em> or an asterisk appears - within the parenthesis: <em>(*)</em>. To check a box or select - a radio button press the <em>right-arrow</em> or - <em>Return</em> key.</dd> + <dd> + <p>Checkboxes are displayed as square brackets: + <em>[ ]</em> and radio buttons are displayed as + parenthesis: <em>( )</em>. When a box is checked or a + button selected, an <samp>x</samp> appears in the brackets: + <em>[x]</em> or an asterisk appears within the parenthesis: + <em>(*)</em>. To check a box or select a radio button press + the <em>right-arrow</em> or <em>Return</em> key.</p> + </dd> <dt>Selection Fields</dt> - <dd>Selection fields are displayed as brackets with the default - option displayed between them: <em>[default__]</em>. To select - an option press the <em>right-arrow</em> or <em>Return</em> - key. A box with a border of asterisks (or line-drawing - characters) will pop up with the list of possible options - listed within the box. Use the <em>up-arrow</em>, - <em>down-arrow</em>, <em>page-up</em>, <em>page-down</em>, and - other navigation keys to move the cursor among options, and the - <em>right-arrow</em> or <em>Return</em> key to select an - option. You also can use the “<em>/</em>” and - “<em>n</em>”ext <a href="#Search">searching</a> - commands for navigating to options which contain particular - strings. <em>NOTE</em> that the popup menu feature can be - disabled via compilation and/or configuration options, or via - the <a href="#InteractiveOptions">Options Menu</a>, in which - case the selection field options will be converted to a list of - radio buttons. The default setting for use of popups or radio - button lists can be toggled via the <em>-popup</em> command - line switch.</dd> + <dd> + <p>Selection fields are displayed as brackets with the + default option displayed between them: <em>[default__]</em>. + To select an option press the <em>right-arrow</em> or + <em>Return</em> key. A box with a border of asterisks (or + line-drawing characters) will pop up with the list of + possible options listed within the box. Use the + <em>up-arrow</em>, <em>down-arrow</em>, <em>page-up</em>, + <em>page-down</em>, and other navigation keys to move the + cursor among options, and the <em>right-arrow</em> or + <em>Return</em> key to select an option. You also can use the + “<samp>/</samp>” and + “<samp>n</samp>”ext <a href= + "#Search">searching</a> commands for navigating to options + which contain particular strings. <em>NOTE</em> that the + popup menu feature can be disabled via compilation and/or + configuration options, or via the <a href= + "#InteractiveOptions">Options Menu</a>, in which case the + selection field options will be converted to a list of radio + buttons. The default setting for use of popups or radio + button lists can be toggled via the <em>-popup</em> command + line switch.</p> + </dd> <dt>Text Entry Fields</dt> <dd> - Text entry (INPUT) fields are displayed as a row of + <p>Text entry (INPUT) fields are displayed as a row of underscores the length of the entry field: <em>_______</em>. You may enter text directly by typing at the keyboard. Use the <a href="keystrokes/edit_help.html">Line Editor</a> keys @@ -2101,7 +2432,7 @@ the Line Editor gets activated with <em>Return</em> or <em>Right Arrow</em>. This mode can be used to avoid "getting stuck" in input fields, especially by users who rarely fill - out forms. + out forms.</p> <p><a name="CtrlVNote" id="CtrlVNote">NOTE:</a> If you have a text input field selected you will not have access to most of @@ -2137,9 +2468,9 @@ <p> KEYMAP:^V:DO_NOTHING<br> KEYMAP:#:SWITCH_DTD</p> - <p>would map SWITCH_DTD away from <em>^V</em> to <em>#</em>, - while leaving its default Line Editor function as a command - escape in place. On the other hand,</p> + <p>would map SWITCH_DTD away from <em>^V</em> to + <samp>#</samp>, while leaving its default Line Editor + function as a command escape in place. On the other hand,</p> <p> KEYMAP:^V::NOP:1<br> KEYMAP:^_::LKCMD:1</p> @@ -2152,26 +2483,28 @@ <dt>TEXTAREA Fields</dt> - <dd>TEXTAREA fields are for most purposes handled as if they - were a series of text entry (INPUT) fields for which successive - lines imply a newline at the end of the preceding line. You - enter text on each line to construct the overall message. Any - blank lines at the bottom of the TEXTAREA field will be - eliminated from the submission. The <em>up-arrow</em>, and - <em>down-arrow</em> or <em>Return</em> keys move you to the - preceding, or next line of the overall message, as for INPUT - fields. The <em>TAB</em> key will move you down beyond the - bottom of the TEXTAREA field, and <em>Back Tab</em> (if - available, e.g., as Shift-Tab, and correctly mapped in the - terminal description) will move backward to a link or field - before the TEXTAREA.</dd> + <dd> + <p>TEXTAREA fields are for most purposes handled as if they + were a series of text entry (INPUT) fields for which + successive lines imply a newline at the end of the preceding + line. You enter text on each line to construct the overall + message. Any blank lines at the bottom of the TEXTAREA field + will be eliminated from the submission. The + <em>up-arrow</em>, and <em>down-arrow</em> or <em>Return</em> + keys move you to the preceding, or next line of the overall + message, as for INPUT fields. The <em>TAB</em> key will move + you down beyond the bottom of the TEXTAREA field, and + <em>Back Tab</em> (if available, e.g., as Shift-Tab, and + correctly mapped in the terminal description) will move + backward to a link or field before the TEXTAREA.</p> + </dd> <dt>Editing TEXTAREA Fields and Special TEXTAREA Functions</dt> <dd> - TEXTAREA fields can be edited using an external editor. The - statusline should tell you when this is possible and what key - to use, it might for example say + <p>TEXTAREA fields can be edited using an external editor. + The statusline should tell you when this is possible and what + key to use, it might for example say</p> <pre> <strong>(Textarea) Enter text. </strong>[ ..... ]<strong> (^Xe for editor).</strong> </pre> @@ -2251,11 +2584,12 @@ content, and the METHOD was <em>GET</em>, Lynx will retrieve from its cache what was returned from the previous submission. If you wish to resubmit that form to the server with the same content as - previously, use the NOCACHE command (“<em>x</em>”) - when positioned on the submit button. The <em>right-arrow</em> - and <em>Return</em> keys also will invoke a no-cache resubmission - if the reply from a form submission included a META element with - a no-cache Pragma or Cache-Control directive:<br></p> + previously, use the NOCACHE command + (“<samp>x</samp>”) when positioned on the submit + button. The <em>right-arrow</em> and <em>Return</em> keys also + will invoke a no-cache resubmission if the reply from a form + submission included a META element with a no-cache Pragma or + Cache-Control directive:</p> <pre> <em><META HTTP-EQUIV="Pragma" CONTENT="no-cache"></em> <em><META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"></em> @@ -2264,7 +2598,7 @@ <p>or the server sent a "Pragma" or "Cache-Control" MIME header with a no-cache directive.</p> - <p>You also can use the DOWNLOAD (“<em>d</em>”) + <p>You also can use the DOWNLOAD (“<samp>d</samp>”) keystroke command when positioned on a form submit button if you wish to download the server's reply to the submission instead of having Lynx render and display it.</p> @@ -2298,7 +2632,7 @@ about which one of the buttons was used to submit the form is included in the form content.</p> - <p>Inlined images can be used as submit buttons in forms. If such + <p>Inlined images can be used as submit buttons in forms: If such buttons are assigned NAMEs in the markup, for graphic clients they can also serve as <a href="#USEMAP">image maps</a>, and the x,y coordinates of the graphic client's cursor position in the @@ -2306,24 +2640,41 @@ content. Since Lynx cannot inline the image, and the user could not have moved a cursor from the origin for the image, if no alternatives are made available in the markup Lynx sends a 0,0 - coordinate pair in the form content. Document authors who use - images as submit buttons, but have at least some concern for text - clients and sight-challenged Webizens, should include VALUEs for - the buttons in such markup. Lynx will then display the string - assigned to the VALUE, as it would for a normal submit button. - Some document authors incorrectly use an ALT instead of VALUE - attribute for this purpose. Lynx "cooperates" by treating ALT as - a synonym for VALUE when present in an INPUT tag with - TYPE="image". If neither a VALUE nor an ALT attribute is present, - Lynx displays "[IMAGE]-Submit" as the string for such buttons. If - clickable images is set, the "[IMAGE]" portion of the string is a - link for the image, and the "Submit" portion is the button for - submitting the form. Otherwise, the entire string is treated as a - submit button. If a VALUE or ALT attribute is present and - clickable images is set, Lynx prepends "[IMAGE]" as a link for - the image, followed by “-” and then the attribute's - value as the displayed string for the submit button. Note that - earlier versions of Lynx would send a name=value pair instead of + coordinate pair in the form content.</p> + + <p>Document authors who use images as submit buttons, but have at + least some concern for text clients and sight-challenged + Webizens, should include VALUEs for the buttons in such markup. + Lynx will then display the string assigned to the VALUE, as it + would for a normal submit button.</p> + + <ul> + <li> + <p>Some document authors incorrectly use an ALT instead of + VALUE attribute for this purpose. Lynx "cooperates" by + treating ALT as a synonym for VALUE when present in an INPUT + tag with TYPE="image".</p> + </li> + + <li> + <p>If neither a VALUE nor an ALT attribute is present, Lynx + displays "[IMAGE]-Submit" as the string for such buttons.</p> + </li> + + <li> + <p>If clickable images is set, the "[IMAGE]" portion of the + string is a link for the image, and the "Submit" portion is + the button for submitting the form.</p> + + <p>Otherwise, the entire string is treated as a submit + button. If a VALUE or ALT attribute is present and clickable + images is set, Lynx prepends "[IMAGE]" as a link for the + image, followed by “-” and then the attribute's + value as the displayed string for the submit button.</p> + </li> + </ul> + + <p>Early versions of Lynx would send a name=value pair instead of a 0,0 coordinate pair if a TYPE="image" submit button was NAME-ed, had a VALUE attribute in the INPUT tag, and was used to submit the form. The script which analyzes the form content thus @@ -2367,10 +2718,10 @@ <em>ENCTYPE="application/sgml-form-urlencoded"</em> for which all reserved characters in the content will be hex escaped, as with <em>application/x-www-form-urlencoded</em>, but semicolons - (“<em>;</em>”) instead of ampersands - (“<em>&</em>”) will be used as the separator for - name=value pairs in the form content. The use of semicolons is - preferred for forms with the <em>GET</em> METHOD, because the + (“<samp>;</samp>”) instead of ampersands + (“<samp>&</samp>”) will be used as the separator + for name=value pairs in the form content. The use of semicolons + is preferred for forms with the <em>GET</em> METHOD, because the <em>GET</em> METHOD causes the encoded form content to be appended as a <em>?searchpart</em> for the form's ACTION, and if such URLs are used in <em>text/html</em> documents or bookmark @@ -2401,8 +2752,8 @@ <p>A <em>Content-Disposition: file; filename=name.suffix</em> header can be used by CGI scripts to set the suggested filename - offered by Lynx for “<em>d</em>”ownload and - “<em>p</em>”rint menu options to save or mail the + offered by Lynx for “<samp>d</samp>”ownload and + “<samp>p</samp>”rint menu options to save or mail the body returned by the script following submission of a FORM. Otherwise, Lynx uses the last symbolic element in the path for the FORM's ACTION, which is normally the script, itself, or a @@ -2645,17 +2996,17 @@ the other two cannot be saved between sessions. <p>Lynx does not waste screen real estate maintaining the <em>banner</em> at the top of every page, but the Lynx TOOLBAR - keystroke command (“<em>#</em>”) will, any time it is - pressed, position you on the <em>banner</em> so that any of its - links can be activated, and pressing the <em>left-arrow</em> when - in the <em>banner</em> will return you to where you were in the - current document. The toolbar is indicated by a - “<em>#</em>" preceding its first link when present on the - screen, that is, when the first page of the document is being - displayed. The availability of a toolbar is indicated by a - “<em>#</em>” at the top, left-hand corner of the - screen when the second or subsequent pages of the document are - being displayed.</p> + keystroke command (“<samp>#</samp>”) will, any time + it is pressed, position you on the <em>banner</em> so that any of + its links can be activated, and pressing the <em>left-arrow</em> + when in the <em>banner</em> will return you to where you were in + the current document. The toolbar is indicated by a + “<samp>#</samp>” preceding its first link when + present on the screen, that is, when the first page of the + document is being displayed. The availability of a toolbar is + indicated by a “<samp>#</samp>” at the top, left-hand + corner of the screen when the second or subsequent pages of the + document are being displayed.</p> <p>Lynx also recognizes the <a href= "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> @@ -2665,11 +3016,11 @@ the other two cannot be saved between sessions. for BANNER (i.e., presenting its markup as a static <em>banner</em>, without any horizontal scrolling of its content). Lynx does not prefix the BANNER or MARQUEE content with - a “<em>#</em>” because the content need not be only a - series of links with brief, descriptive links names, but does add - a “<em>#</em>” at the top, left-hand corner of the - screen when the content is not being displayed, to indicate its - accessibility via the TOOLBAR keystroke command.</p> + a “<samp>#</samp>” because the content need not be + only a series of links with brief, descriptive links names, but + does add a “<samp>#</samp>” at the top, left-hand + corner of the screen when the content is not being displayed, to + indicate its accessibility via the TOOLBAR keystroke command.</p> <p>[<a href="#ToC-Banners">ToC</a>]</p> @@ -2725,7 +3076,7 @@ the other two cannot be saved between sessions. Footnotes</a>, but the NOTE block need not be placed at the bottom of the document. The content of a NOTE block can be any HTML markup that is valid in the BODY of the document. This is an - example:<br></p> + example:</p> <pre> <em><NOTE CLASS="warning" ID="too-bad"> <p>The W3C vendors did not retain NOTE in the HTML 3.2 draft.</p> @@ -2831,9 +3182,9 @@ the other two cannot be saved between sessions. its first line.</p> <p>Lynx respects nested Q start and end tags, and will use ASCII - double-quotes (<em>"</em>) versus grave accent (<em>`</em>) and - apostrophe (<em>'</em>), respectively, for even versus odd depths - in the nest.</p> + double-quotes (<samp>"</samp>) versus grave accent + (<samp>`</samp>) and apostrophe (<samp>'</samp>), respectively, + for even versus odd depths in the nest.</p> <p>Any ID attributes in BLOCKQUOTE, BQ or Q elements can be the target of a hyperlink in the form URL#id. It is treated just like @@ -2990,35 +3341,37 @@ the other two cannot be saved between sessions. <p>State Management via cookie exchanges originally was implemented by Netscape, and such cookies are now designated as <em>Version 0</em>. A more elaborate format for cookies, - designated as <em>Version 1</em>, is being standardized by the - IETF (Internet Engineering Task Force). Lynx supports both - <em>Version 0</em> and <em>Version 1</em> cookie exchanges. This - support can be disabled by default via the SET_COOKIES symbol in - the compilation (<em>userdefs.h</em>) and/or run time (<a href= - "#lynx.cfg">lynx.cfg</a>) configuration files, and that default - setting can be toggled via the <em>-cookies</em> command line - switch. The SET_COOKIES symbol can be further modified by the - ACCEPT_ALL_COOKIES mode. If ACCEPT_ALL_COOKIES is set TRUE, and - SET_COOKIES is TRUE, Lynx will accept all cookies. Additionally, - the cookies that are automatically accepted or rejected by Lynx - can be further modified with the COOKIE_ACCEPT_DOMAINS and - COOKIE_REJECT_DOMAINS options in your .lynxrc file, each of which - is a comma-separated list of domains to perform the desired - action. The domain listed in these options must be identical to - the domain the cookie comes from, there is no wildcard matching. - If a domain is specific in both COOKIE_ACCEPT_DOMAINS and - COOKIE_REJECT_DOMAINS, rejection will take precedence.</p> + designated as <em>Version 1</em>, was standardized by the IETF + (Internet Engineering Task Force) as <a href= + "https://www.ietf.org/rfc/rfc2109.txt">RFC 2109</a>. Lynx + supports both <em>Version 0</em> and <em>Version 1</em> cookie + exchanges. This support can be disabled by default via the + SET_COOKIES symbol in the compilation (<em>userdefs.h</em>) + and/or run time (<a href="#lynx.cfg">lynx.cfg</a>) configuration + files, and that default setting can be toggled via the + <em>-cookies</em> command line switch. The SET_COOKIES symbol can + be further modified by the ACCEPT_ALL_COOKIES mode. If + ACCEPT_ALL_COOKIES is set TRUE, and SET_COOKIES is TRUE, Lynx + will accept all cookies. Additionally, the cookies that are + automatically accepted or rejected by Lynx can be further + modified with the COOKIE_ACCEPT_DOMAINS and COOKIE_REJECT_DOMAINS + options in your .lynxrc file, each of which is a comma-separated + list of domains to perform the desired action. The domain listed + in these options must be identical to the domain the cookie comes + from, there is no wildcard matching. If a domain is specific in + both COOKIE_ACCEPT_DOMAINS and COOKIE_REJECT_DOMAINS, rejection + will take precedence.</p> <p>When cookie support is enabled, <em>Set-Cookie</em> MIME headers received from an http server invoke confirmation prompts - with possible replies of “<em>Y</em>”es or - “<em>N</em>”o for acceptance of the cookie, - “<em>A</em>”lways to accept the cookie and to allow - all subsequent cookies from that <em>domain</em> (server's Fully - Qualified Domain Name, or site-identifying portion of the FQDN) - without further confirmation prompts, or - ne“<em>V</em>”er to never allow cookies from that - <em>domain</em> to be accepted (silently ignore its + with possible replies of “<samp>Y</samp>”es or + “<samp>N</samp>”o for acceptance of the cookie, + “<samp>A</samp>”lways to accept the cookie and to + allow all subsequent cookies from that <em>domain</em> (server's + Fully Qualified Domain Name, or site-identifying portion of the + FQDN) without further confirmation prompts, or + ne“<strong>V</strong>”er to never allow cookies from + that <em>domain</em> to be accepted (silently ignore its <em>Set-Cookie</em> MIME headers). All unexpired cookies are held in a hypothetical <em>Cookie Jar</em> which can be examined via the COOKIE_JAR keystroke command, normally mapped to @@ -3182,7 +3535,7 @@ the other two cannot be saved between sessions. <dt><code>startfile</code></dt> <dd> - is the file or URL that Lynx will load at start-up. + <p>is the file or URL that Lynx will load at start-up.</p> <ul> <li>If startfile is not specified, Lynx will use a default @@ -3207,10 +3560,10 @@ the other two cannot be saved between sessions. <dt><code>options</code></dt> <dd> - Lynx uses only long option names. Option names can begin with - double dash as well, underscores and dashes can be intermixed - in option names (in the reference below options are with one - dash before them and with underscores). + <p>Lynx uses only long option names. Option names can begin + with double dash as well, underscores and dashes can be + intermixed in option names (in the reference below options + are with one dash before them and with underscores).</p> <p>Lynx provides many command-line options. Some options require a value (string, number or keyword). These are noted @@ -3221,12 +3574,14 @@ the other two cannot be saved between sessions. toggle (between true/false). For any of these, an explicit value can be given in different forms to allow for operating system constraints, e.g.,</p> - <pre> -<code> - -center:off - -center=off - -center-</code> + + <blockquote> + <pre> +-center:off +-center=off +-center- </pre> + </blockquote> <p>Lynx recognizes "1", "+", "on" and "true" for true values, and "0", "-", "off" and "false" for false values. Other @@ -3247,1111 +3602,1503 @@ the other two cannot be saved between sessions. <dl> <dt><code><strong>-</strong></code></dt> - <dd>If the argument is only - “<code><strong>-</strong></code>” (dash), then - Lynx expects to receive the arguments from stdin. This is - to allow for the potentially very long command line that - can be associated with the <em>-get_data</em> or - <em>-post_data</em> arguments (see below). It can also be - used to avoid having sensitive information in the invoking - command line (which would be visible to other processes on - most systems), especially when the <em>-auth</em> or - <em>-pauth</em> options are used. On VMS, the dash must be - encased in double-quotes ("-") and the keyboard input - terminated with <em>Control-Z</em> or the command file - input terminated by a line that begins with - “<em>$</em>”. On Unix, the keyboard input - terminator is <em>Control-D</em>. On Win32, [???].</dd> + <dd> + <p>If the argument is only + “<code><strong>-</strong></code>” (dash), + then Lynx expects to receive the arguments from stdin. + This is to allow for the potentially very long command + line that can be associated with the <em>-get_data</em> + or <em>-post_data</em> arguments (see below). It can also + be used to avoid having sensitive information in the + invoking command line (which would be visible to other + processes on most systems), especially when the + <em>-auth</em> or <em>-pauth</em> options are used. On + VMS, the dash must be encased in double-quotes ("-") and + the keyboard input terminated with <em>Control-Z</em> or + the command file input terminated by a line that begins + with “<samp>$</samp>”. On Unix, the keyboard + input terminator is <em>Control-D</em>. On Win32, + [???].</p> + </dd> <dt><code><strong>-accept_all_cookies</strong></code></dt> - <dd>accept all cookies.</dd> + <dd> + <p>accept all cookies.</p> + </dd> <dt><code><strong>-anonymous</strong></code></dt> - <dd>apply restrictions appropriate for an anonymous - account, see <em>-restrictions</em> below for some - details.</dd> + <dd> + <p>apply restrictions appropriate for an anonymous + account, see <em>-restrictions</em> below for some + details.</p> + </dd> <dt> <code><strong>-assume_charset=</strong><em>MIMENAME</em></code></dt> - <dd>charset for documents that do not specify it.</dd> + <dd> + <p>charset for documents that do not specify it.</p> + </dd> <dt> <code><strong>-assume_local_charset=</strong><em>MIMENAME</em></code></dt> - <dd>charset assumed for local files, i.e., files which lynx - creates such as internal pages for the options menu.</dd> + <dd> + <p>charset assumed for local files, i.e., files which + lynx creates such as internal pages for the options + menu.</p> + </dd> <dt> <code><strong>-assume_unrec_charset=</strong><em>MIMENAME</em></code></dt> - <dd>use this instead of unrecognized charsets.</dd> + <dd> + <p>use this instead of unrecognized charsets.</p> + </dd> <dt><code><strong>-auth=</strong><em>ID:PW</em></code></dt> - <dd>set authorization <em>identifier</em> and - <em>password</em> for protected documents at startup. Be - sure to protect any script files which use this - switch.</dd> + <dd> + <p>set authorization <em>identifier</em> and + <em>password</em> for protected documents at startup. Be + sure to protect any script files which use this + switch.</p> + </dd> <dt><code><strong>-base</strong></code></dt> - <dd>prepend a request URL comment and BASE tag to text/html - outputs for -source dumps.</dd> + <dd> + <p>prepend a request URL comment and BASE tag to + text/html outputs for -source dumps.</p> + </dd> <dt><code><strong>-bibp=</strong><em>URL</em></code></dt> - <dd>specify a local bibp server (default - http://bibhost/).</dd> + <dd> + <p>specify a local bibp server (default + http://bibhost/).</p> + </dd> <dt><code><strong>-blink</strong></code></dt> - <dd>forces high intensity background colors for color mode, - if available and supported by the terminal. This applies to - the slang library (for a few terminal emulators), or to - OS/2 EMX with ncurses.</dd> + <dd> + <p>forces high intensity background colors for color + mode, if available and supported by the terminal. This + applies to the slang library (for a few terminal + emulators), or to OS/2 EMX with ncurses.</p> + </dd> <dt><code><strong>-book</strong></code></dt> - <dd>use the bookmark page as the startfile. The default or - command line startfile is still set for the Main screen - command, and will be used if the bookmark page is - unavailable or blank.</dd> + <dd> + <p>use the bookmark page as the startfile. The default or + command line startfile is still set for the Main screen + command, and will be used if the bookmark page is + unavailable or blank.</p> + </dd> <dt><code><strong>-buried_news</strong></code></dt> - <dd>toggles scanning of news articles for buried - references, and converts them to news links. Not - recommended because email addresses enclosed in angle - brackets will be converted to false news links, and - uuencoded messages can be trashed.</dd> + <dd> + <p>toggles scanning of news articles for buried + references, and converts them to news links. Not + recommended because email addresses enclosed in angle + brackets will be converted to false news links, and + uuencoded messages can be trashed.</p> + </dd> <dt> <code><strong>-cache=</strong><em>NUMBER</em></code></dt> - <dd>set the <em>NUMBER</em> of documents cached in memory. - The default is 10.</dd> + <dd> + <p>set the <em>NUMBER</em> of documents cached in memory. + The default is 10.</p> + </dd> <dt><code><strong>-center</strong></code></dt> - <dd>Toggle center alignment in HTML TABLE.</dd> + <dd> + <p>Toggle center alignment in HTML TABLE.</p> + </dd> <dt><code><strong>-case</strong></code></dt> - <dd>enable case-sensitive string searching.</dd> + <dd> + <p>enable case-sensitive string searching.</p> + </dd> <dt> <code><strong>-cfg=</strong><em>FILENAME</em></code></dt> - <dd>specifies a Lynx configuration file other than the - default <a href="#lynx.cfg">lynx.cfg</a>.</dd> + <dd> + <p>specifies a Lynx configuration file other than the + default <a href="#lynx.cfg">lynx.cfg</a>.</p> + </dd> <dt><code><strong>-child</strong></code></dt> - <dd>exit on left-arrow in startfile, and disable save to - disk.</dd> + <dd> + <p>exit on left-arrow in startfile, and disable save to + disk.</p> + </dd> <dt><code><strong>-child_relaxed</strong></code></dt> - <dd>exit on left-arrow in startfile, but allow save to disk - and associated print/mail options.</dd> + <dd> + <p>exit on left-arrow in startfile, but allow save to + disk and associated print/mail options.</p> + </dd> <dt> <code><strong>-cmd_log=</strong><em>FILENAME</em></code></dt> - <dd>write keystroke commands and related information to the - specified file.</dd> + <dd> + <p>write keystroke commands and related information to + the specified file.</p> + </dd> <dt> <code><strong>-cmd_script=</strong><em>FILENAME</em></code></dt> <dd> - read keystroke commands from the specified file. You can - use the data written using the <em>-cmd_log</em> option. - Lynx will ignore other information which the + <p>read keystroke commands from the specified file. You + can use the data written using the <em>-cmd_log</em> + option. Lynx will ignore other information which the command-logging may have written to the log- file. Each line of the command script contains either a comment - beginning with "#", or a keyword: + beginning with "#", or a keyword:</p> <dl> <dt><code><strong>exit</strong></code></dt> - <dd>causes the script to stop, and forces lynx to exit - immediately.</dd> + <dd> + <p>causes the script to stop, and forces lynx to exit + immediately.</p> + </dd> <dt><code><strong>key</strong></code></dt> - <dd>the character value, in printable form. Cursor and - other special keys are given as names, e.g., - <code><strong>Down Arrow</strong></code>. Printable - 7-bit ASCII codes are given as-is, and hexadecimal - values represent other 8-bit codes.</dd> + <dd> + <p>the character value, in printable form. Cursor and + other special keys are given as names, e.g., + <code><strong>Down Arrow</strong></code>. Printable + 7-bit ASCII codes are given as-is, and hexadecimal + values represent other 8-bit codes.</p> + </dd> <dt><code><strong>set</strong></code></dt> - <dd>followed by a "name=value" allows one to override - values set in the lynx.cfg file.</dd> + <dd> + <p>followed by a "name=value" allows one to override + values set in the lynx.cfg file.</p> + </dd> </dl> </dd> <dt><code><strong>-color</strong></code></dt> - <dd>forces color mode on, if available. Default color - control sequences which work for many terminal types are - assumed if the terminal capability description does not - specify how to handle color. Lynx needs to be compiled with - the slang library for this flag. It is equivalent to - setting the COLORTERM environment variable. (If color - support is instead provided by a color-capable curses - library like ncurses, Lynx relies completely on the - terminal description to determine whether color mode is - possible, and this flag is not needed and thus - unavailable.) A saved show_color=always setting found in a - .lynxrc file at startup has the same effect. A saved - show_color=always found in .lynxrc on startup is overridden - by this flag.</dd> + <dd> + <p>forces color mode on. This feature is only available + if Lynx is built using the slang library. The slang + library will send ANSI color sequences irregardless of + the type of terminal which is being used.</p> + + <p>If color support is instead provided by a + color-capable curses library such as ncurses, Lynx relies + completely on the terminal description to determine + whether color mode is possible, and this flag is not + needed and thus unavailable.</p> + + <p>A saved <samp>show_color=always</samp> setting found + in a .lynxrc file at startup has the same effect, but the + setting read from .lynxrc on startup is overridden by + this flag.</p> + </dd> <dt> <code><strong>-connect_timeout</strong>=<em>N</em></code></dt> - <dd>Sets the connection timeout, where <em>N</em> is given - in seconds.</dd> + <dd> + <p>Sets the connection timeout, where <em>N</em> is given + in seconds.</p> + </dd> <dt> <code><strong>-cookie_file=</strong><em>FILENAME</em></code></dt> - <dd>specifies a file to use to read cookies. If none is - specified, the default value is ~/.lynx_cookies for most - systems, but ~/cookies for MS-DOS.</dd> + <dd> + <p>specifies a file to use to read cookies. If none is + specified, the default value is ~/.lynx_cookies for most + systems, but ~/cookies for MS-DOS.</p> + </dd> <dt> <code><strong>-cookie_save_file=</strong><em>FILENAME</em></code></dt> - <dd>specifies a file to use to store cookies. If none is - specified, the value given by - <code><strong>-cookie_file</strong></code> is used.</dd> + <dd> + <p>specifies a file to use to store cookies. If none is + specified, the value given by + <code><strong>-cookie_file</strong></code> is used.</p> + </dd> <dt><code><strong>-cookies</strong></code></dt> - <dd>toggles handling of Set-Cookie headers.</dd> + <dd> + <p>toggles handling of Set-Cookie headers.</p> + </dd> <dt><code><strong>-core</strong></code></dt> - <dd>toggles forced core dumps on fatal errors. (Unix - only)</dd> + <dd> + <p>toggles forced core dumps on fatal errors. (Unix + only)</p> + </dd> <dt><code><strong>-crawl</strong></code></dt> - <dd>with <em>-traversal</em>, output each page to a - file.<br> - with <em>-dump</em>, format output as with - <em>-traversal</em>, but to stdout.</dd> + <dd> + <p>with <em>-traversal</em>, output each page to a + file.</p> + + <p>with <em>-dump</em>, format output as with + <em>-traversal</em>, but to stdout.</p> + </dd> <dt><code><strong>-curses_pads</strong></code></dt> - <dd>toggles the use of curses "pad" feature which supports - left/right scrolling of the display.</dd> + <dd> + <p>toggles the use of curses "pad" feature which supports + left/right scrolling of the display.</p> + </dd> <dt><code><strong>-debug_partial</strong></code></dt> - <dd>separate incremental display stages with MessageSecs - delay</dd> + <dd> + <p>separate incremental display stages with MessageSecs + delay</p> + </dd> <dt> <code><strong>-display=</strong><em>DISPLAY</em></code></dt> - <dd>set the display variable for X rexe-ced programs.</dd> + <dd> + <p>set the display variable for X rexe-ced programs.</p> + </dd> <dt> <code><strong>-display_charset=</strong><em>MIMEname</em></code></dt> - <dd>set the charset for the terminal output.</dd> + <dd> + <p>set the charset for the terminal output.</p> + </dd> <dt><code><strong>-dont_wrap_pre</strong></code></dt> - <dd>inhibit wrapping of text in <pre> when -dump'ing - and -crawl'ing, mark wrapped lines in interactive - session.</dd> + <dd> + <p>inhibit wrapping of text in <pre> when -dump'ing + and -crawl'ing, mark wrapped lines in interactive + session.</p> + </dd> <dt><code><strong>-dump</strong></code></dt> - <dd>dumps the formatted output of the default document or - one specified on the command line to standard out. This can - be used in the following way:<br> - <em>lynx -dump http://www.w3.org/</em></dd> + <dd> + <p>dumps the formatted output of the default document or + one specified on the command line to standard out. This + can be used in the following way:</p> + + <blockquote> + <p><em>lynx -dump http://www.w3.org/</em></p> + </blockquote> + </dd> <dt> <code><strong>-editor=</strong><em>EDITOR</em></code></dt> - <dd>enable external editing using the specified - <em>EDITOR</em>. (vi, ed, emacs, etc.)</dd> + <dd> + <p>enable external editing using the specified + <em>EDITOR</em>. (vi, ed, emacs, etc.)</p> + </dd> <dt><code><strong>-emacskeys</strong></code></dt> - <dd>enable emacs-like key movement.</dd> + <dd> + <p>enable emacs-like key movement.</p> + </dd> <dt><code><strong>-enable_scrollback</strong></code></dt> - <dd>toggles behavior compatible with the scrollback keys in - some communications software (may be incompatible with some - curses packages).</dd> + <dd> + <p>toggles behavior compatible with the scrollback keys + in some communications software (may be incompatible with + some curses packages).</p> + </dd> <dt> <code><strong>-error_file=</strong><em>FILENAME</em></code></dt> - <dd>the status code from the HTTP request is placed in this - file.</dd> + <dd> + <p>the status code from the HTTP request is placed in + this file.</p> + </dd> <dt><code><strong>-exec</strong></code></dt> - <dd>enable local program execution (normally not - configured).</dd> + <dd> + <p>enable local program execution (normally not + configured).</p> + </dd> <dt><code><strong>-fileversions</strong></code></dt> - <dd>include all versions of files in local VMS directory - listings.</dd> + <dd> + <p>include all versions of files in local VMS directory + listings.</p> + </dd> <dt><code><strong>-find_leaks</strong></code></dt> - <dd>toggles the memory leak checking off. Normally this is - not compiled-into your executable, but when it is, it can - be disabled for a session.</dd> + <dd> + <p>toggles the memory leak checking off. Normally this is + not compiled-into your executable, but when it is, it can + be disabled for a session.</p> + </dd> <dt> <code><strong>-force_empty_hrefless_a</strong></code></dt> - <dd>force HREF-less “A” elements to be empty - (close them as soon as they are seen).</dd> + <dd> + <p>force HREF-less “A” elements to be empty + (close them as soon as they are seen).</p> + </dd> <dt><code><strong>-force_html</strong></code></dt> - <dd>forces the first document to be interpreted as - HTML.</dd> + <dd> + <p>forces the first document to be interpreted as + HTML.</p> + </dd> <dt><code><strong>-force_secure</strong></code></dt> - <dd>toggles forcing of the secure flag for SSL - cookies.</dd> + <dd> + <p>toggles forcing of the secure flag for SSL + cookies.</p> + </dd> <dt><code><strong>-forms_options</strong></code></dt> - <dd>toggles whether the Options Menu is key-based or - form-based.</dd> + <dd> + <p>toggles whether the Options Menu is key-based or + form-based.</p> + </dd> <dt><code><strong>-from</strong></code></dt> - <dd>toggles transmissions of From headers to HTTP or HTTPS - servers.</dd> + <dd> + <p>toggles transmissions of From headers to HTTP or HTTPS + servers.</p> + </dd> <dt><code><strong>-ftp</strong></code></dt> - <dd>disable ftp access.</dd> + <dd> + <p>disable ftp access.</p> + </dd> <dt><code><strong>-get_data</strong></code></dt> - <dd>properly formatted data for a get form are read in from - stdin and passed to the form. Input is terminated by a line - that starts with “---”.</dd> + <dd> + <p>properly formatted data for a get form are read in + from stdin and passed to the form. Input is terminated by + a line that starts with “---”.</p> + </dd> <dt><code><strong>-head</strong></code></dt> - <dd>send a HEAD request for the mime headers.</dd> + <dd> + <p>send a HEAD request for the mime headers.</p> + </dd> <dt><code><strong>-help</strong></code></dt> - <dd>print this Lynx command syntax usage message.</dd> + <dd> + <p>print this Lynx command syntax usage message.</p> + </dd> <dt> <code><strong>-hiddenlinks=</strong><em>option</em></code></dt> <dd> - control the display of hidden links. Option values are: + <p>control the display of hidden links. Option values + are:</p> <dl> <dt><code><strong>merge</strong></code></dt> - <dd>hidden links show up as bracketed numbers and are - numbered together with other links in the sequence of - their occurrence in the document.</dd> + <dd> + <p>hidden links show up as bracketed numbers and are + numbered together with other links in the sequence of + their occurrence in the document.</p> + </dd> <dt><code><strong>listonly</strong></code></dt> - <dd>hidden links are shown only on <em>L</em>ist - screens and listings generated by - <code><strong>-dump</strong></code> or from the - <em>P</em>rint menu, but appear separately at the end - of those lists. This is the default behavior.</dd> + <dd> + <p>hidden links are shown only on <em>L</em>ist + screens and listings generated by + <code><strong>-dump</strong></code> or from the + <em>P</em>rint menu, but appear separately at the end + of those lists. This is the default behavior.</p> + </dd> <dt><code><strong>ignore</strong></code></dt> - <dd>hidden links do not appear even in listings.</dd> + <dd> + <p>hidden links do not appear even in listings.</p> + </dd> </dl> </dd> <dt><code><strong>-historical</strong></code></dt> - <dd>toggles use of “>” or - “-->” as a terminator for comments.</dd> + <dd> + <p>toggles use of “>” or + “-->” as a terminator for comments.</p> + </dd> <dt> <code><strong>-homepage=</strong><em>URL</em></code></dt> - <dd>set homepage separate from start page. Will be used if - a fetch of the start page fails or if it is a script which - does not return a document, and as the - <code><em>URL</em></code> for the - “<em>m</em>”ain menu command.</dd> + <dd> + <p>set homepage separate from start page. Will be used if + a fetch of the start page fails or if it is a script + which does not return a document, and as the + <code><em>URL</em></code> for the + “<samp>m</samp>”ain menu command.</p> + </dd> <dt><code><strong>-image_links</strong></code></dt> - <dd>toggles inclusion of links for all images.</dd> + <dd> + <p>toggles inclusion of links for all images.</p> + </dd> <dt><code><strong>-ismap</strong></code></dt> - <dd>toggles inclusion of ISMAP links when client-side MAPs - are present.</dd> + <dd> + <p>toggles inclusion of ISMAP links when client-side MAPs + are present.</p> + </dd> <dt><code><strong>-index=</strong><em>URL</em></code></dt> - <dd>set the default index file to the specified - <em>URL</em></dd> + <dd> + <p>set the default index file to the specified + <em>URL</em></p> + </dd> <dt><code><strong>-justify</strong></code></dt> - <dd>do justification of text.</dd> + <dd> + <p>do justification of text.</p> + </dd> <dt> <code><strong>-link=</strong><em>NUMBER</em></code></dt> - <dd>starting count for lnk#.dat files produced by - <em>-crawl</em>.</dd> + <dd> + <p>starting count for lnk#.dat files produced by + <em>-crawl</em>.</p> + </dd> <dt><code><strong>-localhost</strong></code></dt> - <dd>disable URLs that point to remote hosts.</dd> + <dd> + <p>disable URLs that point to remote hosts.</p> + </dd> <dt><code><strong>-locexec</strong></code></dt> - <dd>enable local program execution from local files only - (if lynx was compiled with local execution enabled).</dd> + <dd> + <p>enable local program execution from local files only + (if lynx was compiled with local execution enabled).</p> + </dd> <dt> <code><strong>-lss=</strong><em>FILENAME</em></code></dt> - <dd>specify filename containing color-style information. - The default is lynx.lss.</dd> + <dd> + <p>specify filename containing color-style information. + The default is lynx.lss.</p> + </dd> <dt><code><strong>-mime_header</strong></code></dt> - <dd>include mime headers and force source dump.</dd> + <dd> + <p>include mime headers and force source dump.</p> + </dd> <dt><code><strong>-minimal</strong></code></dt> - <dd>toggles minimal versus valid comment parsing. When - minimal, any “-->” serves as a terminator - for a comment element. When valid, pairs of - “--” are treated as delimiters for series of - comments within the overall comment element. If historical - is set, that overrides minimal or valid comment - parsing.</dd> + <dd> + <p>toggles minimal versus valid comment parsing. When + minimal, any “-->” serves as a terminator + for a comment element. When valid, pairs of + “--” are treated as delimiters for series of + comments within the overall comment element. If + historical is set, that overrides minimal or valid + comment parsing.</p> + </dd> <dt><code><strong>-nested_tables</strong></code></dt> - <dd>toggles nested-tables logic (for debugging).</dd> + <dd> + <p>toggles nested-tables logic (for debugging).</p> + </dd> <dt> <code><strong>-newschunksize=</strong><em>NUMBER</em></code></dt> - <dd>number of articles in chunked news listings.</dd> + <dd> + <p>number of articles in chunked news listings.</p> + </dd> <dt> <code><strong>-newsmaxchunk=</strong><em>NUMBER</em></code></dt> - <dd>maximum news articles in listings before chunking.</dd> + <dd> + <p>maximum news articles in listings before chunking.</p> + </dd> <dt><code><strong>-nobold</strong></code></dt> - <dd>disable bold video-attribute.</dd> + <dd> + <p>disable bold video-attribute.</p> + </dd> <dt><code><strong>-nobrowse</strong></code></dt> - <dd>disable directory browsing.</dd> + <dd> + <p>disable directory browsing.</p> + </dd> <dt><code><strong>-nocc</strong></code></dt> - <dd>disable Cc: prompts for self copies of mailings. Note - that this does not disable any CCs which are incorporated - within a mailto URL or form ACTION.</dd> + <dd> + <p>disable Cc: prompts for self copies of mailings. Note + that this does not disable any CCs which are incorporated + within a mailto URL or form ACTION.</p> + </dd> <dt><code><strong>-nocolor</strong></code></dt> - <dd>force color mode off, overriding terminal capabilities - and any <em>-color</em> flags, <em>COLORTERM</em> variable, - and saved .lynxrc settings.</dd> + <dd> + <p>force color mode off, overriding terminal capabilities + and any <em>-color</em> flags, <em>COLORTERM</em> + variable, and saved .lynxrc settings.</p> + </dd> <dt><code><strong>-noexec</strong></code></dt> - <dd>disable local program execution. (DEFAULT)</dd> + <dd> + <p>disable local program execution. (DEFAULT)</p> + </dd> <dt><code><strong>-nofilereferer</strong></code></dt> - <dd>disable transmissions of Referer headers for file - URLs.</dd> + <dd> + <p>disable transmissions of Referer headers for file + URLs.</p> + </dd> <dt><code><strong>-nolist</strong></code></dt> - <dd>disable the link list feature in dumps.</dd> + <dd> + <p>disable the link list feature in dumps.</p> + </dd> <dt><code><strong>-nolog</strong></code></dt> - <dd>disable mailing of error messages to document - owners.</dd> + <dd> + <p>disable mailing of error messages to document + owners.</p> + </dd> <dt><code><strong>-nomargins</strong></code></dt> - <dd>disable left/right margins in the default style - sheet.</dd> + <dd> + <p>disable left/right margins in the default style + sheet.</p> + </dd> <dt><code><strong>-nomore</strong></code></dt> - <dd>disable -more- string in statusline messages.</dd> + <dd> + <p>disable -more- string in statusline messages.</p> + </dd> <dt> <code><strong>-nonrestarting_sigwinch</strong></code></dt> - <dd>make window size change handler non-restarting. This - flag is not available on all systems, Lynx needs to be - compiled with HAVE_SIGACTION defined. If available, this - flag <em>may</em> cause Lynx to react more immediately to - window changes when run within an xterm.</dd> + <dd> + <p>make window size change handler non-restarting. This + flag is not available on all systems, Lynx needs to be + compiled with HAVE_SIGACTION defined. If available, this + flag <em>may</em> cause Lynx to react more immediately to + window changes when run within an xterm.</p> + </dd> <dt><code><strong>-nopause</strong></code></dt> - <dd>disable forced pauses for statusline messages.</dd> + <dd> + <p>disable forced pauses for statusline messages.</p> + </dd> <dt><code><strong>-noprint</strong></code></dt> - <dd>disable most print functions.</dd> + <dd> + <p>disable most print functions.</p> + </dd> <dt><code><strong>-noredir</strong></code></dt> - <dd>do not follow URL redirections</dd> + <dd> + <p>do not follow URL redirections</p> + </dd> <dt><code><strong>-noreferer</strong></code></dt> - <dd>disable transmissions of Referer headers.</dd> + <dd> + <p>disable transmissions of Referer headers.</p> + </dd> <dt><code><strong>-noreverse</strong></code></dt> - <dd>disable reverse video-attribute.</dd> + <dd> + <p>disable reverse video-attribute.</p> + </dd> <dt><code><strong>-nosocks</strong></code></dt> - <dd>disable SOCKS proxy usage by a SOCKSified Lynx.</dd> + <dd> + <p>disable SOCKS proxy usage by a SOCKSified Lynx.</p> + </dd> <dt><code><strong>-nostatus</strong></code></dt> - <dd>disable the retrieval status messages.</dd> + <dd> + <p>disable the retrieval status messages.</p> + </dd> <dt><code><strong>-notitle</strong></code></dt> - <dd>disable title and blank line from top of page.</dd> + <dd> + <p>disable title and blank line from top of page.</p> + </dd> <dt><code><strong>-nounderline</strong></code></dt> - <dd>disable underline video-attribute.</dd> + <dd> + <p>disable underline video-attribute.</p> + </dd> <dt><code><strong>-number_fields</strong></code></dt> - <dd>force numbering of links as well as form input - fields.</dd> + <dd> + <p>force numbering of links as well as form input + fields.</p> + </dd> <dt><code><strong>-number_links</strong></code></dt> - <dd>force numbering of links.</dd> + <dd> + <p>force numbering of links.</p> + </dd> <dt><code><strong>-partial</strong></code></dt> - <dd>toggles displaying of partial pages while loading.</dd> + <dd> + <p>toggles displaying of partial pages while loading.</p> + </dd> <dt> <code><strong>-partial_thres=</strong><em>NUMBER</em></code></dt> - <dd>number of lines to render before repainting display - with partial-display logic.</dd> + <dd> + <p>number of lines to render before repainting display + with partial-display logic.</p> + </dd> <dt> <code><strong>-pauth=</strong><em>ID:PW</em></code></dt> - <dd>set authorization <em>identifier</em> and - <em>password</em> for a protected proxy server at startup. - Be sure to protect any script files which use this - switch.</dd> + <dd> + <p>set authorization <em>identifier</em> and + <em>password</em> for a protected proxy server at + startup. Be sure to protect any script files which use + this switch.</p> + </dd> <dt><code><strong>-popup</strong></code></dt> - <dd>toggles handling of single-choice SELECT options via - popup windows or as lists of radio buttons. The default - configuration can be changed in userdefs.h or <a href= - "#lynx.cfg">lynx.cfg</a>. It also can be set and saved via - the “o”ptions menu. The command line switch - toggles the default.</dd> + <dd> + <p>toggles handling of single-choice SELECT options via + popup windows or as lists of radio buttons. The default + configuration can be changed in userdefs.h or <a href= + "#lynx.cfg">lynx.cfg</a>. It also can be set and saved + via the “o”ptions menu. The command line + switch toggles the default.</p> + </dd> <dt><code><strong>-post_data</strong></code></dt> - <dd>properly formatted data for a post form are read in - from stdin and passed to the form. Input is terminated by a - line that starts with “---”.</dd> + <dd> + <p>properly formatted data for a post form are read in + from stdin and passed to the form. Input is terminated by + a line that starts with “---”.</p> + </dd> <dt><code><strong>-preparsed</strong></code></dt> - <dd>show source preparsed and reformatted when used with - -source or in source view (“<em>\</em>”). May - be useful for debugging of broken HTML markup to visualize - the difference between SortaSGML and TagSoup <a href= - "keystrokes/option_help.html#tagsoup">recovery modes</a>, - switched by “<em>^V</em>”.</dd> + <dd> + <p>show source preparsed and reformatted when used with + -source or in source view (“<samp>\</samp>”). + May be useful for debugging of broken HTML markup to + visualize the difference between SortaSGML and TagSoup + <a href="keystrokes/option_help.html#tagsoup">recovery + modes</a>, switched by “<samp>^V</samp>”.</p> + </dd> <dt><code><strong>-prettysrc</strong></code></dt> - <dd>do syntax highlighting and hyperlink handling in source - view.</dd> + <dd> + <p>do syntax highlighting and hyperlink handling in + source view.</p> + </dd> <dt><code><strong>-print</strong></code></dt> - <dd>enable print functions. (default)</dd> + <dd> + <p>enable print functions. (default)</p> + </dd> <dt><code><strong>-pseudo_inlines</strong></code></dt> - <dd>toggles pseudo-ALTs for inline images with no ALT - string.</dd> + <dd> + <p>toggles pseudo-ALTs for inline images with no ALT + string.</p> + </dd> <dt><code><strong>-raw</strong></code></dt> - <dd>toggles default setting of 8-bit character translations - or CJK mode for the startup character set.</dd> + <dd> + <p>toggles default setting of 8-bit character + translations or CJK mode for the startup character + set.</p> + </dd> <dt><code><strong>-realm</strong></code></dt> - <dd>restricts access to URLs in the starting realm.</dd> + <dd> + <p>restricts access to URLs in the starting realm.</p> + </dd> <dt><code><strong>-reload</strong></code></dt> - <dd>flushes the cache on a proxy server (only the first - document affected).</dd> + <dd> + <p>flushes the cache on a proxy server (only the first + document affected).</p> + </dd> <dt><code><strong>-restrictions</strong></code></dt> - <dd>allows a list of services to be disabled selectively - and takes the following form:</dd> + <dd> + <p>allows a list of services to be disabled selectively + and takes the following form:</p> + </dd> - <dd><em>lynx - -restrictions=[option][,option][,option]...</em></dd> + <dd> + <p><em>lynx + -restrictions=[option][,option][,option]...</em></p> + </dd> <dd> - The list of recognized options is printed if none are - specified. + <p>The list of recognized options is printed if none are + specified.</p> <dl> - <dt>?</dt> - - <dd>if used alone, lists restrictions in effect.</dd> - - <dt>all</dt> - - <dd>restricts all options listed below.</dd> - - <dt>bookmark</dt> - - <dd>disallow changing the location of the bookmark - file.</dd> - - <dt>bookmark_exec</dt> - - <dd>disallow execution links via the bookmark - file.</dd> + <dt><strong><samp>?</samp></strong></dt> + + <dd> + <p>if used alone, lists restrictions in effect.</p> + </dd> + + <dt><strong><samp>all</samp></strong></dt> + + <dd> + <p>restricts all options listed below.</p> + </dd> + + <dt><strong><samp>bookmark</samp></strong></dt> + + <dd> + <p>disallow changing the location of the bookmark + file.</p> + </dd> + + <dt><strong><samp>bookmark_exec</samp></strong></dt> + + <dd> + <p>disallow execution links via the bookmark + file.</p> + </dd> + + <dt> + <strong><samp>change_exec_perms</samp></strong></dt> + + <dd> + <p>disallow changing the eXecute permission on files + (but still allow it for directories) when local file + management is enabled.</p> + </dd> + + <dt><strong><samp>chdir</samp></strong></dt> + + <dd> + <p>disallow command which changes Lynx's working + directory.</p> + </dd> + + <dt><strong><samp>default</samp></strong></dt> + + <dd> + <p>same as command line option <em>-anonymous</em>. + Set default restrictions for anonymous users. All + specific services listed are always restricted, + except for: inside_telnet, outside_telnet, + inside_ftp, outside_ftp, inside_rlogin, + outside_rlogin, inside_news, outside_news, + telnet_port, jump, mail, print, exec, and goto. The + settings for these, as well as additional goto + restrictions for specific URL schemes that are also + applied, are derived from definitions within + userdefs.h.</p> + + <p>Note that this is the only option value that may + have the effect of <em>removing</em> some + restrictions, if they have been set by other options, + namely for those services that <em>are</em> allowed + by default according to userdefs.h. However, if the + separate command line option form + (<em>-anonymous</em>) is used, Lynx takes care to set + the default restrictions before handling additional + <em>-restrictions=</em> options (even if they precede + the <em>anonymous</em> option), so that this cannot + happen.</p> + </dd> + + <dt><strong><samp>dired_support</samp></strong></dt> + + <dd> + <p>disallow local file management.</p> + </dd> + + <dt><strong><samp>disk_save</samp></strong></dt> + + <dd> + <p>disallow saving to disk in the download and print + menus.</p> + </dd> + + <dt><strong><samp>dotfiles</samp></strong></dt> + + <dd> + <p>disallow access to, or creation of, hidden (dot) + files.</p> + </dd> + + <dt><strong><samp>download</samp></strong></dt> + + <dd> + <p>disallow some downloaders in the download menu. + This does <em>not</em> imply the disk_save + restriction. It also does not disable the DOWNLOAD + command, and does not prevent "Download or Cancel" + offers when a MIME type cannot otherwise be handled. + Those are only disabled if additionally the disk_save + restriction is in effect <em>and</em> no download + methods are defined in a <a href="#lynx.cfg">Lynx + configuration file</a> that are marked as "always + ENABLED" (or, alternatively, if the -validate switch + is used).</p> + </dd> - <dt>change_exec_perms</dt> + <dt><strong><samp>editor</samp></strong></dt> - <dd>disallow changing the eXecute permission on files - (but still allow it for directories) when local file - management is enabled.</dd> + <dd> + <p>disallow external editing.</p> + </dd> - <dt>chdir</dt> + <dt><strong><samp>exec</samp></strong></dt> - <dd>disallow command which changes Lynx's working - directory.</dd> + <dd> + <p>disable execution scripts.</p> + </dd> - <dt>default</dt> + <dt><strong><samp>exec_frozen</samp></strong></dt> - <dd>same as command line option <em>-anonymous</em>. - Set default restrictions for anonymous users. All - specific services listed are always restricted, except - for: inside_telnet, outside_telnet, inside_ftp, - outside_ftp, inside_rlogin, outside_rlogin, - inside_news, outside_news, telnet_port, jump, mail, - print, exec, and goto. The settings for these, as well - as additional goto restrictions for specific URL - schemes that are also applied, are derived from - definitions within userdefs.h.<br> - Note that this is the only option value that may have - the effect of <em>removing</em> some restrictions, if - they have been set by other options, namely for those - services that <em>are</em> allowed by default according - to userdefs.h. However, if the separate command line - option form (<em>-anonymous</em>) is used, Lynx takes - care to set the default restrictions before handling - additional <em>-restrictions=</em> options (even if - they precede the <em>anonymous</em> option), so that - this cannot happen.</dd> + <dd> + <p>disallow the user from changing the local + execution option.</p> + </dd> - <dt>dired_support</dt> + <dt><strong><samp>externals</samp></strong></dt> - <dd>disallow local file management.</dd> + <dd> + <p>disallow some "EXTERNAL" configuration lines, if + support for passing URLs to external applications + (with the EXTERN_LINK or EXTERN_PAGE command) is + compiled in.</p> + </dd> - <dt>disk_save</dt> + <dt><strong><samp>file_url</samp></strong></dt> - <dd>disallow saving to disk in the download and print - menus.</dd> + <dd> + <p>disallow using G)oto, served links or bookmarks + for file: URLs.</p> + </dd> - <dt>dotfiles</dt> + <dt><strong><samp>goto</samp></strong></dt> - <dd>disallow access to, or creation of, hidden (dot) - files.</dd> + <dd> + <p>disable the “<samp>g</samp>” (goto) + command.</p> + </dd> - <dt>download</dt> + <dt><strong><samp>inside_ftp</samp></strong></dt> - <dd>disallow some downloaders in the download menu. - This does <em>not</em> imply the disk_save restriction. - It also does not disable the DOWNLOAD command, and does - not prevent "Download or Cancel" offers when a MIME - type cannot otherwise be handled. Those are only - disabled if additionally the disk_save restriction is - in effect <em>and</em> no download methods are defined - in a <a href="#lynx.cfg">Lynx configuration file</a> - that are marked as "always ENABLED" (or, alternatively, - if the -validate switch is used).</dd> + <dd> + <p>disallow ftps for people coming from inside your + domain.</p> + </dd> - <dt>editor</dt> + <dt><strong><samp>inside_news</samp></strong></dt> - <dd>disallow external editing.</dd> + <dd> + <p>disallow USENET news reading and posting for + people coming from inside you domain. This applies to + "news", "nntp", "newspost", and "newsreply" URLs, but + not to "snews", "snewspost", or "snewsreply" in case + they are supported.</p> + </dd> - <dt>exec</dt> + <dt><strong><samp>inside_rlogin</samp></strong></dt> - <dd>disable execution scripts.</dd> + <dd> + <p>disallow rlogins for people coming from inside + your domain.</p> + </dd> - <dt>exec_frozen</dt> + <dt><strong><samp>inside_telnet</samp></strong></dt> - <dd>disallow the user from changing the local execution - option.</dd> + <dd> + <p>disallow telnets for people coming from inside + your domain.</p> + </dd> - <dt>externals</dt> + <dt><strong><samp>jump</samp></strong></dt> - <dd>disallow some "EXTERNAL" configuration lines, if - support for passing URLs to external applications (with - the EXTERN_LINK or EXTERN_PAGE command) is compiled - in.</dd> + <dd> + <p>disable the “<samp>j</samp>” (jump) + command.</p> + </dd> - <dt>file_url</dt> + <dt><strong><samp>lynxcgi</samp></strong></dt> - <dd>disallow using G)oto, served links or bookmarks for - file: URLs.</dd> + <dd> + <p>disallow execution of Lynx CGI URLs.</p> + </dd> - <dt>goto</dt> + <dt><strong><samp>mail</samp></strong></dt> - <dd>disable the “<em>g</em>” (goto) - command.</dd> + <dd> + <p>disallow mailing feature.</p> + </dd> - <dt>inside_ftp</dt> + <dt><strong><samp>multibook</samp></strong></dt> - <dd>disallow ftps for people coming from inside your - domain.</dd> + <dd> + <p>disallow multiple bookmarks.</p> + </dd> - <dt>inside_news</dt> + <dt><strong><samp>news_post</samp></strong></dt> - <dd>disallow USENET news reading and posting for people - coming from inside you domain. This applies to "news", - "nntp", "newspost", and "newsreply" URLs, but not to - "snews", "snewspost", or "snewsreply" in case they are - supported.</dd> + <dd> + <p>disallow USENET News posting,</p> + </dd> - <dt>inside_rlogin</dt> + <dt><strong><samp>options_save</samp></strong></dt> - <dd>disallow rlogins for people coming from inside your - domain.</dd> + <dd> + <p>disallow saving options in .lynxrc.</p> + </dd> - <dt>inside_telnet</dt> + <dt><strong><samp>outside_ftp</samp></strong></dt> - <dd>disallow telnets for people coming from inside your - domain.</dd> + <dd> + <p>disallow ftps for people coming from outside your + domain.</p> + </dd> - <dt>jump</dt> + <dt><strong><samp>outside_news</samp></strong></dt> - <dd>disable the “<em>j</em>” (jump) - command.</dd> + <dd> + <p>disallow USENET news reading and posting for + people coming from outside you domain. This applies + to "news", "nntp", "newspost", and "newsreply" URLs, + but not to "snews", "snewspost", or "snewsreply" in + case they are supported.</p> + </dd> - <dt>lynxcgi</dt> + <dt><strong><samp>outside_rlogin</samp></strong></dt> - <dd>disallow execution of Lynx CGI URLs.</dd> + <dd> + <p>disallow rlogins for people coming from outside + your domain.</p> + </dd> - <dt>mail</dt> + <dt><strong><samp>outside_telnet</samp></strong></dt> - <dd>disallow mailing feature.</dd> + <dd> + <p>disallow telnets for people coming from outside + your domain.</p> + </dd> - <dt>multibook</dt> + <dt><strong><samp>print</samp></strong></dt> - <dd>disallow multiple bookmarks.</dd> + <dd> + <p>disallow most print options.</p> + </dd> - <dt>news_post</dt> + <dt><strong><samp>shell</samp></strong></dt> - <dd>disallow USENET News posting,</dd> + <dd> + <p>disallow shell escapes.</p> + </dd> - <dt>options_save</dt> + <dt><strong><samp>suspend</samp></strong></dt> - <dd>disallow saving options in .lynxrc.</dd> + <dd> + <p>disallow <em>Control-Z</em> suspends with escape + to shell on Unix.</p> + </dd> - <dt>outside_ftp</dt> + <dt><strong><samp>telnet_port</samp></strong></dt> - <dd>disallow ftps for people coming from outside your - domain.</dd> + <dd> + <p>disallow specifying a port in telnet G)oto's.</p> + </dd> - <dt>outside_news</dt> + <dt><strong><samp>useragent</samp></strong></dt> - <dd>disallow USENET news reading and posting for people - coming from outside you domain. This applies to "news", - "nntp", "newspost", and "newsreply" URLs, but not to - "snews", "snewspost", or "snewsreply" in case they are - supported.</dd> - - <dt>outside_rlogin</dt> - - <dd>disallow rlogins for people coming from outside - your domain.</dd> - - <dt>outside_telnet</dt> - - <dd>disallow telnets for people coming from outside - your domain.</dd> - - <dt>print</dt> - - <dd>disallow most print options.</dd> - - <dt>shell</dt> - - <dd>disallow shell escapes.</dd> - - <dt>suspend</dt> - - <dd>disallow <em>Control-Z</em> suspends with escape to - shell on Unix.</dd> - - <dt>telnet_port</dt> - - <dd>disallow specifying a port in telnet G)oto's.</dd> - - <dt>useragent</dt> - - <dd>disallow modifications of the User-Agent - header.</dd> + <dd> + <p>disallow modifications of the User-Agent + header.</p> + </dd> </dl> </dd> <dt><code><strong>-resubmit_posts</strong></code></dt> - <dd>toggles forced resubmissions (no-cache) of forms with - method POST when the documents they returned are sought - with the PREV_DOC (<em>left-arrow</em>) command or from the - <em>History Page</em>.</dd> + <dd> + <p>toggles forced resubmissions (no-cache) of forms with + method POST when the documents they returned are sought + with the PREV_DOC (<em>left-arrow</em>) command or from + the <em>History Page</em>.</p> + </dd> <dt><code><strong>-rlogin</strong></code></dt> - <dd>disable recognition of rlogin commands.</dd> + <dd> + <p>disable recognition of rlogin commands.</p> + </dd> <dt><code><strong>-scrollbar</strong></code></dt> - <dd>toggles showing scrollbar.</dd> + <dd> + <p>toggles showing scrollbar.</p> + </dd> <dt><code><strong>-scrollbar_arrow</strong></code></dt> - <dd>toggles showing arrows at ends of the scrollbar.</dd> + <dd> + <p>toggles showing arrows at ends of the scrollbar.</p> + </dd> <dt><code><strong>-selective</strong></code></dt> - <dd>require .www_browsable files to browse - directories.</dd> + <dd> + <p>require .www_browsable files to browse + directories.</p> + </dd> <dt> <code><strong>-session=</strong><em>FILENAME</em></code></dt> - <dd>resumes from specified file on startup and saves - session to that file on exit.</dd> + <dd> + <p>resumes from specified file on startup and saves + session to that file on exit.</p> + </dd> <dt> <code><strong>-sessionin=</strong><em>FILENAME</em></code></dt> - <dd>resumes session from specified file.</dd> + <dd> + <p>resumes session from specified file.</p> + </dd> <dt> <code><strong>-sessionout=</strong><em>FILENAME</em></code></dt> - <dd>saves session to specified file.</dd> + <dd> + <p>saves session to specified file.</p> + </dd> <dt><code><strong>-short_url</strong></code></dt> - <dd>show very long URLs in the status line with "..." to - represent the portion which cannot be displayed. The - beginning and end of the URL are displayed, rather than - suppressing the end.</dd> + <dd> + <p>show very long URLs in the status line with "..." to + represent the portion which cannot be displayed. The + beginning and end of the URL are displayed, rather than + suppressing the end.</p> + </dd> <dt><code><strong>-show_cursor</strong></code></dt> - <dd>If enabled the cursor will not be hidden in the right - hand corner but will instead be positioned at the start of - the currently selected link. Show cursor is the default for - systems without FANCY_CURSES capabilities. The default - configuration can be changed in userdefs.h or <a href= - "#lynx.cfg">lynx.cfg</a>. It also can be set and saved via - the “o”ptions menu. The command line switch - toggles the default.</dd> + <dd> + <p>If enabled the cursor will not be hidden in the right + hand corner but will instead be positioned at the start + of the currently selected link. Show cursor is the + default for systems without FANCY_CURSES capabilities. + The default configuration can be changed in userdefs.h or + <a href="#lynx.cfg">lynx.cfg</a>. It also can be set and + saved via the “o”ptions menu. The command + line switch toggles the default.</p> + </dd> <dt><code><strong>-show_rate</strong></code></dt> - <dd>If enabled the transfer rate is shown in bytes/second. - If disabled, no transfer rate is shown. Use lynx.cfg or the - options menu to select KiB/second and/or ETA.</dd> + <dd> + <p>If enabled the transfer rate is shown in bytes/second. + If disabled, no transfer rate is shown. Use lynx.cfg or + the options menu to select KiB/second and/or ETA.</p> + </dd> <dt><code><strong>-soft_dquotes</strong></code></dt> - <dd>toggles emulation of the old Netscape and Mosaic bug - which treated “<em>></em>” as a - co-terminator for double-quotes and tags.</dd> + <dd> + <p>toggles emulation of the old Netscape and Mosaic bug + which treated “<samp>></samp>” as a + co-terminator for double-quotes and tags.</p> + </dd> <dt><code><strong>-source</strong></code></dt> <dd> - works the same as dump but outputs HTML source instead of - formatted text. For example - <pre> -<tt> - lynx -source . >foo.html - </tt> + <p>works the same as dump but outputs HTML source instead + of formatted text. For example</p> + + <blockquote> + <pre> +lynx -source . >foo.html </pre> + </blockquote> <p>generates HTML source listing the files in the current directory. Each file is marked by an HREF relative to the parent directory. Add a trailing slash to make the HREF's relative to the current directory:</p> - <pre> -<tt> - lynx -source ./ >foo.html - </tt> + + <blockquote> + <pre> +lynx -source ./ >foo.html </pre> + </blockquote> </dd> <dt><code><strong>-stack_dump</strong></code></dt> - <dd>disable SIGINT cleanup handler.</dd> + <dd> + <p>disable SIGINT cleanup handler.</p> + </dd> <dt><code><strong>-startfile_ok</strong></code></dt> - <dd>allow non-http startfile and homepage with - <em>-validate</em>.</dd> + <dd> + <p>allow non-http startfile and homepage with + <em>-validate</em>.</p> + </dd> <dt><code><strong>-stderr</strong></code></dt> - <dd>When dumping a document using - <code><strong>-dump</strong></code> or - <code><strong>-source</strong></code>, Lynx normally does - not display alert (error) messages that you see on the - screen in the status line. Use the - <code><strong>-stderr</strong></code> option to tell Lynx - to write these messages to the standard error.</dd> + <dd> + <p>When dumping a document using + <code><strong>-dump</strong></code> or + <code><strong>-source</strong></code>, Lynx normally does + not display alert (error) messages that you see on the + screen in the status line. Use the + <code><strong>-stderr</strong></code> option to tell Lynx + to write these messages to the standard error.</p> + </dd> <dt><code><strong>-stdin</strong></code></dt> - <dd>read the startfile from standard input (UNIX - only).</dd> + <dd> + <p>read the startfile from standard input (UNIX + only).</p> + </dd> <dt> <code><strong>-syslog=</strong><em>text</em></code></dt> - <dd>information for syslog call.</dd> + <dd> + <p>information for syslog call.</p> + </dd> <dt><code><strong>-syslog-urls</strong></code></dt> - <dd>log requested URLs with syslog.</dd> + <dd> + <p>log requested URLs with syslog.</p> + </dd> <dt><code><strong>-tagsoup</strong></code></dt> - <dd>initialize DTD with "TagSoup" tables, <a href= - "keystrokes/option_help.html#tagsoup">more - details</a>.</dd> + <dd> + <p>initialize DTD with "TagSoup" tables, <a href= + "keystrokes/option_help.html#tagsoup">more + details</a>.</p> + </dd> <dt><code><strong>-telnet</strong></code></dt> - <dd>disable recognition of telnet commands.</dd> + <dd> + <p>disable recognition of telnet commands.</p> + </dd> <dt><code><strong>-term=</strong><em>TERM</em></code></dt> - <dd>tell Lynx what terminal type to assume it is talking - to. (This may be useful for remote execution, when, for - example, Lynx connects to a remote TCP/IP port that starts - a script that, in turn, starts another Lynx process.)</dd> + <dd> + <p>tell Lynx what terminal type to assume it is talking + to. (This may be useful for remote execution, when, for + example, Lynx connects to a remote TCP/IP port that + starts a script that, in turn, starts another Lynx + process.)</p> + </dd> <dt><code><strong>-timeout=</strong><em>N</em></code></dt> - <dd>For win32, sets the network read-timeout, where - <em>N</em> is given in seconds.</dd> + <dd> + <p>For win32, sets the network read-timeout, where + <em>N</em> is given in seconds.</p> + </dd> <dt><code><strong>-tlog</strong></code></dt> - <dd>toggles use of a <em>Lynx Trace Log</em> for the - session. The log is named <em>Lynx.trace</em> and is - created in the home directory when Lynx trace mode is - turned on via the <em>-trace</em> command line switch (see - below), or via the TRACE_TOGGLE (<em>Control-T</em>) - keystroke command. Once a log is started for the session, - all trace and other stderr messages are written to the log. - The contents of the log can be examined during the session - via the TRACE_LOG (normally, “<em>;</em>”) - keystroke command. If use of a Lynx Trace Log is turned - off, any trace output will go to the standard error - stream.</dd> + <dd> + <p>toggles use of a <em>Lynx Trace Log</em> for the + session. The log is named <em>Lynx.trace</em> and is + created in the home directory when Lynx trace mode is + turned on via the <em>-trace</em> command line switch + (see below), or via the TRACE_TOGGLE (<em>Control-T</em>) + keystroke command. Once a log is started for the session, + all trace and other stderr messages are written to the + log. The contents of the log can be examined during the + session via the TRACE_LOG (normally, + “<samp>;</samp>”) keystroke command. If use + of a Lynx Trace Log is turned off, any trace output will + go to the standard error stream.</p> + </dd> <dt><code><strong>-tna</strong></code></dt> - <dd>turns on <a href="#tna">"Textfields Need - Activation"</a> mode.</dd> + <dd> + <p>turns on <a href="#tna">"Textfields Need + Activation"</a> mode.</p> + </dd> <dt><code><strong>-trace</strong></code></dt> - <dd>turns on Lynx trace mode. If a Lynx Trace Log - (<em>Lynx.trace</em> in the home directory) has been - started for the current session, all trace messages are - written to that log, and can be examined during the session - via the TRACE_LOG (normally, “<em>;</em>”) - command. If no Trace Log file is in use, trace messages go - to stderr.</dd> + <dd> + <p>turns on Lynx trace mode. If a Lynx Trace Log + (<em>Lynx.trace</em> in the home directory) has been + started for the current session, all trace messages are + written to that log, and can be examined during the + session via the TRACE_LOG (normally, + “<samp>;</samp>”) command. If no Trace Log + file is in use, trace messages go to stderr.</p> + </dd> <dt> <code><strong>-trace_mask=</strong><em>value</em></code></dt> <dd> - turn on optional traces, which may result in very large - trace files. Logically OR the values to combine options: + <p>turn on optional traces, which may result in very + large trace files. Logically OR the values to combine + options:</p> <dl> <dt>1</dt> - <dd>SGML character parsing states</dd> + <dd> + <p>SGML character parsing states</p> + </dd> <dt>2</dt> - <dd>color-style</dd> + <dd> + <p>color-style</p> + </dd> <dt>4</dt> - <dd>TRST (table layout)</dd> + <dd> + <p>TRST (table layout)</p> + </dd> <dt>8</dt> - <dd>config (lynx.cfg and .lynxrc contents)</dd> + <dd> + <p>config (lynx.cfg and .lynxrc contents)</p> + </dd> <dt>16</dt> - <dd>binary string copy/append, used in form data - construction.</dd> + <dd> + <p>binary string copy/append, used in form data + construction.</p> + </dd> </dl> </dd> <dt><code><strong>-traversal</strong></code></dt> - <dd>traverse all http links derived from startfile. When - used with <em>-crawl</em>, each link that begins with the - same string as startfile is output to a file, intended for - indexing. See CRAWL.announce for more information.</dd> + <dd> + <p>traverse all http links derived from startfile. When + used with <em>-crawl</em>, each link that begins with the + same string as startfile is output to a file, intended + for indexing. See CRAWL.announce for more + information.</p> + </dd> <dt><code><strong>-trim_input_fields</strong></code></dt> - <dd>trim input text/textarea fields in forms.</dd> + <dd> + <p>trim input text/textarea fields in forms.</p> + </dd> <dt><code><strong>-underscore</strong></code></dt> - <dd>toggles use of _underline_ format in dumps.</dd> + <dd> + <p>toggles use of _underline_ format in dumps.</p> + </dd> <dt><code><strong>-use_mouse</strong></code></dt> - <dd>turn on mouse support, if available.</dd> + <dd> + <p>turn on mouse support, if available.</p> + </dd> <dt> <code><strong>-useragent=</strong><em>STRING</em></code></dt> - <dd>set different Lynx User-Agent header. Lynx produces a - warning on startup if the <em>STRING</em> does not contain - "Lynx" or "L_y_n_x", see the <a href="#noteUA">note</a> in - the Options Menu section for rationale.</dd> + <dd> + <p>set different Lynx User-Agent header. Lynx produces a + warning on startup if the <em>STRING</em> does not + contain "Lynx" or "L_y_n_x", see the <a href= + "#noteUA">note</a> in the Options Menu section for + rationale.</p> + </dd> <dt><code><strong>-validate</strong></code></dt> - <dd>accept only http URLs (meant for validation).</dd> + <dd> + <p>accept only http URLs (meant for validation).</p> + </dd> - <dd>This flag implies security restrictions generally more - severe than <em>-anonymous</em>: restriction options as for - <em>-restrictions=all</em>, with the notable exception that - goto remains enabled for http and https URLs; in addition, - the PRINT and DOWNLOAD commands are completely disabled, - and use of a Trace Log file is forced off.</dd> + <dd> + <p>This flag implies security restrictions generally more + severe than <em>-anonymous</em>: restriction options as + for <em>-restrictions=all</em>, with the notable + exception that goto remains enabled for http and https + URLs; in addition, the PRINT and DOWNLOAD commands are + completely disabled, and use of a Trace Log file is + forced off.</p> + </dd> - <dd>Any relaxing of restriction that might be implied by an - also present (or implied) <em>-anonymous</em> flag is - overridden, the only way to possibly relax <em>some</em> of - the restrictions to the level applicable for "anononymous" - accounts is with an explicit - <em>-restrictions=default</em>.</dd> + <dd> + <p>Any relaxing of restriction that might be implied by + an also present (or implied) <em>-anonymous</em> flag is + overridden, the only way to possibly relax <em>some</em> + of the restrictions to the level applicable for + "anononymous" accounts is with an explicit + <em>-restrictions=default</em>.</p> + </dd> <dt><code><strong>-verbose</strong></code></dt> - <dd>toggles [LINK], [IMAGE] and [INLINE] comments with - filenames of these images.</dd> + <dd> + <p>toggles [LINK], [IMAGE] and [INLINE] comments with + filenames of these images.</p> + </dd> <dt><code><strong>-version</strong></code></dt> - <dd>print version information.</dd> + <dd> + <p>print version information.</p> + </dd> <dt><code><strong>-vikeys</strong></code></dt> - <dd>enable vi-like key movement.</dd> + <dd> + <p>enable vi-like key movement.</p> + </dd> <dt><code><strong>-wdebug</strong></code></dt> - <dd>enable Waterloo tcp/ip packet debug (print to watt - debugfile). This applies only to DOS versions compiled with - WATTCP or WATT-32.</dd> + <dd> + <p>enable Waterloo tcp/ip packet debug (print to watt + debugfile). This applies only to DOS versions compiled + with WATTCP or WATT-32.</p> + </dd> <dt> <code><strong>-width=</strong><em>NUMBER</em></code></dt> - <dd>number of columns for formatting of dumps, default is - 80.</dd> + <dd> + <p>number of columns for formatting of dumps, default is + 80.</p> + </dd> <dt><code><strong>-with_backspaces</strong></code></dt> - <dd>emit backspaces in output if -dumping or -crawling - (like <code>man</code> does).</dd> + <dd> + <p>emit backspaces in output if -dumping or -crawling + (like <code>man</code> does).</p> + </dd> </dl> </dd> </dl> <p>No options are required, nor is a startfile argument required. White space can be used in place of equal sign separators - (“<em>=</em>”) appearing in the option list above. It - can not be used in place of the equal signs in forms like - "-option=on" and "-option=off" for simple switches and toggles, - for which "-option" alone (without a value) is valid.</p> + (“<samp>=</samp>”) appearing in the option list + above. It can not be used in place of the equal signs in forms + like "-option=on" and "-option=off" for simple switches and + toggles, for which "-option" alone (without a value) is + valid.</p> <p>[<a href="#ToC-Invoking">ToC</a>]</p> @@ -4396,10 +5143,10 @@ the other two cannot be saved between sessions. <p>To view your current configuration derived from lynx.cfg and any included configuration files, press <em>“g”</em> - and type in “<em>lynxcfg:</em>”. If you are using the - forms-based <em>Options Menu</em>, you may press + and type in “<samp>lynxcfg:</samp>”. If you are using + the forms-based <em>Options Menu</em>, you may press <em>“o”</em> for the Options Menu and follow the - “<em>Check your lynx.cfg</em>'s link near the bottom.</p> + <em>Check your lynx.cfg</em>'s link near the bottom.</p> <p>However, for those who have a restricted account many Lynx features may be disabled by the system administrator, you diff --git a/src/LYShowInfo.c b/src/LYShowInfo.c index 3bf64bd1..4c97e986 100644 --- a/src/LYShowInfo.c +++ b/src/LYShowInfo.c @@ -1,4 +1,4 @@ -/* $LynxId: LYShowInfo.c,v 1.76 2013/10/03 01:01:34 tom Exp $ */ +/* $LynxId: LYShowInfo.c,v 1.77 2018/03/02 01:53:43 tom Exp $ */ #include <HTUtils.h> #include <HTFile.h> #include <HTParse.h> @@ -28,7 +28,8 @@ #define BEGIN_DL(text) fprintf(fp0, "<h2>%s</h2>\n<dl compact>", LYEntifyTitle(&buffer, text)) #define END_DL() fprintf(fp0, "\n</dl>\n") -#define ADD_SS(label,value) dt_String(fp0, label, value) +#define ADD_SS(label,value) dt_String(fp0, label, value, FALSE) +#define ADD_WW(label,value) dt_String(fp0, label, value, TRUE) #define ADD_NN(label,value,units) dt_Number(fp0, label, (long) value, units) static int label_columns; @@ -67,7 +68,8 @@ const char *LYVersionDate(void) static void dt_String(FILE *fp, const char *label, - const char *value) + const char *value, + BOOL allow_wide) { int have; int need; @@ -86,7 +88,10 @@ static void dt_String(FILE *fp, fprintf(fp, "<dt>"); while (need++ < label_columns) fprintf(fp, " "); - fprintf(fp, "<em>%s</em> %s\n", the_label, the_value); + if (LYwideLines && allow_wide) + fprintf(fp, "<em>%s</em><pre>%s</pre>\n", the_label, the_value); + else + fprintf(fp, "<em>%s</em>%s\n", the_label, the_value); FREE(the_label); FREE(the_value); @@ -108,7 +113,7 @@ static void dt_Number(FILE *fp0, static void dt_URL(FILE *fp0, const char *address) { - ADD_SS(gettext("URL:"), address); + ADD_WW(gettext("URL:"), address); /* * If the display handles UTF-8, and if the address uses %xy formatted |