summaryrefslogtreecommitdiffstats
path: root/lynx_help
diff options
context:
space:
mode:
Diffstat (limited to 'lynx_help')
-rw-r--r--lynx_help/Lynx_users_guide.html5729
-rw-r--r--lynx_help/about_lynx.html113
-rw-r--r--lynx_help/help_files.txt38
-rw-r--r--lynx_help/keystrokes/alt_edit_help.html128
-rw-r--r--lynx_help/keystrokes/bashlike_edit_help.html277
-rw-r--r--lynx_help/keystrokes/bookmark_help.html58
-rw-r--r--lynx_help/keystrokes/cookie_help.html76
-rw-r--r--lynx_help/keystrokes/dired_help.html90
-rw-r--r--lynx_help/keystrokes/edit_help.html191
-rw-r--r--lynx_help/keystrokes/environments.html558
-rw-r--r--lynx_help/keystrokes/follow_help.html286
-rw-r--r--lynx_help/keystrokes/gopher_types_help.html87
-rw-r--r--lynx_help/keystrokes/history_help.html58
-rw-r--r--lynx_help/keystrokes/keystroke_help.html177
-rw-r--r--lynx_help/keystrokes/movement_help.html78
-rw-r--r--lynx_help/keystrokes/option_help.html823
-rw-r--r--lynx_help/keystrokes/other_help.html196
-rw-r--r--lynx_help/keystrokes/print_help.html62
-rw-r--r--lynx_help/keystrokes/scrolling_help.html117
-rw-r--r--lynx_help/keystrokes/test_display.html82
-rw-r--r--lynx_help/keystrokes/visited_help.html63
-rw-r--r--lynx_help/keystrokes/xterm_help.html52
-rw-r--r--lynx_help/lynx-dev.html101
-rw-r--r--lynx_help/lynx_help_main.html180
-rw-r--r--lynx_help/lynx_url_support.html796
25 files changed, 10416 insertions, 0 deletions
diff --git a/lynx_help/Lynx_users_guide.html b/lynx_help/Lynx_users_guide.html
new file mode 100644
index 0000000..a5b270f
--- /dev/null
+++ b/lynx_help/Lynx_users_guide.html
@@ -0,0 +1,5729 @@
+<!-- $LynxId: Lynx_users_guide.html,v 1.157 2023/01/03 00:11:31 Jens.Schleusener Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Lynx Users Guide v2.8.9</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "This is the user's guide to Lynx, giving detailed information on how to use the program, and how to change its configuration using the options menu.">
+</head>
+<body>
+ <h1>Lynx Users Guide v2.8.9</h1>
+
+ <p>Lynx is a fully-featured <em>World Wide Web</em>
+ (<em>WWW</em>) client for users running cursor-addressable,
+ character-cell display devices (e.g., vt100 terminals, vt100
+ emulators running on PCs or Macs, or any other character-cell
+ display). It will display <em>Hypertext Markup Language</em>
+ (<em>HTML</em>) documents containing links to files on the local
+ system, as well as files on remote systems running <em>http</em>,
+ <em>gopher</em>, <em>ftp</em>, <em>wais</em>, <em>nntp</em>,
+ <em>finger</em>, or <em>cso</em>/<em>ph</em>/<em>qi</em> servers,
+ and services accessible via logins to <em>telnet</em>,
+ <em>tn3270</em> or <em>rlogin</em> accounts (see <a href=
+ "lynx_url_support.html">URL Schemes Supported by Lynx</a>).
+ <a href="#Hist">Current</a> versions of Lynx run on Unix, VMS,
+ Windows3.x/9x/NT and later, 386DOS and OS/2 EMX.</p>
+
+ <p>Lynx can be used to access information on the <em>WWW</em>, or
+ to build information systems intended primarily for local access.
+ For example, Lynx has been used to build several <em>Campus Wide
+ Information Systems</em> (<em>CWIS</em>). In addition, Lynx can
+ be used to build systems isolated within a single LAN.</p>
+
+ <h2 id="TOC"><a name="Contents" id="Contents">Table of
+ Contents</a></h2>
+
+ <ul>
+ <li><a href="#Help" name="ToC-Help" id="ToC-Help">Lynx online
+ help</a></li>
+
+ <li><a href="#Local" name="ToC-Local" id="ToC-Local">Viewing
+ local files with Lynx</a></li>
+
+ <li><a href="#Leaving" name="ToC-Leaving" id=
+ "ToC-Leaving">Leaving Lynx</a></li>
+
+ <li><a href="#Remote" name="ToC-Remote" id=
+ "ToC-Remote">Starting Lynx with a Remote File</a></li>
+
+ <li><a href="#EnVar" name="ToC-EnVar" id="ToC-EnVar">Starting
+ Lynx with the WWW_HOME environment variable.</a></li>
+
+ <li><a href="#IntraDocNav" name="ToC-IntraDocNav" id=
+ "ToC-IntraDocNav">Navigating hypertext documents with Lynx</a></li>
+
+ <li><a href="#Disposing" name="ToC-Disposing" id=
+ "ToC-Disposing">Printing, Mailing, and Saving rendered files to
+ disk.</a></li>
+
+ <li><a href="#LocalSource" name="ToC-LocalSource" id=
+ "ToC-LocalSource">Viewing the HTML document source and editing
+ documents</a></li>
+
+ <li><a href="#RemoteSource" name="ToC-RemoteSource" id=
+ "ToC-RemoteSource">Downloading and Saving source files.</a></li>
+
+ <li><a href="#ReDo" name="ToC-ReDo" id="ToC-ReDo">Reloading
+ files and refreshing the display</a></li>
+
+ <li><a href="#Search" name="ToC-Search" id="ToC-Search">Lynx
+ searching commands</a></li>
+
+ <li><a href="#InteractiveOptions" name="ToC-InteractiveOptions"
+ id="ToC-InteractiveOptions">Lynx Options Menu</a></li>
+
+ <li><a href="#Mail" name="ToC-Mail" id="ToC-Mail">Comments and
+ mailto: links</a></li>
+
+ <li><a href="#News" name="ToC-News" id="ToC-News">USENET News
+ posting</a></li>
+
+ <li><a href="#Bookmarks" name="ToC-Bookmarks" id=
+ "ToC-Bookmarks">Lynx bookmarks</a></li>
+
+ <li><a href="#Jumps" name="ToC-Jumps" id="ToC-Jumps">Jump
+ command</a></li>
+
+ <li><a href="#DirEd" name="ToC-DirEd" id="ToC-DirEd">Directory
+ Editing</a></li>
+
+ <li><a href="#ColorMouse" name="ToC-ColorMouse" id=
+ "ToC-ColorMouse">Using Color &amp; the Mouse</a></li>
+
+ <li><a href="#MiscKeys" name="ToC-MiscKeys" id=
+ "ToC-MiscKeys">Scrolling and Other useful commands</a></li>
+
+ <li><a href="#Forms" name="ToC-Forms" id="ToC-Forms">Lynx and
+ HTML Forms</a> | <a href="#Images" name="ToC-Images" id=
+ "ToC-Images">Lynx and HTML Images</a></li>
+
+ <li><a href="#Tables" name="ToC-Tables" id="ToC-Tables">Lynx
+ and HTML Tables</a> | <a href="#Tabs" name="ToC-Tabs" id=
+ "ToC-Tabs">Lynx and HTML Tabs</a></li>
+
+ <li><a href="#Frames" name="ToC-Frames" id="ToC-Frames">Lynx
+ and HTML Frames</a> | <a href="#Banners" name="ToC-Banners" id=
+ "ToC-Banners">Lynx and HTML Banners</a></li>
+
+ <li><a href="#Footnotes" name="ToC-Footnotes" id=
+ "ToC-Footnotes">Lynx and HTML Footnotes</a> | <a href="#Notes"
+ name="ToC-Notes" id="ToC-Notes">Lynx and HTML Notes</a></li>
+
+ <li><a href="#Lists" name="ToC-Lists" id="ToC-Lists">Lynx and
+ HTML Lists</a></li>
+
+ <li><a href="#Quotes" name="ToC-Quotes" id="ToC-Quotes">Lynx
+ and HTML Quotes</a></li>
+
+ <li><a href="#Eightbit" name="ToC-Eightbit" id=
+ "ToC-Eightbit">Lynx and HTML Internationalization: 8bit,
+ UNICODE, etc.</a></li>
+
+ <li><a href="#USEMAP" name="ToC-USEMAP" id="ToC-USEMAP">Lynx
+ and Client-Side-Image-Maps</a></li>
+
+ <li><a href="#Refresh" name="ToC-Refresh" id="ToC-Refresh">Lynx
+ and Client-Side-Pull</a></li>
+
+ <li><a href="#Cookies" name="ToC-Cookies" id="ToC-Cookies">Lynx
+ and State Management</a> (Me want <em>cookie</em>!)</li>
+
+ <li><a href="#Cache" name="ToC-Cache" id="ToC-Cache">Lynx and
+ Cached Documents</a></li>
+
+ <li><a href="#Sessions" name="ToC-Sessions" id=
+ "ToC-Sessions">Lynx and Sessions</a></li>
+
+ <li><a href="#Invoking" name="ToC-Invoking" id=
+ "ToC-Invoking">The Lynx command line</a></li>
+
+ <li><a href="#Environment" name="ToC-Environment" id=
+ "ToC-Environment">Environment variables used by Lynx</a></li>
+
+ <li><a href="#lynx.cfg" name="ToC-lynx.cfg" id=
+ "ToC-lynx.cfg">Main configuration file lynx.cfg</a></li>
+
+ <li><a href="#Hist" name="ToC-Hist" id="ToC-Hist">Lynx
+ development history</a></li>
+ </ul>
+
+ <h2 id="id-Help"><a name="Help" id="Help">Lynx online help</a></h2>
+
+ <p>Online help is available while viewing any document. Press the
+ &ldquo;<samp>?</samp>&rdquo; or &ldquo;<samp>H</samp>&rdquo; key
+ (or the &ldquo;<samp>h</samp>&rdquo; 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
+ &ldquo;<samp>K</samp>&rdquo; key (or the
+ &ldquo;<samp>k</samp>&rdquo; 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 &ldquo;g&rdquo; command, followed by
+ &ldquo;LYNXMESSAGES:&rdquo;.</p>
+
+ <p>[<a href="#ToC-Help">ToC</a>]</p>
+
+ <h2 id="id-Local"><a name="Local" id="Local">Viewing local files
+ with Lynx</a></h2>
+
+ <p>Lynx can be started by entering the Lynx command along with
+ the name of a file to display. For example these commands could
+ all be used to display an arbitrary ASCII text or HTML file:</p>
+
+ <dl>
+ <dt>UNIX</dt>
+
+ <dd><code>lynx filename</code>
+ </dd>
+
+ <dd><code>lynx /home/my-dir/filename</code>
+ </dd>
+
+ <dd><code>lynx ~/filename</code>
+ </dd>
+
+ <dt>VMS</dt>
+
+ <dd><code>lynx filename</code>
+ </dd>
+
+ <dd><code>lynx dua5:[my-directory]filename</code>
+ </dd>
+
+ <dd><code>lynx /dua5/my-directory/filename</code>
+ </dd>
+
+ <dd><code>lynx ~/filename</code>
+ </dd>
+
+ <dd><code>lynx sys$login:filename</code>
+ </dd>
+
+ <dd><code>lynx /sys$login/filename</code>
+ </dd>
+
+ <dt>Win32/DOS</dt>
+
+ <dd><code>lynx file:///filename</code>
+ </dd>
+
+ <dd><code>lynx filename</code>
+ </dd>
+
+ <dd><code>lynx c:/dir/filename</code>
+ </dd>
+
+ <dd><code>lynx //n/dir/filename</code>
+ </dd>
+ </dl>
+
+ <p>When executed, Lynx will clear the screen and display as much
+ of the specified file as will fit on the screen. Pressing a
+ <em>down-arrow</em> will bring up the next screen, and pressing
+ an <em>up-arrow</em> will bring up the previous screen. If no
+ file is specified at startup, a default file will be displayed,
+ depending on settings e.g., in <em>lynx.cfg</em>.</p>
+
+ <p>Lynx will display local files written in the <em>HyperText
+ Markup Language</em> (<em>HTML</em>), if the file's name ends
+ with the characters <em>.html</em>, <em>.htm</em>,
+ <em>.shtml</em>, <em>.htmlx</em>, <em>.html3</em>, or
+ <em>.ht3</em>. HTML is a file format that allows users to create
+ a file that contains (among other things) hypertext links to
+ other files. Several files linked together may be described as a
+ <em>hypertext document</em>. If the filename does not have one of
+ the suffixes mapped by Lynx to HTML, the <em>-force_html</em>
+ command line option can be included to force treatment of the
+ file as hypertext.</p>
+
+ <p>When Lynx displays an HTML file, it shows links as "bold face"
+ text, except for one link, which is shown as "highlighted" text.
+ Whether "boldface" or "highlighted" text shows up as reverse
+ video, boldface type, or a color change, etc. depends on the
+ display device being used (and the way in which that device has
+ been configured). Lynx has no control over the exact presentation
+ of links.</p>
+
+ <p>The one link displayed as "highlighted" text is the currently
+ "selected" link. Lynx will display the file associated with the
+ selected link when a <em>right-arrow</em> or a <em>Return</em>
+ key is pressed. To select a particular link, press the
+ <em>up-arrow</em> or <em>down-arrow</em> keys until the desired
+ link becomes "highlighted," and then press the
+ <em>right-arrow</em> or <em>Return</em> key to view the linked
+ information. Information included in the HTML file tells Lynx
+ where to find the linked file and what kind of server will
+ provide it (i.e., HTTP, Gopher, etc.).</p>
+
+ <p>Lynx renders HTML files and saves the rendition (and the
+ source, if so configured in the <a href="#lynx.cfg">lynx.cfg</a>
+ 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 &ldquo;<samp>x</samp>&rdquo; and
+ &ldquo;<samp>X</samp>&rdquo;, 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
+ &ldquo;<samp>D</samp>&rdquo; 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.
+ Additional download methods may be defined in the <a href=
+ "#lynx.cfg">lynx.cfg</a> file. Programs like kermit, zmodem and
+ FTP are some possible options.</p>
+
+ <p>[<a href="#ToC-Local">ToC</a>]</p>
+
+ <h2 id="id-Leaving"><a name="Leaving" id="Leaving">Leaving
+ Lynx</a></h2>
+
+ <p>To exit Lynx use the &ldquo;<samp>q</samp>&rdquo; command. You
+ will be asked whether you really want to quit. Answering
+ &ldquo;<samp>y</samp>&rdquo; will exit and
+ &ldquo;<samp>n</samp>&rdquo; will return you to the current
+ document. Use &ldquo;<samp>Q</samp>&rdquo; or <em>Control-D</em>
+ to quit without verification.</p>
+
+ <p>[<a href="#ToC-Leaving">ToC</a>]</p>
+
+ <h2 id="id-Remote"><a name="Remote" id="Remote">Starting Lynx
+ with a Remote File</a></h2>
+
+ <p>If you wish to view a remote file (that is, a file residing on
+ some computer system other than the one upon which you are
+ running Lynx) without first viewing a local file, you must
+ identify that file by using a Uniform Resource Locator (URL).
+ URLs take the general form:</p>
+
+ <blockquote>
+ <p><code>PROTOCOL :// HOST / PATH</code>
+ </p>
+ </blockquote>
+
+ <p>where</p>
+
+ <dl>
+ <dt><code>PROTOCOL</code>
+ </dt>
+
+ <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>
+ <p>is the Internet address of the computer system on which
+ the server is running, and</p>
+ </dd>
+
+ <dt><code>PATH</code>
+ </dt>
+
+ <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>
+
+ <dl>
+ <dt>HTTP (HyperText Transfer Protocol)</dt>
+
+ <dd><code>https://invisible-island.net/lynx/</code>
+ </dd>
+
+ <dt>Gopher</dt>
+
+ <dd><code>gopher://gopher.micro.umn.edu/11/</code>
+ </dd>
+
+ <dt>FTP (File Transfer Protocol)</dt>
+
+ <dd><code>ftp://ftp2.cc.ukans.edu/pub/lynx/README</code>
+ </dd>
+
+ <dt>WAIS (Wide Area Information Service protocol)</dt>
+
+ <dd><code>wais://cnidr.org/directory-of-servers</code>
+ </dd>
+
+ <dt>A URL may be specified to Lynx on the command line, as
+ in:</dt>
+
+ <dd><code>lynx
+ http://kufacts.cc.ukans.edu/cwis/kufacts_start.html</code>
+ </dd>
+ </dl>
+
+ <p>Lynx also will attempt to create a complete URL if you include
+ adequate portions of it in the startfile argument. For
+ example:</p>
+
+ <pre>
+ <em>wfbr</em> will be expanded to:
+ <em>http://www.wfbr.edu/</em> and:
+ <em>ftp.more.net/pub</em> will be expanded to:
+ <em>ftp://ftp.more.net/pub</em>
+</pre>
+ <p>See <a href="lynx_url_support.html">URL Schemes Supported by
+ Lynx</a> for more detailed information.</p>
+
+ <p>[<a href="#ToC-Remote">ToC</a>]</p>
+
+ <h2 id="id-EnVar"><a name="EnVar" id="EnVar">Starting Lynx with
+ the WWW_HOME environment variable.</a></h2>
+
+ <p>You may also specify a starting file for Lynx using the
+ WWW_HOME environment variable,</p>
+
+ <dl>
+ <dt>UNIX</dt>
+
+ <dd>
+ <dl>
+ <dt>ksh</dt>
+
+ <dd><code>export WWW_HOME=http://www.w3.org/</code>
+ </dd>
+
+ <dt>csh</dt>
+
+ <dd><code>setenv WWW_HOME http://www.w3.org/</code>
+ </dd>
+ </dl>
+ </dd>
+
+ <dt>VMS</dt>
+
+ <dd><code>define "WWW_HOME" "http://www.w3.org/"</code>
+ </dd>
+
+ <dt>win32</dt>
+
+ <dd><code>WWW_HOME=http://www.w3.org/ [or in registry]</code>
+ </dd>
+ </dl>
+
+ <p>Note that on VMS the double-quoting <em>must</em> be included
+ to preserve casing.</p>
+
+ <p>[<a href="#ToC-EnVar">ToC</a>]</p>
+
+ <h2 id="id-IntraDocNav"><a name="IntraDocNav" id=
+ "IntraDocNav">Navigating hypertext documents with Lynx</a></h2>
+
+ <p>The process of moving within a hypertext web, selecting and
+ displaying links is known as "navigation." With Lynx almost all
+ navigation can be accomplished with the arrow keys and the
+ numeric keypad.</p>
+
+ <pre>
+ +-------+-------+-------+
+ | TOP | /|\ | Page |
+ arrow keys | of | | | UP |
+ | text 7| | 8| 9|
+ +---------+ +-------+-------+-------+
+ | SELECT | | | | |
+ | prev /|\| | &lt;--- | | ---&gt; |
+ | link | | | 4| 5| 6|
+ +---------+---------+---------+ +-------+-------+-------+
+ | BACK | SELECT | DISPLAY | | END | | | Page |
+ |&lt;-- prev | next | | sel. --&gt;| | of | | | DOWN |
+ | doc. | link \|/| link | | text 1| \|/ 2| 3|
+ +---------+---------+---------+ +-------+-------+-------+
+</pre>
+ <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>.</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>.</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
+ &ldquo;<samp>V</samp>&rdquo;, 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
+ &ldquo;<samp>m</samp>&rdquo; and
+ &ldquo;<samp>M</samp>&rdquo;, 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 &ldquo;<samp>l</samp>&rdquo; and
+ &ldquo;<samp>A</samp>&rdquo; 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 &ldquo;<samp>i</samp>&rdquo; 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>
+
+ <p>If you choose a link to a server with active access
+ authorization, Lynx will automatically prompt for a username and
+ a password. If you give the correct information, you will then be
+ served the requested information. Lynx will automatically send
+ your username and password to the same server if it is needed
+ again.</p>
+
+ <p>[<a href="#ToC-IntraDocNav">ToC</a>]</p>
+
+ <h2 id="id-Disposing"><a name="Disposing" id=
+ "Disposing">Printing, Mailing, and Saving rendered files to
+ disk.</a></h2>
+
+ <p>Rendered HTML documents, and plain text files, may be printed
+ using the &ldquo;<samp>p</samp>&rdquo; command while viewing the
+ document. After pressing the &ldquo;<samp>p</samp>&rdquo; 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
+ users"). In particular, the <em>Save to a local file</em> option
+ allows you to save the document into a file on your disk space.
+ Additional print options may also be available as configured in
+ the <a href="#lynx.cfg">lynx.cfg</a> file.</p>
+
+ <p>Some options, such as <em>Save to a local file</em>, involve
+ prompting for an output filename. All output filename entries are
+ saved in a circular buffer, and any previous entries can be
+ retrieved for re-use by pressing the <em>up-arrow</em> or
+ <em>down-arrow</em> keys at the prompt.</p>
+
+ <p>Note that if you want exact copies of text files without any
+ expansions of TAB characters to spaces you should use the
+ <a href="#RemoteSource">Download</a> options.</p>
+
+ <p>[<a href="#ToC-Disposing">ToC</a>]</p>
+
+ <h2 id="id-LocalSource"><a name="LocalSource" id=
+ "LocalSource">Viewing the HTML document source and editing
+ documents</a></h2>
+
+ <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 &ldquo;<samp>\</samp>&rdquo; (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
+ unrendered, Lynx must reload it from the server or disk. When
+ viewing unrendered documents you may print them as any normal
+ document.</p>
+
+ <p>Selecting the <em>Print to a local file</em> option from the
+ Print Menu, makes it possible to save the source of the document
+ to disk so that you may have a local copy of the document source,
+ but it is better to <a href="#RemoteSource">Download</a> the
+ source.</p>
+
+ <p>NOTE: When saving an HTML document it is important to name the
+ document with a <em>.html</em> or <em>.htm</em> extension, if you
+ want to read it with Lynx again later.</p>
+
+ <p id="FileEdit">Lynx can allow users to edit documents that
+ reside on the local system. To enable editing, documents must be
+ referenced using a "file:" URL or by specifying a plain filename
+ on the command line as in the following two examples:</p>
+
+ <dl>
+ <dt>Command</dt>
+
+ <dd><code>lynx file://localhost/FULL/PATH/FILENAME</code>
+ </dd>
+
+ <dd><code>lynx path/filename.html</code>
+ </dd>
+ </dl>
+
+ <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 &ldquo;<samp>e</samp>&rdquo;
+ command. When the &ldquo;<samp>e</samp>&rdquo; 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
+ immediately examined.</p>
+
+ <p>[<a href="#ToC-LocalSource">ToC</a>]</p>
+
+ <h2 id="id-RemoteSource"><a name="RemoteSource" id=
+ "RemoteSource">Downloading and Saving source files.</a></h2>
+
+ <p>If the DOWNLOAD keystroke command
+ (&ldquo;<samp>d</samp>&rdquo; or &ldquo;<samp>D</samp>&rdquo;) 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.
+ Any number of download methods such as kermit and zmodem may be
+ 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
+ (<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>&lt;!--X-URL: http://www.site.foo/path/to/file.html
+ --&gt;<br>
+ &lt;BASE href="http://www.site.foo/path/to/file.html"&gt;</p>
+ </blockquote>
+
+ <p>at the start of the file so that relative URLs in the document
+ will still work. Even this modification can be prevented by
+ setting PREPEND_BASE_TO_SOURCE:FALSE in lynx.cfg.</p>
+
+ <p>Some options, such as <em>Save to disk</em>, involve prompting
+ for an output filename. All output filename entries are saved in
+ a circular buffer, and any previous entries can be retrieved for
+ re-use by pressing the <em>up-arrow</em> or <em>down-arrow</em>
+ keys at the prompt.</p>
+
+ <p>[<a href="#ToC-RemoteSource">ToC</a>]</p>
+
+ <h2 id="id-ReDo"><a name="ReDo" id="ReDo">Reloading files and
+ refreshing the display</a></h2>
+
+ <p>The RELOAD (<em>Control-R</em>) command will reload and
+ re-render the file that you are currently viewing. The REFRESH
+ (<em>Control-L</em> or <em>Control-W</em>) command will refresh
+ or wipe the screen to remove or correct any errors that may be
+ caused by operating system or other messages.</p>
+
+ <p>The NOCACHE (&ldquo;<samp>x</samp>&rdquo; or
+ &ldquo;<samp>X</samp>&rdquo;) 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>
+
+ <h2 id="id-Search"><a name="Search" id="Search">Lynx searching
+ commands</a></h2>
+
+ <p>Two commands activate searching in Lynx:
+ &ldquo;<samp>/</samp>&rdquo; and
+ &ldquo;<samp>s</samp>&rdquo;.</p>
+
+ <p>While viewing a normal document use the
+ &ldquo;<samp>/</samp>&rdquo; 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 &ldquo;<samp>s</samp>&rdquo; 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
+ URL and append your query string as a <em>?searchpart</em> (see
+ <a href="lynx_url_support.html">Supported URLs</a>).</p>
+
+ <p>All search words or strings which you have entered during a
+ 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 &ldquo;<samp>n</samp>&rdquo;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
+ useful for performing searches directly via WAIS or Gopher
+ servers in conjunction with the internal gateways for such
+ 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:</p>
+
+ <pre>
+ <em>&lt;ISINDEX PROMPT="Enter WAIS query:"
+ HREF="wais://net.bio.net/biologists-addresses"&gt;</em>
+</pre>
+ <p>for submitting a search of the Biologist's Addresses database
+ directly to the net.bio.net WAIS server.</p>
+
+ <p>[<a href="#ToC-Search">ToC</a>]</p>
+
+ <h2 id="id-InteractiveOptions"><a name="InteractiveOptions" id=
+ "InteractiveOptions">Lynx Options Menu</a></h2>
+
+ <p>The Lynx <em>Options Menu</em> may be accessed by pressing the
+ &ldquo;<samp>o</samp>&rdquo; key. It allows you to change options
+ at runtime, if you need to. Most changes are read from &amp;
+ 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:</p>
+
+ <ul>
+ <li><a name="item-form_based_options" href=
+ "#explain-form_based_options" id=
+ "item-form_based_options">form-based</a></li>
+
+ <li><a name="item-key_based_options" href=
+ "#explain-key_based_options" id=
+ "item-key_based_options">key-based</a></li>
+ </ul>
+
+ <p id="explain-form_based_options">The form-based menu shown
+ below is an HTML file generated at runtime, in which the user
+ fills in choices as in any ordinary HTML form.</p>
+
+ <pre>
+
+ <a href="#item-form_based_options" name=
+"example-form_based_options" id=
+"example-form_based_options">Options Menu (Lynx Version 2.9.0dev.7)</a>
+
+ Accept Changes - Reset Changes - Left Arrow cancels changes - HELP!
+
+ Save options to disk: [ ]
+ (options marked with (!) will not be saved)
+
+ General Preferences
+ User mode : <a href=
+"#optinfo-user_mode">[Advanced____]</a>
+ Editor : <a href=
+"#optinfo-editor">vile______________________________________</a>
+ Type of Search : <a href=
+"#optinfo-type_of_search">[Case insensitive]</a>
+
+ Security and Privacy
+ Cookies : <a href=
+"#optinfo-cookies">[ask user__]</a>
+ Invalid-Cookie Prompting (!) : <a href=
+"#optinfo-invalid_cookie_prompting">[prompt normally___]</a>
+ SSL Prompting (!) : <a href=
+"#optinfo-ssl_prompting">[prompt normally___]</a>
+
+ Keyboard Input
+ Keypad mode : <a href=
+"#optinfo-keypad_mode">[Numbers act as arrows_____________]</a>
+ Emacs keys : <a href=
+"#optinfo-emacs_keys">[OFF]</a>
+ VI keys : <a href=
+"#optinfo-vi_keys">[OFF]</a>
+ Line edit style : <a href=
+"#optinfo-line_edit_style">[Bash-like Bindings]</a>
+
+ Display and Character Set
+ Use locale-based character set : <a href=
+"#optinfo-locale_based_charset">[ON_]</a>
+ Use HTML5 charset replacements(!): <a href=
+"#optinfo-use_html5_charset">[OFF]</a>
+ Display character set : <a href=
+"#optinfo-display_charset">[UNICODE (UTF-8)________________]</a>
+ Assumed document character set(!): <a href=
+"#optinfo-assumed_document_charset">[iso-8859-1______]</a>
+ Internationalized domain names(!): <a href=
+"#optinfo-idna_mode">[IDNA TR46______]</a>
+ Raw 8-bit : <a href=
+"#optinfo-raw_8_bit">[OFF]</a>
+ X Display : <a href=
+"#optinfo-x_display">localhost:0.0_____________________________</a>
+
+ Document Appearance
+ Show color : <a href=
+"#optinfo-show_color">[ON____]</a>
+ Color style (!) : [lynx.lss___________]
+ Default colors (!) : [ON_]
+ Show cursor : <a href=
+"#optinfo-show_cursor">[OFF]</a>
+ Underline links (!) : <a href=
+"#optinfo-underline_links">[OFF]</a>
+ Show scrollbar : <a href=
+"#optinfo-show_scrollbar">[ON_]</a>
+ Popups for select fields : <a href=
+"#optinfo-popups_for_select">[ON_]</a>
+ HTML error recovery : <a href=
+"#optinfo-html_error_recovery">[strict (SortaSGML mode)]</a>
+ Bad HTML messages (!) : <a href=
+"#optinfo-bad_html_messages">[Warn, point to trace-file]</a>
+ Show images : <a href=
+"#optinfo-show_images">[ignore___]</a>
+ Verbose images : <a href=
+"#optinfo-verbose_images">[OFF__________]</a>
+ Collapse BR tags (!) : <a href=
+"#optinfo-collapse_br_tags">[OFF_____]</a>
+ Trim blank lines (!) : <a href=
+"#optinfo-trim_blank_lines">[trim-lines]</a>
+
+ Headers Transferred to Remote Servers
+ Personal mail address : <a href=
+"#optinfo-personal_mail_address">__________________________________________</a>
+ Personal name for mail : <a href=
+"#optinfo-personal_name_for_mail">__________________________________________</a>
+ Password for anonymous ftp : <a href=
+"#optinfo-password_for_anon_ftp">__________________________________________</a>
+ Preferred media type (!) : <a href=
+"#optinfo-preferred_media_type">[Accept lynx's internal types]</a>
+ Preferred encoding (!) : <a href=
+"#optinfo-preferred_encoding">[All_____]</a>
+ Preferred document character set : <a href=
+"#optinfo-preferred_doc_charset">_________________________________</a>
+ Preferred document language : <a href=
+"#optinfo-preferred_doc_language">en_______________________________</a>
+ HTTP protocol (!) : <a href=
+"#optinfo-http_protocol">[HTTP 1.0]</a>
+ Send User-Agent header (!) : <a href=
+"#optinfo-send_user_agent">[X]</a>
+ User-Agent header (!) : <a href=
+"#optinfo-user_agent">Lynx/2.8.9rel.1 libwww-FM/2.14 SSL-MM/1.4.</a>
+
+ Listing and Accessing Files
+ Use Passive FTP (!) : <a href=
+"#optinfo-use_passive_ftp">[ON_]</a>
+ FTP sort criteria : <a href=
+"#optinfo-ftp_sort_criteria">[By Date]</a>
+ Local directory sort criteria : <a href=
+"#optinfo-local_directory_sort_criteria">[Directories first]</a>
+ Local directory sort order : <a href=
+"#optinfo-local_directory_sort_order">[By Date_]</a>
+ Show dot files : <a href=
+"#optinfo-show_dot_files">[OFF]</a>
+ Pause when showing message (!) : <a href=
+"#optinfo-pause_when_showing_message">[ON_]</a>
+ Show transfer rate : <a href=
+"#optinfo-show_transfer_rate">[Show KiB/sec (2-digits), ETA__]</a>
+
+ Special Files and Screens
+ Multi-bookmarks : <a href=
+"#optinfo-multi_bookmarks">[ADVANCED]</a>
+ Review/edit Bookmarks files : Goto multi-bookmark menu
+ Auto Session (!) : <a href=
+"#optinfo-auto_session">[OFF]</a>
+ Session file (!) : <a href=
+"#optinfo-session_file">__________________________________________</a>
+ Visited Pages : <a href=
+"#optinfo-visited_pages">[By Last Visit Reversed_]</a>
+
+ View the file lynx.cfg.
+
+ Accept Changes - Reset Changes - Left Arrow cancels changes
+</pre>
+ <p id="explain-key_based_options">The key-based menu depends on
+ key-strokes to identify options which the user wants to change.
+ It is compiled into Lynx and is accessed by setting FORMS_OPTIONS
+ to TRUE in <code>lynx.cfg</code>.</p>
+
+ <pre>
+
+ <a href="#item-key_based_options" name=
+"example-key_based_options" id=
+"example-key_based_options">Options Menu (Lynx Version 2.9.0dev.7)</a>
+
+ <a href=
+"#optinfo-editor">(E)</a>ditor : emacs
+ <a href=
+"#optinfo-x_display">(D)</a>ISPLAY variable : aixtest.cc.ukans.edu:0.0
+ mu<a href=
+"#optinfo-multi_bookmarks">(L)</a>ti-bookmarks: OFF <a href=
+"#optinfo-bookmark_file">B)</a>ookmark file: lynx_bookmarks.html
+ <a href=
+"#optinfo-ftp_sort_criteria">(F)</a>TP sort criteria : By Filename
+ <a href=
+"#optinfo-personal_mail_address">(P)</a>ersonal mail address : montulli@netscape.com
+ <a href=
+"#optinfo-type_of_search">(S)</a>earching type : CASE INSENSITIVE
+ preferred document lan<a href=
+"#optinfo-preferred_doc_language">(G)</a>uage: en
+ preferred document c<a href=
+"#optinfo-preferred_doc_charset">(H)</a>arset : NONE
+ display <a href=
+"#optinfo-display_charset">(C)</a>haracter set : Western (ISO-8859-1)
+ raw 8-bit or CJK m<a href=
+"#optinfo-raw_8_bit">(O)</a>de : ON show color <a href=
+"#optinfo-show_color">(&amp;)</a> : OFF
+ <a href="#optinfo-vi_keys">(V)</a>I keys: OFF e<a href=
+"#optinfo-emacs_keys">(M)</a>acs keys: OFF sho<a href=
+"#optinfo-show_dot_files">(W)</a> dot files: OFF
+ popups for selec<a href=
+"#optinfo-popups_for_select">(T)</a> fields : ON show cursor <a href="#optinfo-show_cursor">(@)</a> : OFF
+ <a href=
+"#optinfo-keypad_mode">(K)</a>eypad mode : Numbers act as arrows
+ li<a href=
+"#optinfo-line_edit_style">(N)</a>e edit style : Default Binding
+ l<a href=
+"#optinfo-local_directory_sort_criteria">(I)</a>st directory style : Mixed style
+ <a href=
+"#optinfo-user_mode">(U)</a>ser mode : Advanced verbose images <a href="#optinfo-verbose_images">(!)</a> : ON
+ user <a href=
+"#optinfo-user_agent">(A)</a>gent : [User-Agent header]
+ local e<a href=
+"#optinfo-execution_links">(X)</a>ecution links : FOR LOCAL FILES ONLY
+</pre>
+ <p>An option can be changed by entering the capital letter or
+ character in parentheses for the option you wish to change (e.g.,
+ &ldquo;<samp>E</samp>&rdquo; for Editor or
+ &ldquo;<samp>@</samp>&rdquo; 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
+ key to toggle the choices and press the <em>Return</em> key to
+ finish the change.</p>
+
+ <p>For fields where you potentially have more than two choices,
+ popup windows may be evoked which function homologously to those
+ for select fields in <a href="#Forms">HTML Forms</a>. The popup
+ windows will be invoked only if you have popups for select fields
+ set to ON (see below). Otherwise, your cursor will be positioned
+ at the current choice, and you can press any key to cycle through
+ the choices, then press the <em>Return</em> key to finish the
+ change.</p>
+
+ <p>When you are done changing options use the
+ &ldquo;<samp>r</samp>&rdquo; command to return to Lynx or the
+ &ldquo;<samp>&gt;</samp>&rdquo; 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
+ <em>Options Menu</em>:</p>
+
+ <dl>
+ <dt><a name="optinfo-assumed_document_charset" id=
+ "optinfo-assumed_document_charset">Assumed document character
+ set</a>
+ </dt>
+
+ <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 &ldquo;Raw
+ 8-bit or CJK Mode&rdquo; is OFF.</p>
+ </dd>
+
+ <dt><a name="optinfo-auto_session" id=
+ "optinfo-auto_session">Auto Session</a>
+ </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><a name="optinfo-bad_html_messages" id=
+ "optinfo-bad_html_messages">Bad HTML messages</a>
+ </dt>
+
+ <dd>
+ <p>Suppress or redirect Lynx's messages about "Bad HTML":</p>
+
+ <dl>
+ <dt>Ignore</dt>
+
+ <dd>
+ <p>do not warn; no details are written to the
+ trace-file.</p>
+ </dd>
+
+ <dt>Add to trace-file</dt>
+
+ <dd>
+ <p>add the detailed warning message to the
+ trace-file.</p>
+ </dd>
+
+ <dt>Add to LYNXMESSAGES</dt>
+
+ <dd>
+ <p>add the detailed warning message to the message page
+ at "LYNXMESSAGES:".</p>
+ </dd>
+
+ <dt>Warn, point to trace-file</dt>
+
+ <dd>
+ <p>show a warning message on the status line; the
+ complete message is written to the trace-file.</p>
+ </dd>
+ </dl>
+ </dd>
+
+ <dt><a name="optinfo-bookmark_file" id=
+ "optinfo-bookmark_file">Bookmark file</a>
+ </dt>
+
+ <dd>
+ <p>When multi-bookmarks is OFF, this is the filename and
+ location of your default personal bookmark file. Enter
+ &ldquo;<samp>B</samp>&rdquo; 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.</p>
+
+ <p>Using the &ldquo;<samp>a</samp>&rdquo;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
+ &ldquo;<samp>B</samp>&rdquo; 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 &ldquo;<samp>a</samp>&rdquo;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><a name="optinfo-collapse_br_tags" id=
+ "optinfo-collapse_br_tags">Collapse BR tags</a>
+ </dt>
+
+ <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.,
+ &ldquo;collapse&rdquo;, 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><a name="optinfo-cookies" id="optinfo-cookies">Cookies</a>
+ </dt>
+
+ <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><a name="optinfo-display_charset" id=
+ "optinfo-display_charset">Display Character set</a>
+ </dt>
+
+ <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><a name="optinfo-editor" id="optinfo-editor">Editor</a>
+ </dt>
+
+ <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>
+
+ <p>If a full pathname is given, this helps Lynx provide for
+ detecting if options were also provided in this field. In
+ this case, it will also quote the pathname, allowing for
+ embedded blanks and other special characters that might
+ confuse the shell which starts the editor program.</p>
+ </dd>
+
+ <dt><a name="optinfo-emacs_keys" id="optinfo-emacs_keys">Emacs
+ keys</a>
+ </dt>
+
+ <dd>
+ <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).</p>
+
+ <p>Note: this has no direct effect on the line-editor's key
+ bindings.</p>
+ </dd>
+
+ <dt><a name="optinfo-execution_links" id=
+ "optinfo-execution_links">Execution links</a>
+ </dt>
+
+ <dd>
+ <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>
+ <p>Local execution scripts will never be executed</p>
+ </dd>
+
+ <dt>For Local files only</dt>
+
+ <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>
+ <p>All local execution scripts will be executed</p>
+ </dd>
+ </dl>
+ </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><a name="optinfo-ftp_sort_criteria" id=
+ "optinfo-ftp_sort_criteria">FTP sort criteria</a>
+ </dt>
+
+ <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><a name="optinfo-html_error_recovery" id=
+ "optinfo-html_error_recovery">HTML error recovery</a>
+ </dt>
+
+ <dd>
+ <p>Select the <a href=
+ "keystrokes/option_help.html#tagsoup">recovery mode</a> used
+ by Lynx.</p>
+ </dd>
+
+ <dt><a name="optinfo-http_protocol" id=
+ "optinfo-http_protocol">HTTP protocol</a>
+ </dt>
+
+ <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><a name="optinfo-idna_mode" id=
+ "optinfo-idna_mode">Internationalized domain names</a>
+ </dt>
+
+ <dd>
+ Convert internationalized domain names to and from ASCII.
+ <dl>
+ <dt>IDNA 2003</dt>
+
+ <dd>Convert using the older &ldquo;transitional&rdquo;
+ scheme.</dd>
+
+ <dt>IDNA 2008</dt>
+
+ <dd>Convert using the newer &ldquo;non-transitional&rdquo;
+ scheme.</dd>
+
+ <dt>IDNA TR46</dt>
+
+ <dd>Use IDNA 2008 with the amendments from Unicode <a href=
+ "http://www.unicode.org/reports/tr46">Technical Report
+ 46</a>.</dd>
+
+ <dt>IDNA Compatible</dt>
+
+ <dd>First try converting using IDNA 2008, and if
+ unsuccessful, try IDNA 2003.</dd>
+ </dl>
+ </dd>
+
+ <dt><a name="optinfo-invalid_cookie_prompting" id=
+ "optinfo-invalid_cookie_prompting">Invalid-Cookie Prompting</a>
+ </dt>
+
+ <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><a name="optinfo-keypad_mode" id=
+ "optinfo-keypad_mode">Keypad mode</a>
+ </dt>
+
+ <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>
+ &nbsp;&nbsp;<a href="keystrokes/follow_help.html">Follow link
+ (or page) number:</a> and<br>
+ &nbsp;&nbsp;<a href=
+ "keystrokes/follow_help.html#select-option">Select option (or
+ page) number:</a><br>
+ help for more information.</p>
+ </dd>
+
+ <dt><a name="optinfo-line_edit_style" id=
+ "optinfo-line_edit_style">Line edit style</a>
+ </dt>
+
+ <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><a name="optinfo-local_directory_sort_criteria" id=
+ "optinfo-local_directory_sort_criteria">Local directory sort
+ criteria</a>
+ </dt>
+
+ <dd>
+ <p>This applies to directory editing. Files and directories
+ can be presented in the following ways:</p>
+
+ <dl>
+ <dt>Mixed style</dt>
+
+ <dd>
+ <p>Files and directories are listed together in
+ alphabetical order.</p>
+ </dd>
+
+ <dt>Directories first</dt>
+
+ <dd>
+ <p>Files and directories are separated into two
+ alphabetical lists. Directories are listed first.</p>
+ </dd>
+
+ <dt>Files first</dt>
+
+ <dd>
+ <p>Files and directories are separated into two
+ alphabetical lists. Files are listed first.</p>
+ </dd>
+ </dl>
+ </dd>
+
+ <dt><a name="optinfo-local_directory_sort_order" id=
+ "optinfo-local_directory_sort_order">Local directory sort
+ order</a>
+ </dt>
+
+ <dd>
+ <p>The Options Form also allows you to sort by the file
+ attributes.</p>
+
+ <dl>
+ <dt>By name</dt>
+
+ <dd>
+ <p>by filename (the default)</p>
+ </dd>
+
+ <dt>By size</dt>
+
+ <dd>
+ <p>by file size, in descending order</p>
+ </dd>
+
+ <dt>By date</dt>
+
+ <dd>
+ <p>by file modification time, in descending order</p>
+ </dd>
+
+ <dt>By mode</dt>
+
+ <dd>
+ <p>by file protection</p>
+ </dd>
+
+ <dt>By type</dt>
+
+ <dd>
+ <p>by filename suffix, e.g., the text beginning with
+ &ldquo;.&rdquo;</p>
+ </dd>
+
+ <dt>By user</dt>
+
+ <dd>
+ <p>by file owner's user-id</p>
+ </dd>
+
+ <dt>By group</dt>
+
+ <dd>
+ <p>by file owner's group-id</p>
+ </dd>
+ </dl>
+ </dd>
+
+ <dt><a name="optinfo-multi_bookmarks" id=
+ "optinfo-multi_bookmarks">Multi-bookmarks</a>
+ </dt>
+
+ <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
+ &ldquo;<samp>v</samp>&rdquo;iew bookmarks and
+ &ldquo;<samp>a</samp>&rdquo;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 &ldquo;<samp>=</samp>&rdquo; to
+ invoke the STANDARD selection menu, or <em>RETURN</em> for
+ the default bookmark file.</p>
+ </dd>
+
+ <dt><a name="optinfo-password_for_anon_ftp" id=
+ "optinfo-password_for_anon_ftp">Password for anonymous ftp</a>
+ </dt>
+
+ <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><a name="optinfo-pause_when_showing_message" id=
+ "optinfo-pause_when_showing_message">Pause when showing
+ message</a>
+ </dt>
+
+ <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><a name="optinfo-personal_mail_address" id=
+ "optinfo-personal_mail_address">Personal mail address</a>
+ </dt>
+
+ <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><a name="optinfo-personal_name_for_mail" id=
+ "optinfo-personal_name_for_mail">Personal mail name</a>
+ </dt>
+
+ <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><a name="optinfo-popups_for_select" id=
+ "optinfo-popups_for_select">Popups for select fields</a>
+ </dt>
+
+ <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><a name="optinfo-preferred_doc_language" id=
+ "optinfo-preferred_doc_language">Preferred document
+ language</a>
+ </dt>
+
+ <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,&nbsp;en-gb;q=0.8,&nbsp;en;q=0.7</p>
+ </dd>
+
+ <dt><a name="optinfo-preferred_doc_charset" id=
+ "optinfo-preferred_doc_charset">Preferred document charset</a>
+ </dt>
+
+ <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,&nbsp;utf-8;q=0.8</p>
+ </dd>
+
+ <dt><a name="optinfo-preferred_encoding" id=
+ "optinfo-preferred_encoding">Preferred encoding</a>
+ </dt>
+
+ <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><a name="optinfo-preferred_media_type" id=
+ "optinfo-preferred_media_type">Preferred media type</a>
+ </dt>
+
+ <dd>
+ <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.</p>
+
+ <dl>
+ <dt>Accept lynx's internal types</dt>
+
+ <dd>
+ <p>list only the types that are compiled into lynx.</p>
+ </dd>
+
+ <dt>Also accept lynx.cfg's types</dt>
+
+ <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>
+ <p>lists types from the PERSONAL_EXTENSION_MAP setting in
+ lynx.cfg</p>
+ </dd>
+
+ <dt>Also accept system's types</dt>
+
+ <dd>
+ <p>lists types from the GLOBAL_EXTENSION_MAP setting in
+ lynx.cfg</p>
+ </dd>
+
+ <dt>Accept all types</dt>
+
+ <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><a name="optinfo-raw_8_bit" id="optinfo-raw_8_bit">Raw
+ 8-bit or CJK Mode</a>
+ </dt>
+
+ <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 &ldquo;assumed
+ document character set&rdquo;.</li>
+ </ul>
+
+ <p>The setting also can be toggled via the RAW_TOGGLE
+ command, normally mapped to &ldquo;<samp>@</samp>&rdquo;, and
+ at startup via the <em>-raw</em> switch.</p>
+ </dd>
+
+ <dt><a name="optinfo-send_user_agent" id=
+ "optinfo-send_user_agent">Send User-Agent header</a>
+ </dt>
+
+ <dd>
+ <p>Controls whether the user-agent string will be sent.</p>
+ </dd>
+
+ <dt><a name="optinfo-session_file" id=
+ "optinfo-session_file">Session file</a>
+ </dt>
+
+ <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><a name="optinfo-show_color" id="optinfo-show_color">Show
+ color</a>
+ </dt>
+
+ <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><a name="optinfo-show_cursor" id="optinfo-show_cursor">Show
+ cursor</a>
+ </dt>
+
+ <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><a name="optinfo-show_dot_files" id=
+ "optinfo-show_dot_files">Show dot files</a>
+ </dt>
+
+ <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><a name="optinfo-show_images" id="optinfo-show_images">Show
+ images</a>
+ </dt>
+
+ <dd>
+ <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>
+
+ <li><em>as labels</em> to show the descriptive text for the
+ link</li>
+
+ <li><em>as links</em>, which allows you to use an external
+ viewer</li>
+ </ul>
+ <br>
+ </dd>
+
+ <dt><a name="optinfo-show_scrollbar" id=
+ "optinfo-show_scrollbar">Show scrollbar</a>
+ </dt>
+
+ <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><a name="optinfo-show_transfer_rate" id=
+ "optinfo-show_transfer_rate">Show transfer rate</a>
+ </dt>
+
+ <dd>
+ <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:</p>
+
+ <ul>
+ <li>Do not show rate</li>
+
+ <li>Local directory sort order</li>
+
+ <li>Show dot files</li>
+
+ <li>Execution links</li>
+
+ <li>Pause when showing message</li>
+
+ <li>Show transfer rate</li>
+ </ul>
+ <br>
+ </dd>
+
+ <dt><a name="optinfo-ssl_prompting" id=
+ "optinfo-ssl_prompting">SSL Prompting</a>
+ </dt>
+
+ <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><a name="optinfo-trim_blank_lines" id=
+ "optinfo-trim_blank_lines">Trim blank lines</a>
+ </dt>
+
+ <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><a name="optinfo-type_of_search" id=
+ "optinfo-type_of_search">Type of Search</a>
+ </dt>
+
+ <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><a name="optinfo-use_html5_charset" id=
+ "optinfo-use_html5_charset">Use HTML5 charset replacements</a>
+ </dt>
+
+ <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><a name="optinfo-locale_based_charset" id=
+ "optinfo-locale_based_charset">Use locale-based character
+ set</a>
+ </dt>
+
+ <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><a name="optinfo-underline_links" id=
+ "optinfo-underline_links">Underline links</a>
+ </dt>
+
+ <dd>
+ <p>Use underline-attribute rather than bold for links.</p>
+ </dd>
+
+ <dt><a name="optinfo-use_passive_ftp" id=
+ "optinfo-use_passive_ftp">Use Passive FTP</a>
+ </dt>
+
+ <dd>
+ <p>This allows you to change whether Lynx uses passive ftp
+ connections.</p>
+ </dd>
+
+ <dt><a name="optinfo-user_agent" id=
+ "optinfo-user_agent">User-Agent header</a>
+ </dt>
+
+ <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.9</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><a name="optinfo-user_mode" id="optinfo-user_mode">User
+ Mode</a>
+ </dt>
+
+ <dd>
+ <p>There are four possible choices: Novice, Intermediate,
+ Advanced, and Minimal.</p>
+
+ <dl>
+ <dt>Novice</dt>
+
+ <dd>
+ <p>In Novice mode two lines of help are displayed at the
+ bottom of the screen.</p>
+ </dd>
+
+ <dt>Intermediate</dt>
+
+ <dd>
+ <p>Intermediate mode turns off the help lines.</p>
+ </dd>
+
+ <dt>Advanced</dt>
+
+ <dd>
+ <p>Advanced mode displays the URL of the currently
+ selected link at the bottom of the screen.</p>
+ </dd>
+
+ <dt>Minimal</dt>
+
+ <dd>
+ <p>Minimal mode eliminates the URL on the bottom line,
+ the forward/backward indicator in the upper left, and
+ most status-line messages.</p>
+ </dd>
+ </dl>
+ </dd>
+
+ <dt><a name="optinfo-verbose_images" id=
+ "optinfo-verbose_images">Verbose Images</a>
+ </dt>
+
+ <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><a name="optinfo-vi_keys" id="optinfo-vi_keys">VI keys</a>
+ </dt>
+
+ <dd>
+ <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).</p>
+
+ <p>Note: this has no effect on the line-editor's key
+ bindings.</p>
+ </dd>
+
+ <dt><a name="optinfo-visited_pages" id=
+ "optinfo-visited_pages">Visited Pages</a>
+ </dt>
+
+ <dd>
+ <p>Enable several different views of the visited links:</p>
+
+ <dl>
+ <dt>By First Visit</dt>
+
+ <dt>By First Visit Reversed</dt>
+
+ <dt>As Visit Tree</dt>
+
+ <dt>By Last Visit</dt>
+
+ <dt>By Last Visit Reversed</dt>
+ </dl>
+ <br>
+ </dd>
+
+ <dt><a name="optinfo-x_display" id="optinfo-x_display">X
+ Display</a>
+ </dt>
+
+ <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>
+
+ <h2 id="id-Mail"><a name="Mail" id="Mail">Comments and mailto:
+ links</a></h2>
+
+ <p>At any time while viewing documents within Lynx, you may use
+ the &ldquo;<samp>c</samp>&rdquo; 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>
+&lt;HEAD&gt;
+ &hellip;
+ &lt;LINK REV="made" HREF="mailto:user@somedomain.com"&gt;
+ &hellip;
+&lt;/HEAD&gt;
+</pre>
+ <p>You may also add a TITLE attribute with, for example, the name
+ of your page) If no ownership is specified then comments are
+ disabled. Certain links called <a href=
+ "lynx_url_support.html#mailto_url">mailto:</a> links will also
+ allow you to send mail to other people. Using the mail features
+ within Lynx is straightforward.</p>
+
+ <p>Once you have decided to send a comment or have selected a
+ <em>mailto:</em> link a new screen will appear showing you to
+ whom you are sending the message. Lynx will ask for your name,
+ your e-mail address, and the subject of the message. If you have
+ filled in the "personal mail address" field in the <em>Options
+ Menu</em>, your e-mail address will be filled in automatically.
+ After entering the above information, if you have an editor
+ defined in the <em>Options Menu</em> and you are not an anonymous
+ user then your specified editor will be spawned for you so that
+ you can enter your message. If you do not have an editor defined
+ or you are an anonymous user, a simple line mode input scheme
+ will allow you to enter your message.</p>
+
+ <p>To finish sending the message, exit your spawned editor or, if
+ you are using the simple line mode input scheme, type a
+ &ldquo;<samp>.</samp>&rdquo; (period) on a line by itself. You
+ will be asked a final time whether to send the message. If you
+ press &ldquo;<samp>y</samp>&rdquo;, 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 &ldquo;<samp>n</samp>&rdquo;
+ 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>
+
+ <h2 id="id-News"><a name="News" id="News">USENET News posting</a></h2>
+
+ <p>While reading <a href=
+ "http://www.w3.org/LineMode/User/AboutNewsServers.html">news</a>
+ articles with Lynx you should see a link that says <em>Reply to:
+ user@host</em> and, if the nntp server from which you received
+ the article supports posting from your site, a link that says
+ <em>Followup to: newsgroup(s)</em></p>
+
+ <dl>
+ <dt>Reply to user@host</dt>
+
+ <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>
+ <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=
+ "http://www.w3.org/Protocols/rfc977/rfc977">RFC 977</a>.</p>
+
+ <h2 id="id-Bookmarks"><a name="Bookmarks" id="Bookmarks">Lynx
+ bookmarks</a></h2>
+
+ <p>Bookmarks are entries in your <em>bookmark file</em>, which
+ record the URL of a document you may want to return to easily,
+ with a name of your choice to identify the document. To use
+ bookmarks you must first have specified a name for your bookmark
+ file in <a href="#lynx.cfg">lynx.cfg</a> or via the <em>Options
+ Menu</em>.</p>
+
+ <p>To save a bookmark to the document you wish to place in the
+ bookmark file press the &ldquo;<samp>a</samp>&rdquo; 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 &ldquo;<samp>d</samp>&rdquo; to save a link to the
+ document you are currently viewing or
+ &ldquo;<samp>l</samp>&rdquo; to save the link that is currently
+ selected on the page. Selecting &ldquo;<samp>c</samp>&rdquo; will
+ cancel without saving anything to your bookmark file.</p>
+
+ <p>A bookmark file will be created in conjunction with acting on
+ the &ldquo;<samp>a</samp>&rdquo;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 &ldquo;<samp>a</samp>&rdquo;dd command before you can
+ view it.</p>
+
+ <p>Use the &ldquo;<samp>v</samp>&rdquo; 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
+ &ldquo;<samp>r</samp>&rdquo; key when positioned on that link.
+ You also can use a standard text editor (e.g., via the
+ &ldquo;<samp>e</samp>&rdquo;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
+ <em>A</em>nchor element for the link, but you should not change
+ the format within the line for the link, consisting of an
+ <em>LI</em> element followed by the <em>A</em>nchor element, nor
+ cause the line to become wrapped to a second line. You similarly
+ can change the link destination by editing the double-quoted
+ value for the <em>HREF</em> attribute in the <em>A</em>nchor
+ start tag, but you should not otherwise change the spacing within
+ the start tag, nor add other attributes. You can add a new link
+ while editing by copying an existing line for a link, to ensure
+ the proper format, and then modifying its <em>HREF</em> value and
+ <em>A</em>nchor content, but you should not add any other HTML
+ 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
+ &ldquo;<samp>a</samp>&rdquo;dd and
+ &ldquo;<samp>r</samp>&rdquo;emove commands may not work
+ properly.</p>
+
+ <p>When multi-bookmarks (see <a href=
+ "#InteractiveOptions">Options Menu</a>) is OFF, you will always
+ view or add links to the default bookmark file. When it is
+ 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 &ldquo;<samp>=</samp>&rdquo; to invoke the STANDARD
+ selection menu, or <em>RETURN</em> for the default bookmark file.
+ [<a href="#ToC-Bookmarks">ToC</a>]</p>
+
+ <h2 id="id-Jumps"><a name="Jumps" id="Jumps">Jump Command</a></h2>
+
+ <p>Similar to the bookmarks file is the jumps file: for an
+ example, look in the <em>samples</em> subdirectory in the
+ 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 &amp; short-cut names. Once you have
+ done that, typing &ldquo;<samp>j</samp>&rdquo; 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
+ &ldquo;<samp>g</samp>&rdquo;. If you want to check which
+ short-cuts are available, type &ldquo;<samp>?</samp>&rdquo; 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"
+ marker in the URL at each point where you want Lynx to fill in
+ text. When you activate the corresponding jump, Lynx will prompt
+ 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 &ldquo;<samp>g</samp>&rdquo; and
+ &ldquo;<samp>/</samp>&gt;&rdquo; (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
+ administrators who have unsophisticated users to care for, but
+ ordinary Lynx users who have a number of URLs they regularly
+ visit while browsing may find using the jumps command speeds
+ their movements.</p>
+
+ <p>For more advice how to set up the jumps command on your system
+ and how to define short-cut names, read <a href=
+ "#lynx.cfg">lynx.cfg</a> .</p>
+
+ <p>[<a href="#ToC-Jumps">ToC</a>]</p>
+
+ <h2 id="id-DirEd"><a name="DirEd" id="DirEd">Directory
+ Editing</a></h2>
+
+ <p>Lynx offers extended DIRED support on Unix (on VMS the more
+ powerful CSwing program is recommended for character cell
+ terminals, and can be offered via Lynx as a jump shortcut or
+ execution link). When a local directory is accessed using a URL
+ of the form <em>file://localhost/path/</em>, a new set of
+ commands is available. With DIRED support you can create, edit,
+ delete, copy, and move files on your local system. The commands
+ available in DIRED mode are</p>
+
+ <dl>
+ <dt><code>C)reate</code>
+ </dt>
+
+ <dd>
+ <p>Type &ldquo;<samp>c</samp>&rdquo; to create a new file.
+ New file will be empty.</p>
+ </dd>
+
+ <dt><code>D)ownload</code>
+ </dt>
+
+ <dd>
+ <p>Type &ldquo;<samp>d</samp>&rdquo; to download using one of
+ the pre-defined options.</p>
+ </dd>
+
+ <dt><code>E)dit</code>
+ </dt>
+
+ <dd>
+ <p>Type &ldquo;<samp>e</samp>&rdquo; 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>
+ <p>Type &ldquo;<samp>f</samp>&rdquo; 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>
+ <p>Type &ldquo;<samp>m</samp>&rdquo; to modify the name or
+ location of file. Then type &ldquo;<samp>n</samp>&rdquo; to
+ rename the file or &ldquo;<samp>l</samp>&rdquo; to move the
+ file to a different location.</p>
+ </dd>
+
+ <dt><code>R)emove</code>
+ </dt>
+
+ <dd>
+ <p>Type &ldquo;<samp>r</samp>&rdquo; to remove the selected
+ file or directory.</p>
+ </dd>
+
+ <dt><code>T)ag</code>
+ </dt>
+
+ <dd>
+ <p>Type &ldquo;<samp>t</samp>&rdquo; 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>
+ <p>Type &ldquo;<samp>u</samp>&rdquo; 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>
+
+ <h2 id="id-ColorMouse"><a name="ColorMouse" id="ColorMouse">Using
+ Color &amp; the Mouse</a></h2>
+
+ <p>A limited range of colors &amp; mouse commands are available,
+ if the user chooses: see <em>lynx.cfg</em> for details. [<a href=
+ "#ToC-ColorMouse">ToC</a>]</p>
+
+ <h2 id="id-MiscKeys"><a name="MiscKeys" id="MiscKeys">Scrolling
+ and Other useful commands</a></h2>
+
+ <p>A summary of all the keystroke commands and their key bindings
+ can be invoked via the KEYMAP command, normally mapped to
+ &ldquo;<samp>k</samp>&rdquo; and &ldquo;<samp>K</samp>&rdquo;.
+ The following describes some of the most commonly used
+ commands.</p>
+
+ <dl>
+ <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 &ldquo;<code>*****</code>&rdquo;.
+ 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 &ldquo;<samp>E</samp>&rdquo; command allows you to
+ edit the URL (or ACTION) of the current link and then use
+ that as a goto URL. Pressing the &ldquo;<samp>E</samp>&rdquo;
+ 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 &ldquo;E&rdquo;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 &ldquo;<samp>g</samp>&rdquo; command.
+ Note that lower case &ldquo;e&rdquo; invokes the external
+ editor for the current document.</p>
+ </dd>
+
+ <dt><strong><samp>g</samp></strong>
+ </dt>
+
+ <dd>
+ <p>The &ldquo;<samp>g</samp>&rdquo; command allows any URL to
+ be viewed. Pressing the &ldquo;<samp>g</samp>&rdquo; 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 &ldquo;<samp>G</samp>&rdquo; command allows you to
+ edit the URL of the current document and then use that as a
+ goto URL. Pressing the &ldquo;<samp>G</samp>&rdquo; 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
+ &ldquo;<samp>g</samp>&rdquo; command.</p>
+ </dd>
+
+ <dt><strong><samp>z</samp></strong>
+ </dt>
+
+ <dd>
+ <p>Lynx supports completely interruptible I/O processes.
+ Press the &ldquo;<samp>z</samp>&rdquo; 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 &ldquo;<samp>#</samp>&rdquo; 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 &ldquo;<samp>!</samp>&rdquo; 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, &ldquo;<samp>$</samp>&rdquo;
+ normally is a synonym.</p>
+ </dd>
+
+ <dt><strong><samp>=</samp></strong>
+ </dt>
+
+ <dd>
+ <p>The &ldquo;<samp>=</samp>&rdquo; 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
+ &ldquo;<samp>|</samp>&rdquo;</li>
+
+ <li>when line-wrapping is off, use the
+ &ldquo;<samp>=</samp>&rdquo; 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"><strong><samp>*</samp></strong></a>
+ </dt>
+
+ <dd>
+ <p>The &ldquo;<samp>*</samp>&rdquo; 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><strong><samp>@</samp></strong>
+ </dt>
+
+ <dd>
+ <p>The &ldquo;<samp>@</samp>&rdquo; 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"><strong><samp>[</samp></strong></a>
+ </dt>
+
+ <dd>
+ <p>The &ldquo;<samp>[</samp>&rdquo; 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><strong><samp>]</samp></strong>
+ </dt>
+
+ <dd>
+ <p>The &ldquo;<samp>]</samp>&rdquo; 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><strong><samp>{</samp></strong>
+ </dt>
+
+ <dd>
+ <p>If the line-wrapping margin is wider than the terminal's
+ display, scroll left 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><strong><samp>|</samp></strong>
+ </dt>
+
+ <dd>
+ <p>&ldquo;<samp>|</samp>&rdquo; 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 &ldquo;pad&rdquo; 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>
+
+ <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>
+ <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>
+
+ <h2 id="id-Forms"><a name="Forms" id="Forms">Lynx and HTML
+ Forms</a></h2>
+
+ <p>This section describes the Lynx Forms Interface. HTML gives
+ document providers the ability to create on-line forms which may
+ be filled out when the document is viewed. When a form is
+ submitted the information on the form can be used to search a
+ database or complete a survey.</p>
+
+ <p>An HTML Form provides for the use of buttons to perform an
+ action (such as <em>submit</em>), checkboxes, radio buttons or
+ popups to select options from a list, and fields for entering
+ text.</p>
+
+ <dl>
+ <dt>Buttons:</dt>
+
+ <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
+ (&ldquo;<samp>x</samp>&rdquo;) or DOWNLOAD
+ (&ldquo;<samp>d</samp>&rdquo;) keystroke commands to "push"
+ the button (see below).</p>
+ </dd>
+
+ <dt>Checkboxes and Radio buttons</dt>
+
+ <dd>
+ <p>Checkboxes are displayed as square brackets:
+ <em>[&nbsp;]</em> and radio buttons are displayed as
+ parenthesis: <em>(&nbsp;)</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>
+ <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
+ &ldquo;<samp>/</samp>&rdquo; and
+ &ldquo;<samp>n</samp>&rdquo;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>
+ <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
+ to correct errors. If you try to input more text than the
+ field can hold, the line editor will not accept the
+ additional characters. If you fill a text field the cursor
+ will not move off the field but remain at the last field
+ position. Use the <em>up-arrow</em>, and <em>down-arrow</em>,
+ <em>TAB</em> or <em>Return</em> keys to move up, or down from
+ the text entry field. NOTE, however, that <em>Return</em>
+ also will <a href="#submit">submit</a> the form if the text
+ entry field is the only non-hidden field in the form. If
+ <a name="tna" id="tna">"Textfields Need Activation"</a> mode
+ is turned on (with the <kbd>-tna</kbd> command-line option or
+ in <a href="#lynx.cfg">lynx.cfg</a>), then text entry fields
+ do not become active immediately upon being selected, as
+ normally. Keystrokes have their normal command meaning unless
+ 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.</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
+ the Lynx keystroke commands, because they are interpreted by
+ the <a href="keystrokes/edit_help.html">Line Editor</a> as
+ either text entries or editing commands. Select a button or
+ box when you want to use Lynx keystrokes; or prefix your
+ keystroke with <em>^V</em> to temporarily escape from line
+ editing.</p>
+
+ <p>Some flavors of UNIX, shells &amp; terminal settings
+ require that you enter <em>^V^Ve</em> in order to start the
+ external editor, as they also use <em>^V</em> as default
+ command-line quote key (called &ldquo;lnext&rdquo; in stty
+ man pages and &ldquo;stty -a&rdquo; output); to avoid this,
+ you can put &ldquo;stty lnext undef&rdquo; in your .cshrc
+ file (or .profile or .bashrc, depending on what shell you
+ use), or invoke Lynx with a wrapper script, e.g.</p>
+
+ <p><code>&nbsp;&nbsp;#!/bin/sh<br>
+ &nbsp;&nbsp;stty lnext undef<br>
+ &nbsp;&nbsp;$HOME/bin/lynx "$@"<br>
+ &nbsp;&nbsp;stty lnext ^V<br>
+ &nbsp;&nbsp;exit</code>
+ </p>
+
+ <p>NB when NOT in the Line Editor, <em>^V</em> is by default
+ bound to the command to switch between SortaSGML and TagSoup
+ HTML parsing (i.e., SWITCH_DTD). To avoid confusion, either
+ of these separate functions could be changed (mapped away)
+ with a KEYMAP directive in <em>lynx.cfg</em>. For
+ example,</p>
+
+ <p>&nbsp;&nbsp;KEYMAP:^V:DO_NOTHING<br>
+ &nbsp;&nbsp;KEYMAP:#:SWITCH_DTD</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>&nbsp;&nbsp;KEYMAP:^V::NOP:1<br>
+ &nbsp;&nbsp;KEYMAP:^_::LKCMD:1</p>
+
+ <p>would move <em>^V</em>'s Line Editor binding as command
+ escape to <em>^_</em> for the first Line Edit style, letting
+ <em>^V</em> still act as SWITCH_DTD outside of text input
+ fields.</p>
+ </dd>
+
+ <dt>TEXTAREA Fields</dt>
+
+ <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>
+ <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>
+ <p>An external editor has to be defined, for example in the
+ <a href="#InteractiveOptions">Options Menu</a>, before you
+ can start using this function.</p>
+
+ <p>A key to invoke external TEXTAREA editing is normally
+ provided by the <a href=
+ "keystrokes/edit_help.html">Line-Editor Key</a> Bindings. A
+ KEYMAP directive in <em>lynx.cfg</em> can also be used to
+ make a different key invoke external editing; it will then
+ normally be necessary to prefix that key with <em>^V</em> to
+ "escape" from line-editing. Two variants exist,<br>
+ &nbsp;&nbsp;KEYMAP:e:EDITTEXTAREA<br>
+ or<br>
+ &nbsp;&nbsp;KEYMAP:e:DWIMEDIT<br>
+ (the first is only functional for TEXTAREA editing, while the
+ second allows to use the same key for normal <a href=
+ "#FileEdit">file editing</a> <em>as long as both functions do
+ not conflict</em>).</p>
+
+ <p>Please see the <a href="#CtrlVNote">note above</a> for
+ details about <em>^V</em> behavior.</p>
+ You can also use two other special TEXTAREA functions. Again,
+ these are already bound to key sequences in the <a href=
+ "keystrokes/edit_help.html#TASpecial">Line-Editor
+ Bindings</a>, by default <em>^Xg</em> and <em>^Xi</em>. You
+ can use different keys by adding KEYMAP bindings to your
+ <em>lynx.cfg</em> file, e.g.
+ <p>&nbsp;&nbsp;KEYMAP:$:GROWTEXTAREA<br>
+ &nbsp;&nbsp;KEYMAP:#:INSERTFILE</p>
+
+ <p>With these bindings, (in a TEXTAREA only) <em>^V$</em>
+ would add 5 lines to the TEXTAREA and <em>^V#</em> would
+ prompt for the name of an existing file to be inserted into
+ the TEXTAREA (above the cursorline). An automatic variation
+ of GROWTEXTAREA is normally compiled in, so that hitting
+ <em>Enter</em> with the cursor on the last line adds a new
+ line to the TEXTAREA, with the cursor on it.</p>
+
+ <p>If you have some single keys (or control keys) to spare
+ that you do not need for their normal purposes, you can
+ dedicate those keys to invoke the special functions (without
+ requiring a prefix key). For example, to use the <em>^E</em>
+ key for the DWIMEDIT action, and the <em>Insert</em> key for
+ the INSERTFILE action, use<br>
+ &nbsp;&nbsp;KEYMAP:^E:DWIMEDIT:PASS<br>
+ &nbsp;&nbsp;KEYMAP:0x10C:INSERTFILE:PASS<br>
+ (see lynx.cfg for other keystroke codes to use).</p>
+
+ <p>Note that the default bindings that use <em>^X</em> as a
+ prefix key <em>may</em> also work by substituting the
+ <kbd>Escape</kbd> key for ^X. If your keyboard has a modifier
+ (Meta) key that gets transmitted as an ESC prefix, for
+ example <kbd>Alt</kbd>, you can then even use <em>Alt-e</em>
+ instead of <em>^Xe</em>, <em>Alt-g</em> instead of
+ <em>^Xg</em>, and so on. But this does not work reliably
+ everywhere (it depends on the way Lynx is compiled, including
+ which libraries are used, and behavior of the connection and
+ terminal type).</p>
+ </dd>
+ </dl>
+
+ <p>In general, you can move around the form using the standard
+ Lynx navigation keys. The <em>up-arrow</em> and
+ <em>down-arrow</em> keys, respectively, select the previous or
+ next field, box, or button. The <em>TAB</em> key selects the next
+ field, box, or button.</p>
+
+ <p>To <a name="submit" id="submit"><em>submit</em></a> the form
+ press <em>right-arrow</em> or <em>Return</em> when positioned on
+ the form's submit button. If you've submitted the form previously
+ during the Lynx session, have not changed any of the form
+ 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
+ (&ldquo;<samp>x</samp>&rdquo;) 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>&lt;META HTTP-EQUIV="Pragma" CONTENT="no-cache"&gt;</em>
+ <em>&lt;META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"&gt;</em>
+</pre>
+ <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 (&ldquo;<samp>d</samp>&rdquo;)
+ 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>
+
+ <p>Forms which have <em>POST</em> as the METHOD, or a <a href=
+ "lynx_url_support.html#mailto_url">mailto:</a> URL as the ACTION,
+ are always resubmitted, even if the content has not changed, when
+ you activate the <em>submit</em> button. Lynx normally will not
+ resubmit a form which has <em>POST</em> as the METHOD if the
+ document returned by the form has links which you activated, and
+ then you go back via the PREV_DOC (<em>left-arrow</em>) command
+ or via the <a href="keystrokes/history_help.html">History
+ Page</a>. Lynx can be compiled so that it resubmits the form in
+ those cases as well, and the default can be changed via <a href=
+ "#lynx.cfg">lynx.cfg</a>, and toggled via the
+ <em>-resubmit_posts</em> command line switch.</p>
+
+ <p>If the form has one <em>text entry</em> field and no other
+ fields except, possibly, hidden INPUT fields not included in the
+ display, then that field also serves as a <em>submit</em> button,
+ and pressing <em>right-arrow</em> or <em>Return</em> on that
+ field will invoke submission of the form. Be sure to use
+ <em>up-arrow</em>, <em>down-arrow</em> or <em>TAB</em> to move
+ off the text entry field, in such cases, if it is not your
+ intention to submit the form (or to retrieve what was returned
+ from an earlier submission if the content was not changed and the
+ METHOD was <em>GET</em>).</p>
+
+ <p>Forms can have multiple <em>submit</em> buttons, if they have
+ been assigned NAMEs in the markup. In such cases, information
+ 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
+ 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
+ image when it was <em>clicked</em> are included in the form
+ 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.</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 &ldquo;-&rdquo; 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
+ could be made aware whether the submission was by a user with a
+ graphic client and had image loading turned on, or by a user who
+ did not see the image nor make a conscious choice within it.
+ However, requests that this be included in HTML specifications
+ consistently have fallen on deaf ears, and thus Lynx now "fakes"
+ a 0,0 coordinate pair whether or not a VALUE or ALT attribute is
+ present in the INPUT tag. Ideally, the script which analyzes the
+ submitted content will treat the 0,0 coordinate pair as an
+ indicator that the user did not see the image and make a
+ conscious choice within it.</p>
+
+ <p>Forms can have <em>hidden</em> INPUT fields, which are not
+ displayed, but have NAMEs and VALUEs included in the content.
+ These often are used to keep track of information across a series
+ of related form submissions, but have the potential for including
+ information about the user that might be considered to represent
+ an invasion of privacy. NOTE, in this regard, that Lynx has
+ implemented the <a href="http://www.w3.org/Markup/html3/">HTML
+ 3.0</a> <em>DISABLED</em> attribute for <em>all</em> of its form
+ fields. These can be used to keep track of information across
+ submissions, and to cast it unmodifiable in the current form, but
+ keep the user aware that it will be included in the
+ submission.</p>
+
+ <p>Forms most commonly are submitted to http servers with the
+ content encoded as
+ <em>ENCTYPE="application/x-www-form-urlencoded"</em> for analysis
+ by a script, and Lynx treats that as the default if no ENCTYPE is
+ specified in the FORM start tag. However, you can specify a
+ <a href="lynx_url_support.html#mailto_url">mailto</a> URL as the
+ form's ACTION to have the form content sent, instead, to an email
+ address. In such cases, you may wish to specify
+ <em>ENCTYPE="text/plain"</em> in the form markup, so that the
+ content will not be encoded, but remain readable as plain
+ text.</p>
+
+ <p>Lynx also supports
+ <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
+ (&ldquo;<samp>;</samp>&rdquo;) instead of ampersands
+ (&ldquo;<samp>&amp;</samp>&rdquo;) 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
+ files without conversion of the ampersands to SGML character
+ references (<em>&amp;amp;</em> or <em>&amp;#38;</em>), their
+ being followed by form field NAMEs which might correspond to SGML
+ entities could lead to corruption of the intended URL.</p>
+
+ <p>NOTE, in this regard, that Lynx converts ampersands to
+ <em>&amp;amp;</em> when creating bookmarks, and thus the bookmark
+ links will not be vulnerable to such corruptions. Also NOTE that
+ Lynx allows you to save links in your bookmark file for documents
+ returned by forms with the <em>GET</em> METHOD, and which thus
+ have the content appended as a <em>?searchpart</em>, but not if
+ the METHOD was <em>POST</em>, because the content would be lost
+ and the link thus would be invalid.</p>
+
+ <p>Lynx supports <em>ENCTYPE="multipart/form-data"</em> for
+ sending form content with name=value pairs encoded as multipart
+ sections with individual MIME headers and boundaries. However,
+ Lynx does not yet support INPUTs with <em>TYPE="file"</em> or
+ <em>TYPE="range"</em> and will set the <em>DISABLED</em>
+ attribute for all of the form's fields if any INPUTs with either
+ of those two TYPEs are present, so that the form cannot be
+ submitted. Otherwise, Lynx will submit the form with the
+ multipart ENCTYPE.</p>
+
+ <p>A
+ <em>Content-Disposition:&nbsp;file;&nbsp;filename=name.suffix</em>
+ header can be used by CGI scripts to set the suggested filename
+ offered by Lynx for &ldquo;<samp>d</samp>&rdquo;ownload and
+ &ldquo;<samp>p</samp>&rdquo;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
+ PATH_INFO field, and thus might be misleading. This also can be
+ done via a META element in any document:</p>
+
+ <pre>
+ <em>&lt;META HTTP-EQUIV="Content-Disposition"
+ CONTENT="file; filename=name.suffix"&gt;</em>
+</pre>
+ <p>[<a href="#ToC-Forms">ToC</a>]</p>
+
+ <h2 id="id-Images"><a name="Images" id="Images">Lynx and HTML
+ Images</a></h2>
+
+ <p>As a text browser, Lynx does not display images as such -- you
+ need to define a viewer in <em>lynx.cfg</em>: see there -- , but
+ users can choose a number of ways of showing their presence.</p>
+
+ <p>There are 3 choices in <em>lynx.cfg</em>, with 2 corresponding
+ keys:</p>
+
+ <pre>
+ MAKE_LINKS_FOR_ALL_IMAGES * IMAGE_TOGGLE
+ MAKE_PSEUDO_ALTS_FOR_INLINES [ INLINE_TOGGLE
+ VERBOSE_IMAGES no corresponding key
+</pre>
+ <p>You can also use the <em>Options Menu</em>, as outlined
+ below:</p>
+
+ <pre>
+ key lynx.cfg FM KM .lynxrc variable in source
+
+ * MAKE_LINKS_ Y N N clickable_images
+ [ MAKE_PSEUDO_ Y N N pseudo_inline_alts
+ VERBOSE_ Y Y Y verbose_img
+
+FM = Form-based Menu ; KM = Key-based Menu ;
+in .lynxrc , VERBOSE_IMAGES is called &ldquo;verbose_images&rdquo;:
+the other two cannot be saved between sessions.
+</pre>
+ <p>In the Form-based Menu, the 3-way &ldquo;Show images&rdquo;
+ selection combines the effects of the &ldquo;*&rdquo; &amp;
+ &ldquo;[&rdquo; keys, as follows:</p>
+
+ <pre>
+ Ignore clickable_images = FALSE, pseudo_inline_alts = FALSE
+ As labels clickable_images = FALSE, pseudo_inline_alts = TRUE
+ As links clickable_images = TRUE, pseudo_inline_alts = unchanged
+</pre>
+ <h2 id="id-Tables"><a name="Tables" id="Tables">Lynx and HTML
+ Tables</a></h2>
+
+ <p>HTML includes markup for creating <em>tables</em> structured
+ as arrays of cells aligned by columns and rows on the displayed
+ page.</p>
+
+ <p>Lynx recognizes the TABLE element and all of its associated
+ elements as described in <a href=
+ "http://www.faqs.org/rfcs/rfc1942.html">RFC 1942</a> and will
+ process any ID attributes in the start tags for handling as
+ NAME-ed anchors, but does not create actual <em>tables</em>.
+ Instead, it treats the TR start tag as a collapsible BR (line
+ break), and inserts a collapsible space before the content of
+ each TH and TD start tag. This generally makes all of the content
+ of the <em>table</em> readable, preserves most of the intra-cell
+ organization, and makes all of the links in the <em>table</em>
+ accessible, but any information critically dependent on the
+ column and row alignments intended for the <em>table</em> will be
+ missed.</p>
+
+ <p>If inherently tabular data must be presented with Lynx, one
+ can use PRE formatted content, or, if the <em>table</em> includes
+ markup not allowed for PRE content, construct the <em>table</em>
+ using <a href="#Tabs">HTML Tabs</a>. An example <em>table</em>
+ using <em>TAB</em> elements is included in the test subdirectory
+ of the Lynx distribution.</p>
+
+ <div id="TRST">
+ <p>Starting with version 2.8.3, Lynx renders some tables in
+ tabular form. This tabular representation for <em>simple</em>
+ tables (<dfn>TRST</dfn>) does not attempt to implement full
+ support for any table model. Limitations are:</p>
+
+ <ul>
+ <li>All data constituting a table row generally has to fit
+ within the display width without inserting line breaks.</li>
+
+ <li>Cell contents have to be simple. In general, only inline
+ markup is acceptable, no <code>&lt;P&gt;</code>,
+ <code>&lt;BR&gt;</code> etc. (although
+ <code>&lt;BR&gt;</code> may be ignored at the beginning of
+ the first cell or at the end of the last cell of a row).</li>
+
+ <li>When tables are nested, only the innermost level is a
+ candidate for tabular representation.</li>
+
+ <li>Most attributes are ignored, including borders,
+ <code>WIDTH</code>, vertical alignment.</li>
+ </ul>
+
+ <p>Horizontal alignments (<code>LEFT</code>,
+ <code>CENTER</code>, <code>RIGHT</code>), <code>COLSPAN</code>,
+ and <code>ROWSPAN</code> are interpreted according to HTML
+ 4.01. (<code>ROWSPAN</code> can only reserve empty space in
+ subsequent rows, because of the limitations above.) When TRST
+ fails because a table is not "simple" enough, the
+ representation falls back to the minimal handling described
+ earlier. Many (but, unfortunately, by no means all) tables that
+ represent inherently tabular material will thus be shown with
+ correct tabular formatting. Where table markup is used only for
+ layout purposes (containing whole blocks of text and list
+ within table cells) and not essential for understanding the
+ textual contents, it remains basically ignored. Some more
+ information on details is available in the file
+ <kbd>README.TRST</kbd> of the source distribution.</p>
+ </div>
+
+ <p>For tabular display of more complex tables, Lynx users can
+ make use of external scripts or programs. The normal Lynx
+ distribution currently does not provide such scripts, but they
+ can be written locally or downloaded from several sources. It is
+ suggested to use one of Lynx's facilities for invoking external
+ programs (see <kbd>DOWNLOADER</kbd>, <kbd>PRINTER</kbd>,
+ <kbd>EXTERNAL</kbd>, <kbd>TRUSTED_LYNXCGI</kbd> in <a href=
+ "#lynx.cfg">lynx.cfg</a> and <a href=
+ "lynx_url_support.html#cgi_url"><code>lynxcgi:</code></a> in
+ <em>Supported URLs</em> for information on various ways for
+ setting this up).</p>
+
+ <p>[<a href="#ToC-Tables">ToC</a>]</p>
+
+ <h2 id="id-Tabs"><a name="Tabs" id="Tabs">Lynx and HTML Tabs</a></h2>
+
+ <p>Lynx implements the <a href=
+ "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> TAB
+ element only when LEFT alignment is in effect. If the alignment
+ is CENTER or RIGHT (JUSTIFY is not yet implemented in Lynx, and
+ is treated as a synonym for LEFT), or if the TAB element
+ indicates a position to the left of the current position on the
+ screen, it is treated as a collapsible space. For purposes of
+ implementing TAB, Lynx treats <em>en</em> units as half a
+ character cell width when specified by the INDENT attribute, and
+ rounds up for odd values (e.g., a value of either 5 or 6 will be
+ treated as three spaces, each the width of a character cell). See
+ the example <em>table</em> using TAB elements in the test
+ subdirectory of the Lynx distribution as a model for using this
+ functionality.</p>
+
+ <p>Note that this <em>Users Guide</em> and the <a href=
+ "lynx_url_support.html">Supported URLs</a> page include TAB
+ markup in a manner which <em>degrades gracefully</em> for WWW
+ browsers which do not support it. Toggle to display of <a href=
+ "#LocalSource">source</a> and <a href="#Search">search</a> for
+ <em>&lt;tab</em> to examine the use of TAB markup in these
+ documents.</p>
+
+ <p>[<a href="#ToC-Tabs">ToC</a>]</p>
+
+ <h2 id="id-Frames"><a name="Frames" id="Frames">Lynx and HTML
+ Frames</a></h2>
+
+ <p>Some implementations of HTML include markup, primarily
+ designed for graphic clients, that is intended to create an array
+ of simultaneously displayed, independently scrolling windows.
+ Such windows have been termed <em>frames</em>.</p>
+
+ <p>Lynx recognizes the Netscape and Microsoft Explorer FRAME,
+ FRAMESET, and NOFRAMES elements, but is not capable of windowing
+ to create the intended positioning of <em>frames</em>. Instead,
+ Lynx creates labeled links to the <em>frame</em> sources,
+ typically positioned in the upper left corner of the display, and
+ renders the NOFRAMES section. If the document provider has
+ disregard for text clients and sight-challenged Webizens, and
+ thus does not include substantive content in the NOFRAMES section
+ or a link in it to a document suitable for text clients, you can
+ usually guess from the labeling of the <em>frame</em> links which
+ one has the substantive material (if there is any), or you can
+ try each of those links to see if anything worthwhile is
+ returned.</p>
+
+ <p>[<a href="#ToC-Frames">ToC</a>]</p>
+
+ <p>Some sites -- in ignorance of Lynx capabilities -- may tell
+ you (for example) "to view this page you need Netscape
+ Navigator". You can simply ignore such warnings and access the
+ frames via the Lynx-generated links as above.</p>
+
+ <h2 id="id-Banners"><a name="Banners" id="Banners">Lynx and HTML
+ Banners</a></h2>
+
+ <p>Some implementations of HTML markup include provisions for
+ creating a non-scrolling window to be positioned at the top of
+ each page, containing links with brief, descriptive link names,
+ analogous to a Windows toolbar. Such windows have been termed
+ <em>banners</em>.</p>
+
+ <p>Lynx recognizes and processes all of the <a href=
+ "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> REL
+ attribute tokens in LINK elements for creating a <em>banner</em>,
+ and a number of others which have subsequently been proposed.
+ These <em>banner</em> tokens are <em>Home</em>, <em>ToC</em>,
+ <em>Contents</em>, <em>Index</em>, <em>Glossary</em>,
+ <em>Copyright</em>, <em>Up</em>, <em>Next</em>,
+ <em>Previous</em>, <em>Prev</em>, <em>Help</em>, <em>Search</em>,
+ <em>Top</em>, <em>Origin</em>, <em>Navigator</em>,
+ <em>Child</em>, <em>Disclaimer</em>, <em>Sibling</em>,
+ <em>Parent</em>, <em>Author</em>, <em>Editor</em>,
+ <em>Publisher</em>, <em>Trademark</em>, <em>Meta</em>,
+ <em>URC</em>, <em>Hotlist</em>, <em>Begin</em>, <em>First</em>,
+ <em>End</em>, <em>Last</em>, <em>Pointer</em>,
+ <em>Translation</em>, <em>Definition</em>, <em>Chapter</em>,
+ <em>Section</em>, <em>Subsection</em>, <em>Alternate</em>,
+ <em>Documentation</em>, <em>Biblioentry</em>,
+ <em>Bibliography</em>, <em>Start</em>, <em>Appendix</em>,
+ <em>Bookmark</em> and <em>Banner</em>. Any LINK elements with
+ those tokens as the REL attribute value, and an HREF attribute
+ value in the LINK, will invoke creation of a <em>banner</em> at
+ the top of the first page, with the element's HREF as the link,
+ and the token as the default link name. If a TITLE attribute is
+ included in the LINK, its value will be used as the link name
+ instead of the default. <em>Bookmark</em> and <em>Banner</em> are
+ intended to be accompanied by a TITLE attribute, which in effect
+ makes the namespace for REL <em>banner</em> tokens infinite.</p>
+
+ <p>If the special token <em>Help</em> is used as the REL value
+ and no HREF is included in the LINK, Lynx will use it own
+ <em>HELPFILE</em> URL for that link. For the special token
+ <em>Home</em> without an HREF, Lynx will use the default
+ <em>STARTFILE</em> (i.e., derived from the configuration files or
+ the WWW_HOME environment variable, <em>not</em> the command line
+ <em>startfile</em> if one was used). However, if a
+ <em>-homepage=URL</em> was specified on the command line, its URL
+ will be used as the HREF. For the special token <em>Index</em>
+ without an HREF, Lynx will use the <em>DEFAULT_INDEX_FILE</em>
+ derived from the configuration files, or if an
+ <em>-index=URL</em> was specified on the command line, its URL
+ will be used as the HREF.</p>
+
+ <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 (&ldquo;<samp>#</samp>&rdquo;) 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
+ &ldquo;<samp>#</samp>&rdquo; 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 &ldquo;<samp>#</samp>&rdquo; 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>
+ BANNER container element, and will create a <em>banner</em> based
+ on its content if one has not already been created based on LINK
+ elements. Lynx treats the Microsoft MARQUEE element as a synonym
+ 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 &ldquo;<samp>#</samp>&rdquo; because the content need not be
+ only a series of links with brief, descriptive links names, but
+ does add a &ldquo;<samp>#</samp>&rdquo; 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>
+
+ <h2 id="id-Footnotes"><a name="Footnotes" id="Footnotes">Lynx and
+ HTML Footnotes</a></h2>
+
+ <p>Lynx implements the <a href=
+ "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> FN
+ element similarly to a named <em>A</em>nchor within the current
+ document, and assumes that the footnotes will be positioned at
+ the bottom of the document. However, in contrast to named
+ <em>A</em>nchors, the FN container element is treated as a block
+ (i.e., as if a new paragraph were indicated whether or not that
+ is indicated in its content) with greater than normal left and
+ right margins, and the block will begin with a <em>FOOTNOTE:</em>
+ label. For example, if the document contains:</p>
+
+ <pre>
+ See the <em>&lt;A HREF="#fn1"&gt;</em><a href=
+"#an1">footnote</a><em>&lt;/A&gt;</em>.
+</pre>
+ <p>activating that link will take you to the labeled rendering
+ of:</p>
+
+ <pre>
+ <em>&lt;FN ID="fn1"&gt;</em>&lt;p&gt;<a name="an1" id=
+"an1">Lynx does not use popups for FN blocks.</a>&lt;/p&gt;<em>&lt;/FN&gt;</em>
+</pre>
+ <p>i.e., position it at the top of the page. Then, upon reading
+ the footnote, you can return to your previous position in the
+ document by pressing the <em>left-arrow</em> key. The content of
+ an FN element can be any HTML markup that is valid in the BODY of
+ the document.</p>
+
+ <p>[<a href="#ToC-Footnotes">ToC</a>]</p>
+
+ <h2 id="id-Notes"><a name="Notes" id="Notes">Lynx and HTML
+ Notes</a></h2>
+
+ <p>Lynx implements the <a href=
+ "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> NOTE
+ element (<em>Admonishment</em>) as a labeled block, i.e., as if a
+ new paragraph were indicated whether or not paragraphing markup
+ is included in its content, with greater than normal left and
+ right margins, and with the type of note indicated by an
+ emphasized label based on the value of its CLASS or ROLE
+ attribute. If no CLASS or ROLE attribute is included, the default
+ label <em>NOTE:</em> will be used. Lynx recognizes the values
+ <em>caution</em> and <em>warning</em>, for which, respectively,
+ the labels <em>CAUTION:</em> or <em>WARNING:</em> will be used.
+ The NOTE element can have an ID attribute, which will be treated
+ as a named <em>A</em>nchor, as for <a href="#Footnotes">HTML
+ 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:</p>
+
+ <pre>
+ <em>&lt;NOTE CLASS="warning" ID="too-bad"&gt;
+ &lt;p&gt;The W3C vendors did not retain NOTE in the HTML 3.2 draft.&lt;/p&gt;
+ &lt;/NOTE&gt;</em>
+</pre>
+ <p>It will <em>degrade gracefully</em> for WWW browsers which do
+ not support NOTE, except for recognition of the ID attribute as a
+ named <em>A</em>nchor.</p>
+
+ <p>[<a href="#ToC-Notes">ToC</a>]</p>
+
+ <h2 id="id-Lists"><a name="Lists" id="Lists">Lynx and HTML
+ Lists</a></h2>
+
+ <p>Lynx implements the <a href=
+ "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> list
+ elements UL (<em>Unordered List</em>), OL (<em>Ordered
+ List</em>), and DL (<em>Definition List</em>), and their
+ associated attributes, and elements (LH, LI, DT, and DD) for the
+ most part as described in that specification. The lists can be
+ nested, yielding progressively greater indentation, up to six
+ levels. The <a href=
+ "http://www.w3.org/MarkUp/html-spec/html-spec_toc.html">HTML
+ 2.0</a> MENU and DIR elements <em>both</em> are treated as
+ synonyms for UL with the PLAIN attribute (no <em>bullets</em>,
+ see below). Note, thus, that neither DIR nor MENU yields a series
+ of columns with 24-character spacing. A single nesting index is
+ maintained, so that different types of List elements can be used
+ for different levels within the nest. Also, the <a href=
+ "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> FIG,
+ CAPTION and CREDIT elements are treated as valid within list
+ blocks. They will be rendered with indentation appropriate for
+ the current nesting depth, and the CAPTION or CREDIT elements
+ will have a <em>CAPTION:</em> or <em>CREDIT:</em> label beginning
+ the first line of their content. The content of any APPLET or
+ OBJECT elements in the lists also will be indented appropriately
+ for the current nesting depth, but those will not invoke line
+ breaks unless indicated by their content, and it should not
+ include markup which is inappropriate within the list.</p>
+
+ <p>Lynx also supports the TYPE attribute for OL elements, which
+ can have values of <em>1</em> for Arabic numbers, <em>I</em> or
+ <em>i</em> for uppercase or lowercase Roman numerals, or
+ <em>A</em> or <em>a</em> for uppercase or lowercase letters, that
+ increment for successive LI elements in the list block. The
+ CONTINUE attribute can be used to continue the ordering from the
+ preceding list block when the nesting depth is changed.</p>
+
+ <p>Lynx treats the OL attributes START and SEQNUM as synonyms for
+ specifying the ordering value for the first LI element in the
+ block. The values should be specified as Arabic numbers, but will
+ be displayed as Arabic, Roman, or alphabetical depending on the
+ TYPE for the block. The values can range from <em>-29997</em> to
+ the system's maximum positive integer for Arabic numbers. For
+ Roman numerals, they can range from <em>1</em> (<em>I</em> or
+ <em>i</em>) to <em>3000</em> (<em>MMM</em> or <em>mmm.</em>). For
+ alphabetical orders, the values can range from <em>1</em>
+ (<em>A</em> or <em>a</em>) to <em>18278</em> (<em>ZZZ</em> or
+ <em>zzz</em>). If the CONTINUE attribute is used, you do not need
+ to specify a START or SEQNUM attribute to extend the ordering
+ from a previous block, and you can include a TYPE attribute to
+ change among Arabic, Roman, or alphabetical ordering styles, or
+ their casing, without disrupting the sequence. If you do not
+ include a START, SEQNUM or CONTINUE attribute, the first LI
+ element of each OL block will default to <em>1</em>, and if you
+ do not include a TYPE attribute, Lynx defaults to Arabic
+ numbers.</p>
+
+ <p>For UL blocks without the PLAIN attribute, Lynx uses
+ <em>*</em>, <em>+</em>, <em>o</em>, <em>#</em>, <em>@</em> and
+ <em>-</em> as <em>bullets</em> to indicate, progressively, the
+ depth within the six nesting levels.</p>
+
+ <p>Lynx treats UL, OL, DIR, and MENU blocks as having the COMPACT
+ attribute by default, i.e., single spaces between LH and LI
+ elements within those blocks. For DL blocks, double spacing will
+ be used to separate the DT and DD elements unless the COMPACT
+ attribute has been specified.</p>
+
+ <p>[<a href="#ToC-Lists">ToC</a>]</p>
+
+ <h2 id="id-Quotes"><a name="Quotes" id="Quotes">Lynx and HTML
+ Quotes</a></h2>
+
+ <p>The <a href=
+ "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> and
+ later specifications provide for two classes of quotation in HTML
+ documents. Block quotes, designated by the BLOCKQUOTE element (or
+ its abbreviated synonym BQ in HTML 3.0), have implied paragraph
+ breaks preceding and following the start and end tags for the
+ block. Character level quotes, designated by the Q element, in
+ contrast are simply directives in the markup to insert an
+ appropriate quotation mark.</p>
+
+ <p>Lynx renders block quotes with a greater than normal left and
+ right indentation. Lynx does not support italics, and normally
+ substitutes underlining, but does not underline block quotes so
+ as not to obscure any explicit emphasis elements within the
+ quotation. The BLOCKQUOTE or BQ block can include a CREDIT
+ container element, whose content will be rendered as an implied
+ new paragraph with a <em>CREDIT:</em> label at the beginning of
+ its first line.</p>
+
+ <p>Lynx respects nested Q start and end tags, and will use ASCII
+ 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
+ the NAME in <em>A</em>nchors.</p>
+
+ <p>[<a href="#ToC-Quotes">ToC</a>]</p>
+
+ <h2 id="id-Eightbit"><a name="Eightbit" id="Eightbit">Lynx and
+ HTML Internationalization: 8bit, UNICODE, etc.</a></h2>
+
+ <p>Lynx has superior support for HTML 4.0/I18N
+ internationalization issues. However, to see the characters other
+ than 7bit properly you <em>should</em> set your <a href=
+ "keystrokes/option_help.html#DC">display character set</a> from
+ Option Menu and save its value, this is a Frequently Asked
+ Question. Fine-turning is also available from <a href=
+ "#lynx.cfg">lynx.cfg</a></p>
+
+ <p>[<a href="#ToC-Eightbit">ToC</a>]</p>
+
+ <h2 id="id-USEMAP"><a name="USEMAP" id="USEMAP">Lynx and
+ Client-Side-Image-Maps</a></h2>
+
+ <p>HTML includes markup, designed primarily for graphic clients,
+ that treats inlined images as maps, such that areas of the image
+ within which a mouse cursor was positioned when the mouse was
+ <em>clicked</em> can correspond to URLs which should be
+ retrieved. The original implementations were based on the client
+ sending an http server the x,y coordinates associated with the
+ <em>click</em>, for handling by a script invoked by the server,
+ and have been termed <em>server-side-image-maps</em>. Lynx has no
+ rational way of coping with such a procedure, and thus simply
+ sends a 0,0 coordinate pair, which some server scripts treat as
+ an instruction to return a document suitable for a text
+ client.</p>
+
+ <p>Newer HTML markup provides bases for the client to determine
+ the URLs associated with areas in the image map, and/or for a
+ text client to process alternative markup and allow the user to
+ make choices based on textual information. These have been termed
+ <em>client-side-image-maps</em>.</p>
+
+ <p>Lynx recognizes and processes the MAP container element and
+ its AREA elements, and will create a menu of links for the HREF
+ of each AREA when the link created for the IMG element with a
+ USEMAP attribute is activated. The menu uses the ALT attributes
+ of the AREA elements as the link names, or, if the document's
+ author has disregard for text clients and sight-challenged
+ Webizens, and thus did not include ALT attributes, Lynx uses the
+ resolved URLs pointed to by the HREF attributes as the link
+ names. Lynx uses the TITLE attribute of the IMG element, or the
+ TITLE attribute of the MAP, if either was present in the markup,
+ as the title and main header of the menu. Otherwise, it uses the
+ ALT attribute of the IMG element. If neither TITLE nor ALT
+ attributes were present in the markup, Lynx creates and uses a
+ <em>[USEMAP]</em> pseudo-ALT. The MAPs need not be in the same
+ document as the IMG elements. If not in the same document, Lynx
+ will fetch the document which contains the referenced MAP, and
+ locate it based on its NAME or ID attribute. All MAPs encountered
+ in documents during a Lynx session are cached, so that they need
+ not be retrieved repeatedly when referenced in different
+ documents.</p>
+
+ <p>If the IMG element also indicates a
+ <em>server-side-image-map</em> via an ISMAP attribute, Lynx
+ normally will create a link for that as well, using an
+ <em>[ISMAP]</em> pseudo-ALT (followed by a hyphen to indicate its
+ association with the <em>client-side-image-map</em>) rather than
+ ignoring it, and will submit a 0,0 coordinate pair if that link
+ is activated. Although, the <em>client-side-image-map</em> may be
+ more useful for a client such as Lynx, because all of the URLs
+ associated with the image map can be accessed, and their nature
+ indicated via ALT attributes, Lynx-friendly sites can map 0,0
+ such that the server returns a for-text-client document
+ homologous to the content of FIG elements (see below). Inclusion
+ of such a link for submissions to the server can be disabled by
+ default via the configuration file (<a href=
+ "#lynx.cfg">lynx.cfg</a>), and the default can be toggled via the
+ <em>-ismap</em> command line switch.</p>
+
+ <p>Lynx also recognizes the <a href=
+ "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> FIG
+ and OVERLAY elements, and will handle them as intended for text
+ clients. These are the ideal way to handle
+ <em>client-side-image-maps</em>, because the FIG content provides
+ complete alternative markup, rather than relying on the client to
+ construct a relatively meager list of links with link names based
+ on ALT strings.</p>
+
+ <p>The presently experimental OBJECT element encompasses much of
+ the functionality of the FIG element for
+ <em>client-side-image-maps</em>. Lynx will render and display the
+ content of OBJECT elements which have the SHAPES attribute
+ equivalently to its handling of FIG. Lynx also handles OBJECT
+ elements with the USEMAP and/or ISMAP attributes equivalently to
+ its handling of IMG elements with <em>client-side-image-maps</em>
+ and/or <em>server-side-image-maps</em>.</p>
+
+ <p>[<a href="#ToC-USEMAP">ToC</a>]</p>
+
+ <h2 id="id-Refresh"><a name="Refresh" id="Refresh">Lynx and
+ Client-Side-Pull</a></h2>
+
+ <p>HTML includes provision for passing instructions to clients
+ via directives in META elements, and one such instruction, via
+ the token <em>Refresh</em>, should invoke reloading of the
+ document, fetched from a server with the same URL or a new URL,
+ at a specified number of seconds following receipt of the current
+ document. This procedure has been termed
+ <em>client-side-pull</em>. An example of such an element is:</p>
+
+ <pre>
+ <em>&lt;META HTTP-EQUIV="Refresh" CONTENT="3; URL=http://host/path"&gt;</em>
+</pre>
+ <p>which instructs a client to fetch the indicated URL in 3
+ seconds after receiving the current document. If the
+ <em>URL=</em> field is omitted, the URL defaults to that of the
+ current document. A <em>no-cache</em> directive is implied when
+ the <em>Refresh</em> if for the same URL.</p>
+
+ <p>Lynx recognizes and processes <em>Refresh</em> directives in
+ META elements, but puts up a labeled link, typically in the upper
+ left corner of the display, indicating the number of seconds
+ intended before a refresh, and the URL for the refresh, instead
+ of making the request automatically after the indicated number of
+ seconds. This allows people using a braille interface any amount
+ of time to examine the current document before activating the
+ link for the next URL. In general, if the number of seconds
+ indicated is short, the timing is not critical and you can
+ activate the link whenever you like. If it is long (e.g., 60
+ seconds), a server process may be generating new documents or
+ images at that interval, and you would be wasting bandwidth by
+ activating the link at a shorter interval.</p>
+
+ <p>[<a href="#ToC-Refresh">ToC</a>]</p>
+
+ <h2 id="id-Cookies"><a name="Cookies" id="Cookies">Lynx State
+ Management</a> (Me want <em>cookie</em>!)</h2>
+
+ <p>HTTP provides a means to carry state information across
+ successive connections between a browser and an http server.
+ Normally, http servers respond to each browser request without
+ relating that request to previous or subsequent requests. Though
+ the inclusion of INPUT fields with TYPE="hidden" can be used as a
+ sort of state management by <a href="#Forms">HTML Forms</a>, a
+ more general approach involves exchanges of MIME headers between
+ the server and browser. When replying to a request, the server
+ can send a <em>Set-Cookie</em> MIME header which contains
+ information (<em>cookies</em>) relevant to the browser's request,
+ and in subsequent requests the browser can send a <em>Cookie</em>
+ MIME header with information derived from previously received
+ cookies.</p>
+
+ <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>, was standardized by the IETF
+ (Internet Engineering Task Force) as <a href=
+ "https://www.ietf.org/rfc/rfc2109.txt">RFC&nbsp;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 &ldquo;<samp>Y</samp>&rdquo;es or
+ &ldquo;<samp>N</samp>&rdquo;o for acceptance of the cookie,
+ &ldquo;<samp>A</samp>&rdquo;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&ldquo;<strong>V</strong>&rdquo;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
+ <em>Ctrl-K</em>, for invoking the <a href=
+ "keystrokes/cookie_help.html">Cookie Jar Page</a>. If Lynx has
+ been compiled with the --enable-persistent-cookies flag, then
+ unexpired cookies will be stored between sessions in the filename
+ set with the COOKIE_FILE option in your .lynxrc.</p>
+
+ <p>A common use of cookies by http servers is simply to track the
+ documents visited by individual users. Though this can be useful
+ to the site's WebMaster for evaluating and improving the
+ organization of links in the various documents of the site, if
+ the user has configured Lynx to include a <em>From</em> MIME
+ header with the user's email address in http requests, or has
+ passed personal information to the server via a form submission,
+ the tracking might be used to draw inferences, possibly
+ incorrect, about that user, and may be considered by some as an
+ invasion of privacy.</p>
+
+ <p>An example of worthwhile State Management via cookies is the
+ setting of personal preferences, typically via a form submission
+ to the site, which will then apply to all documents visited at
+ that site.</p>
+
+ <p>If you accept cookies when accessing a site, but are given no
+ indication about how they will be used in subsequent requests to
+ that site, nor can infer how they will be used, you can
+ <em>Gobble</em> (delete) the cookies and/or change the
+ &ldquo;allow&rdquo; setting for its <em>domain</em> via the
+ <a href="keystrokes/cookie_help.html">Cookie Jar Page</a>.</p>
+
+ <p>[<a href="#ToC-Cookies">ToC</a>]</p>
+
+ <h2 id="id-Cache"><a name="Cache" id="Cache">Cached Documents</a></h2>
+
+ <p>A list of documents which are in lynx's internal cache is
+ accessible through hypothetical <em>Cache Jar</em> which can be
+ examined via the CACHE_JAR keystroke command, normally mapped to
+ <em>Ctrl-X</em>.</p>
+
+ <p>Entries in the <em>Cache Jar</em> are ordered from oldest (at
+ the top) to newest. The user can easily access any document which
+ is in the cache, especially those which may be soon removed due
+ to configurable limits on the maximum number of cached documents,
+ as well as the maximum amount of memory used by the cache.</p>
+
+ <p>The structure of <em>Cache Jar</em> is simple:</p>
+
+ <ul>
+ <li>Each entry starts with its ordinal number (within the
+ session), recently added documents in cache have a smaller
+ number than documents which are added before, and are
+ positioned at the end of <em>Cache Jar</em></li>
+
+ <li>Following its ordinal number is the document title, which
+ is also a link. On activating this link, the user is prompted
+ if they want to delete the document from <em>Cache Jar</em>.
+ The document's address (also a link) follows the title. It is
+ distinguished by a <code>URL:</code> label preceding the link.
+ Activating this link, lynx displays the corresponding cached
+ document.</li>
+
+ <li>Below each cached document URL lynx shows the document
+ properties which include:
+ <ul>
+ <li>Lines,</li>
+
+ <li>Size,</li>
+
+ <li>File-Cache,</li>
+
+ <li>Content-Type,</li>
+
+ <li>Content-Language,</li>
+
+ <li>Content-Encoding,</li>
+
+ <li>Content-Location,</li>
+
+ <li>Subject,</li>
+
+ <li>Owner,</li>
+
+ <li>Date,</li>
+
+ <li>Expires,</li>
+
+ <li>Last-Modified,</li>
+
+ <li>ETag,</li>
+
+ <li>Server, and</li>
+
+ <li>Source-Cache-File.</li>
+ </ul>
+ </li>
+ </ul>
+
+ <p>This feature can be enabled by default using the USE_CACHEJAR
+ symbol in the compilation (<code>userdefs.h</code>), as well as
+ enabled in lynx.cfg</p>
+
+ <p>[<a href="#ToC-Cache">ToC</a>]</p>
+
+ <h2 id="id-Sessions"><a name="Sessions" id=
+ "Sessions"><em>Sessions</em></a></h2>
+
+ <p>Lynx's current state (all information about the user's current
+ activity with lynx) is called a session. Sessions are useful in
+ particular if you are in the middle of exploring something on the
+ web and you were forced to stop abruptly, losing any trace of
+ your current work.</p>
+
+ <p>A session can be automatically restored as lynx starts after a
+ clean exit. The session data is saved if lynx is invoked with the
+ <em>-session=FILENAME</em> switch. The <em>FILENAME</em> is the
+ name of the file where the session will be stored.</p>
+
+ <p>There are also switches for only restoring:
+ <em>-sessionin=FILENAME</em> and for only saving:
+ <em>-sessionout=FILENAME</em> sessions:</p>
+
+ <p>If you do not want to specify these options at each lynx
+ startup, there is an option in <em>lynx.cfg</em> to enable
+ automatic saving/restoring of session. To keep lynx startup/exit
+ reasonable fast there is also an option in <em>lynx.cfg</em>
+ specifying how much information about the current lynx session
+ will be stored in file.</p>
+
+ <p>The syntax of the session file is simple. You can use a text
+ editor to modify, add new entries, or remove URLs you no longer
+ want.</p>
+
+ <p>[<a href="#ToC-Sessions">ToC</a>]</p>
+
+ <h2 id="id-Invoking"><a name="Invoking" id="Invoking">The Lynx
+ command line</a></h2>
+
+ <p>A summary of the Lynx command line options (switches) is
+ returned to stdout if Lynx is invoked with the <em>-help</em>
+ switch. A description of the options also should be available via
+ the system man (Unix) pages or help (VMS) libraries. On Win32,
+ typing lynx -help in a DOS window should display similarly. The
+ basic syntax of the Lynx command line can be represented as one
+ of the following:</p>
+
+ <dl>
+ <dt><code>Command</code>
+ </dt>
+
+ <dd><code>lynx [options]</code>
+ </dd>
+
+ <dd><code>lynx [options] startfile</code>
+ </dd>
+ </dl>
+
+ <p>where</p>
+
+ <dl>
+ <dt><code>startfile</code>
+ </dt>
+
+ <dd>
+ <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
+ starting file and base directory determined during
+ installation.</li>
+
+ <li>If a specified file is local (i.e., not a URL) Lynx
+ displays that file and uses the directory in which that
+ file resides as the base directory.</li>
+
+ <li>If a URL is specified, the file will be retrieved, and
+ only the server base directory will be relevant to further
+ accesses.</li>
+
+ <li>If more than one local file or remote URL is listed on
+ the command line, Lynx will open only the last
+ interactively. All of the names (local files and remote
+ URLs) are added to the G)oto history.</li>
+ </ul>
+ </dd>
+
+ <dt><code>options</code>
+ </dt>
+
+ <dd>
+ <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
+ in the reference below. The other options set boolean values
+ in the program. There are three types of boolean options:
+ set, unset and toggle. If no option value is given, these
+ have the obvious meaning: set (to true), unset (to false), or
+ 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>
+
+ <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
+ option-values are ignored.</p>
+
+ <p>The default boolean, number and string option values that
+ are compiled into lynx are displayed in the help-message
+ provided by lynx -help. Some of those may differ according to
+ how lynx was built; see the help message itself for these
+ values. The -help option is processed before any option,
+ including those that control reading from the lynx.cfg file.
+ Therefore runtime configuration values are not reflected in
+ the help-message.</p>
+
+ <p>Capitalized items in the option summary indicate that a
+ substitution must be made. These are the options:</p>
+
+ <dl>
+ <dt><code><strong>-</strong></code>
+ </dt>
+
+ <dd>
+ <p>If the argument is only
+ &ldquo;<code><strong>-</strong></code>&rdquo; (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 &ldquo;<samp>$</samp>&rdquo;. 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>
+ <p>accept all cookies.</p>
+ </dd>
+
+ <dt><code><strong>-anonymous</strong></code>
+ </dt>
+
+ <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>
+ <p>charset for documents that do not specify it.</p>
+ </dd>
+
+ <dt>
+ <code><strong>-assume_local_charset=</strong><em>MIMENAME</em></code>
+ </dt>
+
+ <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>
+ <p>use this instead of unrecognized charsets.</p>
+ </dd>
+
+ <dt><code><strong>-auth=</strong><em>ID:PW</em></code>
+ </dt>
+
+ <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>
+ <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>
+ <p>specify a local bibp server (default
+ http://bibhost/).</p>
+ </dd>
+
+ <dt><code><strong>-blink</strong></code>
+ </dt>
+
+ <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>
+ <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>
+ <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>
+ <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>
+ <p>Toggle center alignment in HTML TABLE.</p>
+ </dd>
+
+ <dt><code><strong>-case</strong></code>
+ </dt>
+
+ <dd>
+ <p>enable case-sensitive string searching.</p>
+ </dd>
+
+ <dt><code><strong>-cfg=</strong><em>FILENAME</em></code>
+ </dt>
+
+ <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>
+ <p>exit on left-arrow in startfile, and disable save to
+ disk.</p>
+ </dd>
+
+ <dt><code><strong>-child_relaxed</strong></code>
+ </dt>
+
+ <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>
+ <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>
+ <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:</p>
+
+ <dl>
+ <dt><code><strong>exit</strong></code>
+ </dt>
+
+ <dd>
+ <p>causes the script to stop, and forces lynx to exit
+ immediately.</p>
+ </dd>
+
+ <dt><code><strong>key</strong></code>
+ </dt>
+
+ <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>
+ <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>
+ <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 without regard to
+ 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>
+ <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>
+ <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>
+ <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>
+ <p>toggles handling of Set-Cookie headers.</p>
+ </dd>
+
+ <dt><code><strong>-core</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles forced core dumps on fatal errors. (Unix
+ only)</p>
+ </dd>
+
+ <dt><code><strong>-crawl</strong></code>
+ </dt>
+
+ <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>
+ <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>
+ <p>separate incremental display stages with MessageSecs
+ delay</p>
+ </dd>
+
+ <dt><code><strong>-display=</strong><em>DISPLAY</em></code>
+ </dt>
+
+ <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>
+ <p>set the charset for the terminal output.</p>
+ </dd>
+
+ <dt><code><strong>-dont_wrap_pre</strong></code>
+ </dt>
+
+ <dd>
+ <p>inhibit wrapping of text in &lt;pre&gt; when -dump'ing
+ and -crawl'ing, mark wrapped lines in interactive
+ session.</p>
+ </dd>
+
+ <dt><code><strong>-dump</strong></code>
+ </dt>
+
+ <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>
+ <p>enable external editing using the specified
+ <em>EDITOR</em>. (vi, ed, emacs, etc.)</p>
+ </dd>
+
+ <dt><code><strong>-emacskeys</strong></code>
+ </dt>
+
+ <dd>
+ <p>enable emacs-like key movement.</p>
+ </dd>
+
+ <dt><code><strong>-enable_scrollback</strong></code>
+ </dt>
+
+ <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>
+ <p>the status code from the HTTP request is placed in
+ this file.</p>
+ </dd>
+
+ <dt><code><strong>-exec</strong></code>
+ </dt>
+
+ <dd>
+ <p>enable local program execution (normally not
+ configured).</p>
+ </dd>
+
+ <dt><code><strong>-fileversions</strong></code>
+ </dt>
+
+ <dd>
+ <p>include all versions of files in local VMS directory
+ listings.</p>
+ </dd>
+
+ <dt><code><strong>-find_leaks</strong></code>
+ </dt>
+
+ <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>
+ <p>force HREF-less &ldquo;A&rdquo; elements to be empty
+ (close them as soon as they are seen).</p>
+ </dd>
+
+ <dt><code><strong>-force_html</strong></code>
+ </dt>
+
+ <dd>
+ <p>forces the first document to be interpreted as
+ HTML.</p>
+ </dd>
+
+ <dt><code><strong>-force_secure</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles forcing of the secure flag for SSL
+ cookies.</p>
+ </dd>
+
+ <dt><code><strong>-forms_options</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles whether the Options Menu is key-based or
+ form-based.</p>
+ </dd>
+
+ <dt><code><strong>-from</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles transmissions of From headers to HTTP or HTTPS
+ servers.</p>
+ </dd>
+
+ <dt><code><strong>-ftp</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable ftp access.</p>
+ </dd>
+
+ <dt><code><strong>-get_data</strong></code>
+ </dt>
+
+ <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 &ldquo;---&rdquo;.</p>
+ </dd>
+
+ <dt><code><strong>-head</strong></code>
+ </dt>
+
+ <dd>
+ <p>send a HEAD request for the mime headers.</p>
+ </dd>
+
+ <dt><code><strong>-help</strong></code>
+ </dt>
+
+ <dd>
+ <p>print this Lynx command syntax usage message.</p>
+ </dd>
+
+ <dt>
+ <code><strong>-hiddenlinks=</strong><em>option</em></code>
+ </dt>
+
+ <dd>
+ <p>control the display of hidden links. Option values
+ are:</p>
+
+ <dl>
+ <dt><code><strong>merge</strong></code>
+ </dt>
+
+ <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>
+ <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>
+ <p>hidden links do not appear even in listings.</p>
+ </dd>
+ </dl>
+ </dd>
+
+ <dt><code><strong>-historical</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles use of &ldquo;&gt;&rdquo; or
+ &ldquo;--&gt;&rdquo; as a terminator for comments.</p>
+ </dd>
+
+ <dt><code><strong>-homepage=</strong><em>URL</em></code>
+ </dt>
+
+ <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
+ &ldquo;<samp>m</samp>&rdquo;ain menu command.</p>
+ </dd>
+
+ <dt><code><strong>-image_links</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles inclusion of links for all images.</p>
+ </dd>
+
+ <dt><code><strong>-ismap</strong></code>
+ </dt>
+
+ <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>
+ <p>set the default index file to the specified
+ <em>URL</em></p>
+ </dd>
+
+ <dt><code><strong>-justify</strong></code>
+ </dt>
+
+ <dd>
+ <p>do justification of text.</p>
+ </dd>
+
+ <dt><code><strong>-link=</strong><em>NUMBER</em></code>
+ </dt>
+
+ <dd>
+ <p>starting count for lnk#.dat files produced by
+ <em>-crawl</em>.</p>
+ </dd>
+
+ <dt><code><strong>-localhost</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable URLs that point to remote hosts.</p>
+ </dd>
+
+ <dt><code><strong>-locexec</strong></code>
+ </dt>
+
+ <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>
+ <p>specify filename containing color-style information.
+ The default is lynx.lss.</p>
+ </dd>
+
+ <dt><code><strong>-mime_header</strong></code>
+ </dt>
+
+ <dd>
+ <p>include mime headers and force source dump.</p>
+ </dd>
+
+ <dt><code><strong>-minimal</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles minimal versus valid comment parsing. When
+ minimal, any &ldquo;--&gt;&rdquo; serves as a terminator
+ for a comment element. When valid, pairs of
+ &ldquo;--&rdquo; 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>
+ <p>toggles nested-tables logic (for debugging).</p>
+ </dd>
+
+ <dt>
+ <code><strong>-newschunksize=</strong><em>NUMBER</em></code>
+ </dt>
+
+ <dd>
+ <p>number of articles in chunked news listings.</p>
+ </dd>
+
+ <dt>
+ <code><strong>-newsmaxchunk=</strong><em>NUMBER</em></code>
+ </dt>
+
+ <dd>
+ <p>maximum news articles in listings before chunking.</p>
+ </dd>
+
+ <dt><code><strong>-nobold</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable bold video-attribute.</p>
+ </dd>
+
+ <dt><code><strong>-nobrowse</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable directory browsing.</p>
+ </dd>
+
+ <dt><code><strong>-nocc</strong></code>
+ </dt>
+
+ <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>
+ <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>
+ <p>disable local program execution. (DEFAULT)</p>
+ </dd>
+
+ <dt><code><strong>-nofilereferer</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable transmissions of Referer headers for file
+ URLs.</p>
+ </dd>
+
+ <dt><code><strong>-nolist</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable the link list feature in dumps.</p>
+ </dd>
+
+ <dt><code><strong>-nolog</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable mailing of error messages to document
+ owners.</p>
+ </dd>
+
+ <dt><code><strong>-nomargins</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable left/right margins in the default style
+ sheet.</p>
+ </dd>
+
+ <dt><code><strong>-nomore</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable -more- string in statusline messages.</p>
+ </dd>
+
+ <dt><code><strong>-nonrestarting_sigwinch</strong></code>
+ </dt>
+
+ <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>
+ <p>disable forced pauses for statusline messages.</p>
+ </dd>
+
+ <dt><code><strong>-noprint</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable most print functions.</p>
+ </dd>
+
+ <dt><code><strong>-noredir</strong></code>
+ </dt>
+
+ <dd>
+ <p>do not follow URL redirections</p>
+ </dd>
+
+ <dt><code><strong>-noreferer</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable transmissions of Referer headers.</p>
+ </dd>
+
+ <dt><code><strong>-noreverse</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable reverse video-attribute.</p>
+ </dd>
+
+ <dt><code><strong>-nosocks</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable SOCKS proxy usage by a SOCKSified Lynx.</p>
+ </dd>
+
+ <dt><code><strong>-nostatus</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable the retrieval status messages.</p>
+ </dd>
+
+ <dt><code><strong>-notitle</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable title and blank line from top of page.</p>
+ </dd>
+
+ <dt><code><strong>-nounderline</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable underline video-attribute.</p>
+ </dd>
+
+ <dt><code><strong>-number_fields</strong></code>
+ </dt>
+
+ <dd>
+ <p>force numbering of links as well as form input
+ fields.</p>
+ </dd>
+
+ <dt><code><strong>-number_links</strong></code>
+ </dt>
+
+ <dd>
+ <p>force numbering of links.</p>
+ </dd>
+
+ <dt><code><strong>-partial</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles displaying of partial pages while loading.</p>
+ </dd>
+
+ <dt>
+ <code><strong>-partial_thres=</strong><em>NUMBER</em></code>
+ </dt>
+
+ <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>
+ <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>
+ <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 &ldquo;o&rdquo;ptions menu. The command line
+ switch toggles the default.</p>
+ </dd>
+
+ <dt><code><strong>-post_data</strong></code>
+ </dt>
+
+ <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 &ldquo;---&rdquo;.</p>
+ </dd>
+
+ <dt><code><strong>-preparsed</strong></code>
+ </dt>
+
+ <dd>
+ <p>show source preparsed and reformatted when used with
+ -source or in source view (&ldquo;<samp>\</samp>&rdquo;).
+ 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 &ldquo;<samp>^V</samp>&rdquo;.</p>
+ </dd>
+
+ <dt><code><strong>-prettysrc</strong></code>
+ </dt>
+
+ <dd>
+ <p>do syntax highlighting and hyperlink handling in
+ source view.</p>
+ </dd>
+
+ <dt><code><strong>-print</strong></code>
+ </dt>
+
+ <dd>
+ <p>enable print functions. (default)</p>
+ </dd>
+
+ <dt><code><strong>-pseudo_inlines</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles pseudo-ALTs for inline images with no ALT
+ string.</p>
+ </dd>
+
+ <dt><code><strong>-raw</strong></code>
+ </dt>
+
+ <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>
+ <p>restricts access to URLs in the starting realm.</p>
+ </dd>
+
+ <dt><code><strong>-reload</strong></code>
+ </dt>
+
+ <dd>
+ <p>flushes the cache on a proxy server (only the first
+ document affected).</p>
+ </dd>
+
+ <dt><code><strong>-restrictions</strong></code>
+ </dt>
+
+ <dd>
+ <p>allows a list of services to be disabled selectively
+ and takes the following form:</p>
+ </dd>
+
+ <dd>
+ <p><em>lynx
+ -restrictions=[option][,option][,option]...</em>
+ </p>
+ </dd>
+
+ <dd>
+ <p>The list of recognized options is printed if none are
+ specified.</p>
+
+ <dl>
+ <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><strong><samp>editor</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow external editing.</p>
+ </dd>
+
+ <dt><strong><samp>exec</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disable execution scripts.</p>
+ </dd>
+
+ <dt><strong><samp>exec_frozen</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow the user from changing the local
+ execution option.</p>
+ </dd>
+
+ <dt><strong><samp>externals</samp></strong>
+ </dt>
+
+ <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><strong><samp>file_url</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow using G)oto, served links or bookmarks
+ for file: URLs.</p>
+ </dd>
+
+ <dt><strong><samp>goto</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disable the &ldquo;<samp>g</samp>&rdquo; (goto)
+ command.</p>
+ </dd>
+
+ <dt><strong><samp>inside_ftp</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow ftps for people coming from inside your
+ domain.</p>
+ </dd>
+
+ <dt><strong><samp>inside_news</samp></strong>
+ </dt>
+
+ <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><strong><samp>inside_rlogin</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow rlogins for people coming from inside
+ your domain.</p>
+ </dd>
+
+ <dt><strong><samp>inside_telnet</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow telnets for people coming from inside
+ your domain.</p>
+ </dd>
+
+ <dt><strong><samp>jump</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disable the &ldquo;<samp>j</samp>&rdquo; (jump)
+ command.</p>
+ </dd>
+
+ <dt><strong><samp>lynxcgi</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow execution of Lynx CGI URLs.</p>
+ </dd>
+
+ <dt><strong><samp>mail</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow mailing feature.</p>
+ </dd>
+
+ <dt><strong><samp>multibook</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow multiple bookmarks.</p>
+ </dd>
+
+ <dt><strong><samp>news_post</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow USENET News posting,</p>
+ </dd>
+
+ <dt><strong><samp>options_save</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow saving options in .lynxrc.</p>
+ </dd>
+
+ <dt><strong><samp>outside_ftp</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow ftps for people coming from outside your
+ domain.</p>
+ </dd>
+
+ <dt><strong><samp>outside_news</samp></strong>
+ </dt>
+
+ <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><strong><samp>outside_rlogin</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow rlogins for people coming from outside
+ your domain.</p>
+ </dd>
+
+ <dt><strong><samp>outside_telnet</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow telnets for people coming from outside
+ your domain.</p>
+ </dd>
+
+ <dt><strong><samp>print</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow most print options.</p>
+ </dd>
+
+ <dt><strong><samp>shell</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow shell escapes.</p>
+ </dd>
+
+ <dt><strong><samp>suspend</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow <em>Control-Z</em> suspends with escape
+ to shell on Unix.</p>
+ </dd>
+
+ <dt><strong><samp>telnet_port</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow specifying a port in telnet G)oto's.</p>
+ </dd>
+
+ <dt><strong><samp>useragent</samp></strong>
+ </dt>
+
+ <dd>
+ <p>disallow modifications of the User-Agent
+ header.</p>
+ </dd>
+ </dl>
+ </dd>
+
+ <dt><code><strong>-resubmit_posts</strong></code>
+ </dt>
+
+ <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>
+ <p>disable recognition of rlogin commands.</p>
+ </dd>
+
+ <dt><code><strong>-scrollbar</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles showing scrollbar.</p>
+ </dd>
+
+ <dt><code><strong>-scrollbar_arrow</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles showing arrows at ends of the scrollbar.</p>
+ </dd>
+
+ <dt><code><strong>-selective</strong></code>
+ </dt>
+
+ <dd>
+ <p>require .www_browsable files to browse
+ directories.</p>
+ </dd>
+
+ <dt>
+ <code><strong>-session=</strong><em>FILENAME</em></code>
+ </dt>
+
+ <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>
+ <p>resumes session from specified file.</p>
+ </dd>
+
+ <dt>
+ <code><strong>-sessionout=</strong><em>FILENAME</em></code>
+ </dt>
+
+ <dd>
+ <p>saves session to specified file.</p>
+ </dd>
+
+ <dt><code><strong>-short_url</strong></code>
+ </dt>
+
+ <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>
+ <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 &ldquo;o&rdquo;ptions menu. The command
+ line switch toggles the default.</p>
+ </dd>
+
+ <dt><code><strong>-show_rate</strong></code>
+ </dt>
+
+ <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>
+ <p>toggles emulation of the old Netscape and Mosaic bug
+ which treated &ldquo;<samp>&gt;</samp>&rdquo; as a
+ co-terminator for double-quotes and tags.</p>
+ </dd>
+
+ <dt><code><strong>-source</strong></code>
+ </dt>
+
+ <dd>
+ <p>works the same as dump but outputs HTML source instead
+ of formatted text. For example</p>
+
+ <blockquote>
+ <pre>
+lynx -source . &gt;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>
+
+ <blockquote>
+ <pre>
+lynx -source ./ &gt;foo.html
+</pre>
+ </blockquote>
+ </dd>
+
+ <dt><code><strong>-stack_dump</strong></code>
+ </dt>
+
+ <dd>
+ <p>disable SIGINT cleanup handler.</p>
+ </dd>
+
+ <dt><code><strong>-startfile_ok</strong></code>
+ </dt>
+
+ <dd>
+ <p>allow non-http startfile and homepage with
+ <em>-validate</em>.</p>
+ </dd>
+
+ <dt><code><strong>-stderr</strong></code>
+ </dt>
+
+ <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>
+ <p>read the startfile from standard input (UNIX
+ only).</p>
+ </dd>
+
+ <dt><code><strong>-syslog=</strong><em>text</em></code>
+ </dt>
+
+ <dd>
+ <p>information for syslog call.</p>
+ </dd>
+
+ <dt><code><strong>-syslog-urls</strong></code>
+ </dt>
+
+ <dd>
+ <p>log requested URLs with syslog.</p>
+ </dd>
+
+ <dt><code><strong>-tagsoup</strong></code>
+ </dt>
+
+ <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>
+ <p>disable recognition of telnet commands.</p>
+ </dd>
+
+ <dt><code><strong>-term=</strong><em>TERM</em></code>
+ </dt>
+
+ <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>
+ <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>
+ <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,
+ &ldquo;<samp>;</samp>&rdquo;) 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>
+ <p>turns on <a href="#tna">"Textfields Need
+ Activation"</a> mode.</p>
+ </dd>
+
+ <dt><code><strong>-trace</strong></code>
+ </dt>
+
+ <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,
+ &ldquo;<samp>;</samp>&rdquo;) 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>
+ <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>
+ <p>SGML character parsing states</p>
+ </dd>
+
+ <dt>2</dt>
+
+ <dd>
+ <p>color-style</p>
+ </dd>
+
+ <dt>4</dt>
+
+ <dd>
+ <p>TRST (table layout)</p>
+ </dd>
+
+ <dt>8</dt>
+
+ <dd>
+ <p>config (lynx.cfg and .lynxrc contents)</p>
+ </dd>
+
+ <dt>16</dt>
+
+ <dd>
+ <p>binary string copy/append, used in form data
+ construction.</p>
+ </dd>
+ </dl>
+ </dd>
+
+ <dt><code><strong>-traversal</strong></code>
+ </dt>
+
+ <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>
+ <p>trim input text/textarea fields in forms.</p>
+ </dd>
+
+ <dt><code><strong>-underscore</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles use of _underline_ format in dumps.</p>
+ </dd>
+
+ <dt><code><strong>-update_term_title</strong></code>
+ </dt>
+
+ <dd>
+ <p>enables updating the title in terminal emulators. Use
+ only if your terminal emulator supports that escape code.
+ Has no effect when used with -notitle.</p>
+ </dd>
+
+ <dt><code><strong>-use_mouse</strong></code>
+ </dt>
+
+ <dd>
+ <p>turn on mouse support, if available.</p>
+ </dd>
+
+ <dt>
+ <code><strong>-useragent=</strong><em>STRING</em></code>
+ </dt>
+
+ <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>
+ <p>accept only http URLs (meant for validation).</p>
+ </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>
+ <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
+ "anonymous" accounts is with an explicit
+ <em>-restrictions=default</em>.</p>
+ </dd>
+
+ <dt><code><strong>-verbose</strong></code>
+ </dt>
+
+ <dd>
+ <p>toggles [LINK], [IMAGE] and [INLINE] comments with
+ filenames of these images.</p>
+ </dd>
+
+ <dt><code><strong>-version</strong></code>
+ </dt>
+
+ <dd>
+ <p>print version information.</p>
+ </dd>
+
+ <dt><code><strong>-vikeys</strong></code>
+ </dt>
+
+ <dd>
+ <p>enable vi-like key movement.</p>
+ </dd>
+
+ <dt><code><strong>-wdebug</strong></code>
+ </dt>
+
+ <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>
+ <p>number of columns for formatting of dumps, default is
+ 80.</p>
+ </dd>
+
+ <dt><code><strong>-with_backspaces</strong></code>
+ </dt>
+
+ <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
+ (&ldquo;<samp>=</samp>&rdquo;) 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>
+
+ <h2 id="Environments"><a name="Environment" id=
+ "Environment"><em>Environment variables used by Lynx</em></a></h2>
+
+ <p>Lynx uses certain environment variables and sets a few of
+ them. Please visit a <a href=
+ "keystrokes/environments.html">separate page</a> for this rather
+ technical information.</p>
+
+ <p>[<a href="#ToC-Environment">ToC</a>]</p>
+
+ <h2 id="id-lynx.cfg"><a name="lynx.cfg" id="lynx.cfg">Main
+ configuration file lynx.cfg</a></h2>
+
+ <p>Lynx has several levels of customization: from the Options
+ Menu (accessible on-line, and possibly stored in your local
+ .lynxrc file), via command-line switches on startup (mainly for
+ batch processing). The most important and numerous default
+ settings are stored in the Lynx configuration file
+ <em>lynx.cfg</em>.</p>
+
+ <p>If you are on a UNIX system you should have appropriate
+ permissions to make changes there or ask your system
+ administrator to modify lynx.cfg for your needs. This file
+ provides default settings for all accounts on your system. It may
+ be copied to your shell account and included with -cfg command
+ line switch or via an environment variable LYNX_CFG (if you have
+ shell access). Starting with version 2.8.1 Lynx has an include
+ facility so you can load the system-wide configuration file and
+ easily add one or more settings from your local add-on
+ configuration file. It is really cool to read lynx.cfg with its
+ comments for hundreds of options, most of them commented out
+ because they are built-in defaults. You may visit an index of
+ options: <a href=
+ "https://lynx.invisible-island.net/release/lynx_help/cattoc.html">
+ by category</a> or <a href=
+ "https://lynx.invisible-island.net/release/lynx_help/alphatoc.html">
+ by alphabet</a>.</p>
+
+ <p>To view your current configuration derived from lynx.cfg and
+ any included configuration files, press <em>&ldquo;g&rdquo;</em>
+ and type in &ldquo;<samp>lynxcfg:</samp>&rdquo;. If you are using
+ the forms-based <em>Options Menu</em>, you may press
+ <em>&ldquo;o&rdquo;</em> for the Options Menu and follow the
+ <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
+ probably will not see your lynx.cfg.</p>
+
+ <p>[<a href="#ToC-lynx.cfg">ToC</a>]</p>
+
+ <h2 id="id-Hist"><a name="Hist" id="Hist">Lynx development
+ history</a></h2>
+
+ <p>Lynx grew out of efforts to build a campus-wide information
+ system at The University of Kansas. The earliest versions of Lynx
+ provided a user-friendly, distributed hypertext interface for
+ users connected to multiuser (Unix and VMS) systems via
+ curses-oriented display devices. A custom hypertext format was
+ developed to support hypertext links to local files and files on
+ remote Gopher servers. Using Gopher servers for distributed file
+ service allowed information providers to publish information from
+ a wide variety of platforms (including Unix, VMS, VM/CMS and
+ Macintosh). In addition, Lynx became the most user-friendly
+ Gopher client, although that was only an ancillary
+ capability.</p>
+
+ <p>This distributed approach let providers retain complete
+ control over their information, but it made communication between
+ users and providers somewhat more difficult. Following the lead
+ of Neal Erdwien, of Kansas State University, the Lynx hypertext
+ format was extended to include links for including ownership
+ information with each file. This information made it possible for
+ users running Lynx clients to send comments and suggestions via
+ e-mail to the providers.</p>
+
+ <p>This early version of Lynx was also augmented to support
+ hypertext links to programs running on remote systems. It
+ included the ability to open a Telnet connection, as well as the
+ ability to start programs via rexec, inetd, or by direct socket
+ connects. These capabilities were included to allow users to
+ access databases or custom program interfaces.</p>
+
+ <p>A subsequent version of Lynx incorporated the World Wide Web
+ libraries to allow access to the full list of WWW servers, along
+ with the option to build hypertext documents in HTML, rather than
+ the native Lynx format. HTML has become far more widely used, and
+ the native format has been phased out. With the addition of the
+ WWW libraries, Lynx became a fully-featured WWW client, limited
+ only by the display capabilities offered in the curses
+ environment.</p>
+
+ <p>Lynx was designed by Lou Montulli, Charles Rezac and Michael
+ Grobe of Academic Computing Services at The University of Kansas.
+ Lynx was implemented by Lou Montulli and maintained by Garrett
+ Arch Blythe and Craig Lavender.</p>
+
+ <p><em>Foteos Macrides</em> and members of the <a href=
+ "lynx-dev.html">lynx-dev</a> list have developed and supported
+ Lynx since release of v2.3 in May 1994.<br>
+ The Lynx2-3FM code set was released as v2.4 in June 1995.<br>
+ The Lynx2-4FM code set was released as v2.5 in May 1996.<br>
+ The Lynx2-5FM code set was released as v2.6 in September
+ 1996.<br>
+ The Lynx2-6FM code set was released as v2.7 in February 1997.<br>
+ The v2-7FM code set was released as v2.7.1 in April 1997.<br>
+ The v2-7-1FM code set was released as v2.7.2 in January 1998.<br>
+ The 2.7.1 development set was released as v2.8 in March 1998.<br>
+ The 2.8 development set was released as v2.8.1 in October
+ 1998.<br>
+ The 2.8.1 development set was released as v2.8.2 in June
+ 1999.<br>
+ The 2.8.2 development set was released as v2.8.3 in April
+ 2000.<br>
+ The 2.8.3 development set was released as v2.8.4 in July
+ 2001.<br>
+ The 2.8.4 development set was released as v2.8.5 in February
+ 2004.<br>
+ The 2.8.5 development set was released as v2.8.6 in October
+ 2006.<br>
+ The 2.8.6 development set was released as v2.8.7 in July
+ 2009.<br>
+ The 2.8.7 development set was released as v2.8.8 in February
+ 2014.<br>
+ The 2.8.8 development set was released as v2.8.9 in July
+ 2018.<br></p>
+
+ <p>Since early 1997, the Lynx code has expanded into
+ autoconfigure and PC versions. The branching of the Lynx source
+ base from a single source into two sources (FM/Foteos Macrides
+ and ac/autoconfigure) should be considered a healthy synergism
+ among groups of computer professionals acting in their spare time
+ out of a common goal.</p>
+
+ <p>Lynx has incorporated code from a variety of sources along the
+ way. The earliest versions of Lynx included code from Earl Fogel
+ of Computing Services at the University of Saskatchewan, who
+ implemented HYPERREZ in the Unix environment. Those versions also
+ incorporated libraries from the Unix Gopher clients developed at
+ the University of Minnesota, and the later versions of Lynx rely
+ on the WWW client library code developed by Tim Berners-Lee (and
+ others) and the WWW community.</p>
+
+ <p>Contributors have generally been acknowledged in the CHANGES
+ file. Earlier CHANGES file can be found in the docs/ subdirectory
+ of this distribution.</p>
+
+ <p>Information on obtaining the most current version of Lynx is
+ available at <a href=
+ "https://lynx.invisible-island.net/current/index.html">the
+ current distribution page</a>.</p>
+
+ <p>[<a href="#Contents">ToC</a>]</p>
+</body>
+</html>
diff --git a/lynx_help/about_lynx.html b/lynx_help/about_lynx.html
new file mode 100644
index 0000000..f4a875b
--- /dev/null
+++ b/lynx_help/about_lynx.html
@@ -0,0 +1,113 @@
+<!-- $LynxId: about_lynx.html,v 1.24 2021/07/01 21:02:17 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>About Lynx &ndash; Who, What, and When &ndash; Where it is
+ now</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Give a little history of Lynx, by whom and where it was originally developed, and add some of its current contact information.">
+</head>
+<body>
+ <blockquote>
+ <p>[ <a href="lynx-dev.html">About Lynx-Dev</a> | <a href=
+ "http://mail.gnu.org/mailman/listinfo/lynx-dev/">Lynx-Dev
+ Archives</a> ]</p>
+ </blockquote>
+
+ <h2>About Lynx</h2>
+
+ <p><strong>Lynx</strong> is a fully-featured <em>World Wide
+ Web</em> (<em>WWW</em>) browser for users on Unix, VMS, and other
+ platforms running cursor-addressable, character-cell terminals or
+ emulators. That includes vt100 terminals, other character-cell
+ displays, and vt100 emulators such as Kermit or Procomm running
+ on PCs or Macs.</p>
+
+ <p>For information on how to use <strong>Lynx</strong> see the
+ <a href="Lynx_users_guide.html">Lynx User's Guide</a>, or the
+ <a href="lynx_help_main.html">Lynx help files</a>.</p>
+
+ <h2>Credits and Copyright</h2>
+
+ <p><strong>Lynx</strong> was a product of the Distributed
+ Computing Group within Academic Computing Services of <a href=
+ "http://web.archive.org/web/19971210163627/http://www.cc.ukans.edu/">
+ The University of Kansas</a>.</p>
+
+ <p><strong>Lynx</strong> was originally developed by <a href=
+ "http://web.archive.org/web/20040309105337/http://www.cc.ukans.edu/cwis/people/Lou.Montulli.html">
+ Lou Montulli</a>, <a href=
+ "http://condor.cc.ku.edu/~grobe/">Michael Grobe</a>, and <a href=
+ "http://web.archive.org/web/20040412210202/http://www.cc.ukans.edu/cwis/people/Charles.Rezac.html">
+ Charles Rezac</a>. <a href=
+ "http://web.archive.org/web/20040412210651/http://www.cc.ukans.edu/cwis/people/Garrett/Garrett_Arch_Blythe.html">
+ Garrett Blythe</a> created <a href=
+ "http://web.archive.org/web/20040812204015/http://www.cc.ukans.edu/about_doslynx/doslynx.html">
+ DosLynx</a> and later joined the <strong>Lynx</strong> effort as
+ well. Following the departures of Lou and Garrett for positions
+ at Netscape in the summer of 1994, <em>Craig Lavender</em>
+ provided support services for <strong>Lynx</strong>, and
+ <em>Ravikumar Kolli</em> for DosLynx.</p>
+
+ <p><strong>Lynx</strong> is maintained and supported by members
+ of the Internet community coordinated via the <a href=
+ "#lynx-dev_list"><em>lynx-dev mailing list</em></a>.</p>
+
+ <p><strong>Lynx</strong> is derived from material copyrighted by
+ the University of Kansas. However most of the release (and
+ corresponding copyright) is the work of developers on the
+ <a href="#lynx-dev_list"><em>lynx-dev mailing list</em></a>. It
+ is distributed <a href="COPYHEADER">without restrictions on usage
+ or redistribution</a> under the <a href="COPYING">GNU General
+ Public License (Version 2)</a>.</p>
+
+ <p><strong>Lynx</strong> was built over an early version of the
+ Common Code Library developed by the CERN WWW Project. That code
+ is copyrighted by CERN. <strong>Lynx</strong> contains other
+ sections of code that are copyrighted by other institutions or
+ individuals. The <strong>Lynx</strong> copyright does not
+ override or invalidate those copyrights.</p>
+
+ <p>Thanks to <a name="note13" href=
+ "http://www.w3.org/People/Berners-Lee/" id="note13">Tim
+ Berners-Lee</a> and the other <a name="note14" href=
+ "http://www.w3.org/People.html" id="note14">CERN World Wide Web
+ wizards</a> for the WWW client library code and all of their
+ other work on the WWW project, NCSA and the <a href=
+ "http://archive.ncsa.uiuc.edu/SDG/Software/Mosaic/NCSAMosaicHome.html">
+ Mosaic</a> developers, and to everyone out in netland who has
+ contributed to <strong>Lynx</strong>'s development either
+ directly (through comments or bug reports) or indirectly (through
+ inspiration and development of other systems).</p>
+
+ <p>Also, special thanks go to <em>Foteos Macrides</em> who ported
+ much of <strong>Lynx</strong> to VMS and did much of its
+ development following Lou Montulli's and Garrett Blythe's
+ departures from the University of Kansas, and to <em>Earl
+ Fogel</em> of the University of Saskatchewan. Earl implemented
+ the hypertext engine HYPERREZ in the Unix environment. HYPERREZ
+ was developed by Niel Larson of Think.com and served as the model
+ for the early versions of <strong>Lynx</strong> which did not use
+ the WWW libraries and had their own hypertext format.</p>
+
+ <h2><a name="availability" id="availability">Availability</a></h2>
+
+ <p>Information on obtaining the most current version of
+ <strong>Lynx</strong> is available via the <a href=
+ "https://lynx.invisible-island.net">Lynx homepage</a>.</p>
+
+ <h2><a name="lynx-dev_list" id="lynx-dev_list">Mailing List</a></h2>
+
+ <p>We have a mailing list for <strong>Lynx</strong> development
+ discussion. If you are interested in joining the list, follow
+ this <a href="lynx-dev.html">link</a>. There also are links to
+ <a href=
+ "http://mail.gnu.org/mailman/listinfo/lynx-dev/">archives</a> in
+ html format for this mailing list.</p>
+</body>
+</html>
diff --git a/lynx_help/help_files.txt b/lynx_help/help_files.txt
new file mode 100644
index 0000000..326ddbd
--- /dev/null
+++ b/lynx_help/help_files.txt
@@ -0,0 +1,38 @@
+# $LynxId: help_files.txt,v 1.12 2012/01/31 10:52:22 tom Exp $
+#
+# Format:
+# KEYWORD=<filename>.html
+# No space is allowed.
+#
+# Usage:
+# ... href="@KEYWORD@">whatever keyword says</a>
+# ... href="@KEYWORD@#section>...</a>
+# ... href="../@KEYWORD#section>...</a>
+#
+# Help files which are used in Lynx's help directory.
+# Each filename has to end with '.html' otherwise install-help will fail.
+#
+ABOUT_LYNX=about_lynx.html
+ALT_EDIT_HELP=alt_edit_help.html
+BASHLIKE_EDIT_HELP=bashlike_edit_help.html
+BOOKMARK_HELP=bookmark_help.html
+COOKIE_HELP=cookie_help.html
+DIRED_HELP=dired_help.html
+EDIT_HELP=edit_help.html
+ENVIRONMENTS=environments.html
+FOLLOW_HELP=follow_help.html
+GOPHER_TYPES_HELP=gopher_types_help.html
+HISTORY_HELP=history_help.html
+KEYSTROKE_HELP=keystroke_help.html
+LYNX_HELP_MAIN=lynx_help_main.html
+LYNX_URL_SUPPORT=lynx_url_support.html
+LYNX_USERS_GUIDE=Lynx_users_guide.html
+MOVEMENT_HELP=movement_help.html
+OPTION_HELP=option_help.html
+OTHER_HELP=other_help.html
+PRINT_HELP=print_help.html
+SCROLLING_HELP=scrolling_help.html
+TEST_DISPLAY=test_display.html
+VISITED_HELP=visited_help.html
+XTERM_HELP=xterm_help.html
+LYNX_DEV=lynx-dev.html
diff --git a/lynx_help/keystrokes/alt_edit_help.html b/lynx_help/keystrokes/alt_edit_help.html
new file mode 100644
index 0000000..63f1044
--- /dev/null
+++ b/lynx_help/keystrokes/alt_edit_help.html
@@ -0,0 +1,128 @@
+<!-- $LynxId: alt_edit_help.html,v 1.21 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Lynx Line Editor Alternative Key Binding</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <link rel="Sibling" title="Default Binding" href=
+ "edit_help.html">
+ <link rel="Sibling" title="Bash-Like Binding" href=
+ "bashlike_edit_help.html">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Describes an alternative set of line editor bindings for Lynx. This is one of the alternate bindings normally compiled-in">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#alternate_bindings">Table of key-bindings</a></li>
+
+ <li><a href="#notes">Notes</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p><strong>Lynx</strong> invokes a built-in <a href=
+ "edit_help.html">Line Editor</a> for entering strings in response
+ to prompts, in forms, and for email messages if an external
+ editor has not been defined. Additional alternative key-bindings
+ can be offered by configuring with
+ <code>--enable-alt-bindings</code> or by adding them in
+ LYEditmap.c before compiling <strong>Lynx</strong>. If available,
+ they may be selected via the &ldquo;o&rdquo;ptions menu, or by
+ editing lineedit_mode in the &ldquo;.lynxrc&rdquo; file.</p>
+
+ <p><strong><em>Note:</em></strong> setting emacs/vi keys ON has
+ no direct effect on line-editor bindings.</p>
+
+ <h2><a name="alternate_bindings" id="alternate_bindings">Table of
+ key-bindings</a></h2>
+
+ <p>This is the <em>Alternative Binding</em> keymap.</p>
+
+ <pre>
+ ENTER Input complete - RETURN
+ TAB Input complete - TAB, Do
+ ABORT Input cancelled - Ctrl-G, Ctrl-O, (Ctrl-C on some systems)
+ ERASE Erase the line - Ctrl-U
+
+ BACK Cursor back char - Left-Arrow, Ctrl-B
+ FORW Cursor forward char - Right-Arrow, Ctrl-F
+ BACKW Cursor back word - Ctrl-P
+ FORWW Cursor forward word - Ctrl-N
+ BOL Go to begin of line - Ctrl-A, Home, Find
+ EOL Go to end of line - Ctrl-E, End, Select
+
+ DELP Delete prev char - Backspace, Delete, Remove
+ DELN Delete next char - Ctrl-D (<em><a href=
+"#note_1">see note 1</a></em>)
+ DELPW Delete prev word - Ctrl-R
+ DELNW Delete next word - Ctrl-T
+ DELEL Delete to end of line - Ctrl-K
+
+ UPPER Upper case the line - Ctrl-^
+ LOWER Lower case the line - Ctrl-_
+
+ LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) (<em><a href="#note_2">see note 2</a></em>)
+
+<a name="TASpecial" id=
+"TASpecial">Special commands for use only in textarea fields</a> (<em><a href="#note_3">see note 3</a></em>):
+
+ Textarea external edit - Ctrl-X e
+ Insert file in textarea - Ctrl-X i
+ Grow textarea - Ctrl-X g
+</pre>
+ <h2><a name="emacs_bindings" id="emacs_bindings">Emacs-like
+ commands</a></h2>
+
+ <pre>
+ TPOS Transpose characters - Ctrl-t
+ SETMARK Set mark at current position in line - Ctrl-@
+ XPMARK Exchange current position with mark - Ctrl-x Ctrl-x
+ KILLREG Kill region between mark and position - Ctrl-x Ctrl-w (<em><a href="#note_3">see note 3</a></em>)
+ YANK Insert text last killed (with KILLREG) - Ctrl-y
+</pre>
+ <h2><a name="examples" id="examples">Try it yourself</a></h2>
+
+ <p>Here is a little textarea for practice:</p>
+
+ <form action="">
+ <p>
+ <textarea name="practice" cols="40" rows=
+ "5">This text cannot be submitted. Normally lines like
+these would be part of a form that is filled out and
+then submitted. You can move around here and delete
+or add text as you like, using the Line-Editor keys.
+</textarea><input type="reset" value="[reset content]">
+ </p>
+ </form>
+
+ <h2><a name="special_keys" id="special_keys">Special keys</a></h2>
+
+ <p>See the <em><a href="edit_help.html#special_keys">Lynx Line
+ Editor</a></em> page for an explanation of terminology and
+ key-names.</p>
+
+ <h2><a name="notes" id="notes">Notes</a></h2>
+
+ <ol>
+ <li id="note_1">"next" means the character "under" a box or
+ underline style cursor; it means "to the immediate right of" an
+ I-beam (between characters) type cursor.</li>
+
+ <li id="note_2">Follow Ctrl-V with any recognized key command,
+ to "escape" from a text input field.</li>
+
+ <li id="note_3">For other key combinations using Ctrl-X as a
+ prefix key, see the Help page for the <a rel="Sibling" title=
+ "Bash-Like Binding" href=
+ "bashlike_edit_help.html">Bash-Like</a> Binding.</li>
+ </ol>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/bashlike_edit_help.html b/lynx_help/keystrokes/bashlike_edit_help.html
new file mode 100644
index 0000000..621e3e0
--- /dev/null
+++ b/lynx_help/keystrokes/bashlike_edit_help.html
@@ -0,0 +1,277 @@
+<!-- $LynxId: bashlike_edit_help.html,v 1.22 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Lynx Line Editor Bash-Like Key Binding</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <link rel="Sibling" title="Default Binding" href=
+ "edit_help.html">
+ <link rel="Sibling" title="Alternative Binding" href=
+ "alt_edit_help.html">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Describes the bash-like line editor bindings for Lynx. This is one of the alternate bindings normally compiled-in">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#bash_bindings">Bash-like bindings</a></li>
+
+ <li><a href="#examples">Try it yourself</a></li>
+
+ <li><a href="#emacs_bindings">Emacs-like commands</a></li>
+
+ <li><a href="#special_keys">Comments on special keys</a></li>
+
+ <li><a href="#notes">Notes</a></li>
+
+ <li><a href="#miscellaneous">Additional details</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p><strong>Lynx</strong> invokes a built-in <a href=
+ "edit_help.html">Line Editor</a> for entering strings in response
+ to prompts, in forms, and for email messages if an external
+ editor has not been defined. Alternative key bindings are
+ normally available (unless <strong>Lynx</strong> was configured
+ with <code>--disable-alt-bindings</code>). If available, they may
+ be selected via the &ldquo;o&rdquo;ptions menu, or by editing
+ lineedit_mode in the &ldquo;.lynxrc&rdquo; file.</p>
+
+ <p>You can always see the current set of key-bindings in
+ <strong>Lynx</strong> by opening the special URL <a href=
+ "LYNXEDITMAP:">LYNXEDITMAP:</a>. This page is provided for those
+ not using Lynx.</p>
+
+ <p><strong><em>Note:</em></strong> setting emacs/vi keys ON has
+ no direct effect on line-editor bindings.</p>
+
+ <h2><a name="bash_bindings" id="bash_bindings">Bash-like
+ bindings</a></h2>
+
+ <p>This is the <em>Bash-like Binding</em> keymap.</p>
+
+ <pre>
+ ENTER Input complete - Enter, RETURN
+ TAB Completion / Next - TAB, Do (<em><a href=
+"#note_2">see note 2</a></em>)
+ ABORT Cancel / Undo Change - Ctrl-g, Ctrl-_
+ ERASE Erase the line - M-k, Ctrl-x k
+
+ BACK Cursor back char - Left-Arrow, Ctrl-b
+ FORW Cursor forward char - Right-Arrow, Ctrl-f
+ BACKW Cursor back word - M-b, Ctrl-r
+ FORWW Cursor forward word - M-f, Ctrl-s (<em><a href=
+"#note_5">see note 5</a></em>)
+ BOL Go to begin of line - Ctrl-a, Home, Find
+ EOL Go to end of line - Ctrl-e, End, Select (<em><a href="#note_4">see note 4</a></em>)
+
+ DELP Delete prev char - Backspace
+ DELN Delete next char - Ctrl-d, Delete, Remove (<em><a href="#note_1">see note 1</a></em>)
+ DELPW Delete prev word - Ctrl-w, M-Backspace, M-Delete (<em><a href="#note_3">see note 3</a></em>)
+ DELNW Delete next word - M-d
+ DELBL Delete to beg of line - Ctrl-u
+ DELEL Delete to end of line - Ctrl-k (<em><a href=
+"#note_4">see note 4</a></em>)
+
+ UPPER Upper case the line - M-u
+ LOWER Lower case the line - M-l
+
+ LKCMD Invoke cmd prompt - Ctrl-v [FORM] (<em><a href=
+"#note_6">see note 6</a></em>)
+ SWMAP Switch input keymap - Ctrl-^ (if compiled in)
+
+<a name="TASpecial" id=
+"TASpecial">Special commands for use in textarea fields</a> [FORM]:
+
+ PASS! Textarea external edit - Ctrl-e Ctrl-e, Ctrl-x e (<em><a href="#note_4">see note 4</a></em>)
+ PASS! Insert file in textarea - Ctrl-x i
+ PASS! Grow textarea - Ctrl-x g
+</pre>
+ <h2><a name="examples" id="examples">Try it yourself</a></h2>
+
+ <p>Here is a little textarea for practice:</p>
+
+ <form action="">
+ <p>
+ <textarea name="practice" cols="40" rows=
+ "5">This text cannot be submitted. Normally lines like
+these would be part of a form that is filled out and
+then submitted. You can move around here and delete
+or add text as you like, using the Line-Editor keys.
+</textarea><input type="reset" value="[reset content]">
+ </p>
+ </form>
+
+ <h2><a name="emacs_bindings" id="emacs_bindings">Emacs-like
+ commands</a></h2>
+
+ <pre>
+ TPOS Transpose characters - Ctrl-t
+ SETMARK Set mark at current position in line - Ctrl-@
+ XPMARK Exchange current position with mark - Ctrl-x Ctrl-x
+ KILLREG Kill region between mark and position - Ctrl-x Ctrl-w (<em><a href="#note_3">see note 3</a></em>)
+ YANK Insert text last killed (with KILLREG) - Ctrl-y
+</pre>
+ <h2><a name="special_keys" id="special_keys">Special keys</a></h2>
+
+ <p>See the <em><a href="edit_help.html#special_keys">Lynx Line
+ Editor</a></em> page for an explanation of terminology and
+ key-names.</p>
+
+ <h2><a name="notes" id="notes">Notes</a></h2>
+
+ <ol>
+ <li id="note_1">"next" means the character "under" a box or
+ underline style cursor; it means "to the immediate right of" an
+ I-beam (between characters) type cursor.</li>
+
+ <li id="note_2">For entering strings in response to prompts
+ (that is, when not editing form text fields), some keys have
+ different actions: TAB tries to complete input based on
+ previous response; Up-Arrow and Down-Arrow may offer previous
+ response and next response, respectively, from recall buffer
+ for some prompts.</li>
+
+ <li id="note_3">Ctrl-w can only be used for editing functions
+ if its default KEYMAP to REFRESH is changed. This can be done
+ in the lynx.cfg file, for example with the line
+ "KEYMAP:^W:DO_NOTHING". This also applies for other keys: as
+ long as the key's action is mapped to REFRESH, either with an
+ explicit KEYMAP in lynx.cfg or by default, the key's Line
+ Editor binding is disabled.</li>
+
+ <li id="note_4">These keys invoke special behavior when pressed
+ twice in a row: Ctrl-e Ctrl-e calls the external editor for
+ changing the text in a textarea (if available). Ctrl-k Ctrl-k
+ will move to the next link, so that all lines in a textarea can
+ be conveniently cleared by repeating Ctrl-k.</li>
+
+ <li id="note_5">Key is likely unavailable for
+ <strong>Lynx</strong>, because it is interpreted by operating
+ system, comm program, or curses library, or swallowed as part
+ of escape sequence recognition. Binding is provided for the
+ benefit of those where this does not apply.</li>
+
+ <li id="note_6">where <strong>[FORM]</strong> is marked,
+ indicates that the binding is effective only in form text
+ fields. It is ignored by Line Editor elsewhere.</li>
+ </ol>
+
+ <p>When a text input field, including a textarea line, is
+ selected, the Line Editor functions get a first grab at the keys
+ entered. If a key has no function defined in the Line Editor
+ binding, it can either be ignored, or passed on for normal key
+ command handling, where modifiers like Ctrl-x or Meta currently
+ have no effect (see the <a href="LYNXKEYMAP:">Key Map Page</a>
+ accessible with the key <kbd>K</kbd> for current
+ information).</p>
+
+ <h2><a name="miscellaneous" id="miscellaneous">Additional
+ details</a></h2>
+
+ <p>Here are some additional details on other keys, for the
+ curious (very much subject to change)</p>
+
+ <pre>
+Normal key action when used in form fields, subject to remapping
+with KEYMAP: [FORM (except Up-Arrow, Down-Arrow)]
+ Ctrl-l (<em><a href="#note_3">see note 3</a></em>)
+ Ctrl-o, Ctrl-z, Ctrl-\, Ctrl-] (<em><a href=
+"#note_5">see note 5</a></em>)
+ Ctrl-n [emacskey], Ctrl-p [emacskey]
+ Up-Arrow, Down-Arrow (<em><a href=
+"#note_2">see note 2</a></em>)
+ Page-Up, Page-Down, F1, Back-Tab
+
+Normal key command with Meta modifier ignored when used in form fields,
+subject to remapping with KEYMAP: [FORM (except Up-Arrow, Down-Arrow)]
+ M-Ctrl-l (<em><a href=
+"#note_3">see note 3</a></em>) M-Ctrl-o <a href="#no_meta">[!]</a>,
+ M-Ctrl-z, M-Ctrl-\, M-Ctrl-] (<em><a href=
+"#note_5">see note 5</a></em>)
+ M-Ctrl-u, M-/, M-n
+ M-Up-Arrow <a href=
+"#no_meta">[!]</a>, M-Down-Arrow <a href=
+"#no_meta">[!]</a> (<em><a href="#note_2">see note 2</a></em>)
+ M-Page-Up <a href=
+"#no_meta">[!]</a>, M-Page-Down <a href=
+"#no_meta">[!]</a>, M-Home, M-End
+
+Passed as specific command:
+ lynx action duplicates by default
+ ----------- ---------------------
+ M-Ctrl-d NEXT_LINK Down-Arrow
+ M-Ctrl-e EDITTEXTAREA Ctrl-e Ctrl-e
+ M-Ctrl-k LPOS_NEXT_LINK (none, Down-Arrow suggested)
+ M-e EDITTEXTAREA Ctrl-e Ctrl-e
+ M-g GROWTEXTAREA (none, Ctrl-v $ suggested?)
+ M-i INSERTFILE (none, Ctrl-v # suggested?)
+ M-&lt; HOME M-Home
+ M-&gt; END M-End
+ M-F1 DWIMHELP F1
+ M-Find WHEREIS Ctrl-v /
+ M-Select NEXT Ctrl-v n
+
+Duplicates function of other key(s):
+ edit action duplicates
+ ----------- ----------
+ M-Ctrl-b BACKW M-b, Ctrl-r
+ M-Ctrl-f FORWW M-f
+ M-Ctrl-n FORWW M-f
+ M-Ctrl-p BACKW M-b, Ctrl-r
+ M-Ctrl-r BACKW M-b, Ctrl-r
+ M-a BOL Ctrl-a, Home, ...
+
+Modifier ignored, and duplicates function of other key(s):
+ edit action duplicates
+ ----------- ----------
+ M-Ctrl-a BOL Ctrl-a, Home, ...
+ M-Ctrl-g ABORT Ctrl-g, ...
+ M-TAB TAB Ctrl-i <a href=
+"#no_meta">[!]</a>
+ M-Ctrl-j ENTER Ctrl-m, Ctrl-j, Enter / RETURN
+ M-RETURN ENTER Ctrl-m, Ctrl-j, Enter / RETURN
+ M-Ctrl-y YANK Ctrl-y <a href=
+"#no_meta">[!]</a>
+ M-Ctrl-^ SWMAP Ctrl-^ <a href=
+"#no_meta">[!]</a> (if compiled in)
+ M-Right-Arrow FORW Right-Arrow <a href=
+"#no_meta">[!]</a>, Ctrl-f
+ M-Left-Arrow BACK Left-Arrow <a href=
+"#no_meta">[!]</a>, Ctrl-b
+ M-Do TAB Ctrl-i <a href=
+"#no_meta">[!]</a>
+
+Key completely ignored:
+ Ctrl-q, Insert
+ M-Ctrl-q, M-Ctrl-s, M-Ctrl-t, M-Ctrl-v, M-ESC (<em><a href="#note_5">see note 5</a></em>)
+ M-Ctrl-@, M-Ctrl-_, M-Remove, M-Insert <a href=
+"#no_meta">[!]</a>
+
+Meta + other (mostly, printable character) keys:
+ Modifier ignored, or sequence swallowed (<em><a href=
+"#note_5">see note 5</a></em>).
+ M-@, M-E...M-Z, M-\, M-^, M-_ attempt to interpret
+ as 7-bit escape representation for character in 8-bit
+ control (C1) range if appropriate according to
+ Display Character Set.
+
+[emacskey] Normal key action subject to emacs_keys setting.
+
+<a name="no_meta" id=
+"no_meta">[!]</a> Action of key with Meta modifier follows action of key without
+ Meta. If you manage to enter the Meta key while Line-Editor
+ Binding is not set to Bash-Like, and the unmodified binding
+ is different from that listed here, M-&lt;<var>key</var>&gt; will act
+ like &lt;<var>key</var>&gt;.
+</pre>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/bookmark_help.html b/lynx_help/keystrokes/bookmark_help.html
new file mode 100644
index 0000000..87d8591
--- /dev/null
+++ b/lynx_help/keystrokes/bookmark_help.html
@@ -0,0 +1,58 @@
+<!-- $LynxId: bookmark_help.html,v 1.11 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Lynx Bookmark Help Summary</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Lynx stores Bookmark files on your local machine. You can update these from within Lynx, or with a text editor">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Bookmark files</a></li>
+
+ <li><a href="#internal_edit">Updating within Lynx</a></li>
+
+ <li><a href="#external_edit">Updating with a text editor</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Bookmark files</a></h2>
+
+ <p><strong>Lynx</strong> stores <em>Bookmark files</em> on your
+ local machine. You can update these from within
+ <strong>Lynx</strong>, or with a text editor:</p>
+
+ <h2><a name="internal_edit" id="internal_edit">Updating within
+ Lynx</a></h2>
+
+ <ul>
+ <li>The append feature, invoked by pressing an
+ &ldquo;<em>a</em>&rdquo; while viewing a document will add the
+ current document or the currently highlighted link to your
+ default <em>Bookmark file</em>, or to one you select if
+ multiple bookmarks are enabled.</li>
+
+ <li>The remove feature, invoked by pressing an
+ &ldquo;<em>r</em>&rdquo; when a <em>Bookmark file</em> is being
+ displayed, will remove the currently highlighted link.</li>
+
+ <li>You may set and modify the paths and names of your
+ <em>Bookmark files</em> and enable or disable multiple
+ bookmarks in the <a href="option_help.html">Options
+ Menu</a>.</li>
+ </ul>
+
+ <h2><a name="external_edit" id="external_edit">Updating with a
+ text editor</a></h2>
+
+ <p>Lynx stores its bookmarks as an HTML file, using an unordered
+ list (<em>UL</em> and <em>LI</em> tags). It expects the list
+ items to be one per line, without wrapping.</p>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/cookie_help.html b/lynx_help/keystrokes/cookie_help.html
new file mode 100644
index 0000000..80e01d6
--- /dev/null
+++ b/lynx_help/keystrokes/cookie_help.html
@@ -0,0 +1,76 @@
+<!-- $LynxId: cookie_help.html,v 1.12 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Help on the Cookie Jar Page</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Lynx provides a page show shows information about all of the unexpired cookies, including their fully qualified domain name, expiration time and name/value pairs.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#showing_cookies">Cookie Details Shown</a></li>
+
+ <li><a href="#removing_cookies">Removing Cookies</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p><strong>Lynx</strong>'s <em>Cookie Jar Page</em> displays all
+ of the unexpired cookies you have accumulated in the hypothetical
+ <em>Cookie Jar</em>. The cookies are obtained via
+ <em>Set-Cookie</em> MIME headers in replies from http servers,
+ and are used for <a href="../Lynx_users_guide.html#Cookies">State
+ Management</a> across successive requests to the servers.</p>
+
+ <p>The cookies are listed by <em>domain</em> (server's Fully
+ Qualified Domain Name, or site-identifying portion of the FQDN),
+ and in order of decreasing specificity (number of slash-separated
+ symbolic elements in the <em>path</em> attribute of the cookie).
+ When <strong>Lynx</strong> sends requests to an http server whose
+ address tail-matches a <em>domain</em> in the <em>Cookie
+ Jar</em>, all its cookies with a <em>path</em> which head-matches
+ the path in the URL for that request are included as a
+ <em>Cookie</em> MIME header. The &ldquo;allow&rdquo; setting for
+ accepting cookies from each domain (always, never, or via prompt)
+ also is indicated in the listing.</p>
+
+ <h2><a name="showing_cookies" id="showing_cookies">Cookie Details
+ Shown</a></h2>
+
+ <p>The listing also shows the <em>port</em> (normally 80) of the
+ URL for the request which caused the cookie to be sent, and
+ whether the <em>secure</em> flag is set for the cookie, in which
+ case it will be sent only via secure connections (presently, only
+ SSL). The <em>Maximum Gobble Date</em>, i.e., when the cookie is
+ intended to expire, also is indicated. Also, a server may change
+ the expiration date, or cause the cookie to be deleted, in its
+ replies to subsequent requests from <strong>Lynx</strong>. If the
+ server included any explanatory comments in its
+ <em>Set-Cookie</em> MIME headers, those also are displayed in the
+ listing.</p>
+
+ <h2><a name="removing_cookies" id="removing_cookies">Removing
+ Cookies</a></h2>
+
+ <p>The <em>domain</em>=value pairs, and each cookie's name=value,
+ are links in the listing. Activating a <em>domain</em>=value link
+ will invoke a prompt asking whether all cookies in that
+ <em>domain</em> should be <em>Gobbled</em> (deleted from the
+ <em>Cookie Jar</em>), and/or whether the <em>domain</em> entry
+ should be <em>Gobbled</em> if all of its cookies have been
+ <em>Gobbled</em>, or whether to change the &ldquo;allow&rdquo;
+ setting for that <em>domain</em>. Activating a cookie's
+ name=value link will cause that particular cookie to be
+ <em>Gobbled</em>. You will be prompted for confirmations of
+ deletions, to avoid any accidental <em>Gobbling</em>.</p>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/dired_help.html b/lynx_help/keystrokes/dired_help.html
new file mode 100644
index 0000000..f3e7e05
--- /dev/null
+++ b/lynx_help/keystrokes/dired_help.html
@@ -0,0 +1,90 @@
+<!-- $LynxId: dired_help.html,v 1.12 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Lynx Dired-mode Key Bindings</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Lynx's dired-mode allows you to browse for file-URLs. This describes the key-bindings for dired-mode.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#dired_bindings">Dired Key bindings</a></li>
+
+ <li><a href="#other_bindings">Other Key bindings</a></li>
+
+ <li><a href="#notes">Notes</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p><strong>Lynx</strong> changes into <em>Dired mode</em> when
+ you use a URL of the type <em>file://localhost/path/</em>.</p>
+
+ <h2><a name="dired_bindings" id="dired_bindings">Dired Key
+ bindings</a></h2>
+
+ <p>While in Dired mode, some keys are remapped to do the
+ following functions:</p>
+
+ <blockquote>
+ <pre>
+
+ C)reate - Create a new, empty file in the current
+ directory. You will be prompted to enter
+ a name for the file.
+
+ F)ull menu - Show a full menu of commands for currently
+ selected file or directory.
+
+ M)odify - Modify the name or location of selection. If
+ multiple files have been selected, you will
+ only be able to change the location. Choose
+ between changing the name or location and then
+ enter a new filename or path.
+
+ R)emove - Delete currently selected files.
+
+ T)ag - Tag the highlighted file. Multiple files may
+ be tagged and all other commands except "Create"
+ will be performed on tagged files instead of the
+ one highlighted. Press &ldquo;<em>t</em>&rdquo; again to untag
+ a file.
+
+ U)pload - Upload a file to the current directory using
+ one of the options listed in the upload screen.
+</pre>
+ </blockquote>
+
+ <h2><a name="other_bindings" id="other_bindings">Other Key
+ bindings</a></h2>
+
+ <p>Some other keys useful in <em>Dired mode</em>:</p>
+
+ <blockquote>
+ <pre>
+ D)ownload - Download selection using options listed in
+ the download options screen.
+
+ E)dit - Spawn the editor defined in the <a href=
+"option_help.html">Options Menu</a>
+ and load selection for editing.
+</pre>
+ </blockquote>
+
+ <h2><a name="notes" id="notes">Notes</a></h2>
+
+ <p><em>Dired mode</em> must be activated at compile time.
+ Otherwise, the above commands will not be available and
+ <strong>Lynx</strong> will treat a directory listing as an HTML
+ file.</p>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/edit_help.html b/lynx_help/keystrokes/edit_help.html
new file mode 100644
index 0000000..42d3e8a
--- /dev/null
+++ b/lynx_help/keystrokes/edit_help.html
@@ -0,0 +1,191 @@
+<!-- $LynxId: edit_help.html,v 1.30 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Lynx Line Editor Default Key Binding</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Describes Lynx's built-in line-editor, when it is used, and the keys used for the default binding. There are alternate and special bindings.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#regular_keymap">Regular Keymap</a></li>
+
+ <li><a href="#editing_keymap">Editing Keymap</a></li>
+
+ <li><a href="#examples">Try it yourself</a></li>
+
+ <li><a href="#notes">Notes</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p><strong>Lynx</strong> invokes a built-in <em>Line Editor</em>
+ for entering strings in response to prompts, in forms, and for
+ email messages if an external editor has not been defined.
+ Alternative key bindings are normally available (unless
+ <strong>Lynx</strong> was configured with
+ <code>--disable-alt-bindings</code>). If available, they may be
+ selected via the &ldquo;o&rdquo;ptions menu, or by editing
+ lineedit_mode in the &ldquo;.lynxrc&rdquo; file.</p>
+
+ <p>Two such alternative key bindings, which may be available on
+ your system, are the</p>
+
+ <ul>
+ <li><a href="alt_edit_help.html">Alternative Binding</a> keymap
+ and the</li>
+
+ <li><a href="bashlike_edit_help.html">Bash-like Binding</a>
+ keymap.</li>
+ </ul>
+
+ <p>You can always see the current set of key-bindings in
+ <strong>Lynx</strong> by opening the special URL <a href=
+ "LYNXEDITMAP:">LYNXEDITMAP:</a>. This page is provided for those
+ not using Lynx.</p>
+
+ <p><strong><em>Note:</em></strong> setting emacs/vi keys ON has
+ no effect on line-editor bindings.</p>
+
+ <h2><a name="regular_keymap" id="regular_keymap">Regular
+ Keymap</a></h2>
+
+ <p>This is the <em>Default Binding</em> keymap:</p>
+
+ <pre>
+ ENTER Input complete - RETURN
+ TAB Input complete - TAB, Do
+ ABORT Input cancelled - Ctrl-G, Ctrl-O, (Ctrl-C on some systems)
+ ERASE Erase the line - Ctrl-U
+
+ BACK Cursor back char - Left-Arrow
+ FORW Cursor forward char - Right-Arrow
+ BACKW Cursor back word - Ctrl-P
+ FORWW Cursor forward word - Ctrl-N
+ BOL Go to begin of line - Ctrl-A, Home, Find
+ EOL Go to end of line - Ctrl-E, End, Select
+
+ DELP Delete prev char - Backspace, Delete, Remove
+ DELN Delete next char - Ctrl-D, Ctrl-R (<em><a href=
+"#note_1">see note 1</a></em>)
+ DELPW Delete prev word - Ctrl-B
+ DELNW Delete next word - Ctrl-F
+ DELEL Delete to end of line - Ctrl-_
+
+ UPPER Upper case the line - Ctrl-T
+ LOWER Lower case the line - Ctrl-K
+
+ LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) (<em><a href="#note_2">see note 2</a></em>)
+ SWMAP Switch input keymap - Ctrl-^ (if compiled in)
+</pre>
+ <h2><a name="editing_keymap" id="editing_keymap">Editing
+ Keymap</a></h2>
+
+ <p><a name="TASpecial" id="TASpecial">These are special commands
+ for use only in textarea fields</a> (<em><a href="#note_3">see
+ note 3</a></em>):</p>
+
+ <pre>
+ Textarea external edit - Ctrl-X e
+ Insert file in textarea - Ctrl-X i
+ Grow textarea - Ctrl-X g
+</pre>
+ <h2><a name="emacs_bindings" id="emacs_bindings">Emacs-like
+ commands</a></h2>
+
+ <pre>
+ TPOS Transpose characters - Ctrl-t
+ SETMARK Set mark at current position in line - Ctrl-@
+ XPMARK Exchange current position with mark - Ctrl-x Ctrl-x
+ KILLREG Kill region between mark and position - Ctrl-x Ctrl-w (<em><a href="#note_3">see note 3</a></em>)
+ YANK Insert text last killed (with KILLREG) - Ctrl-y
+</pre>
+ <h2><a name="examples" id="examples">Try it yourself</a></h2>
+
+ <p>Here is a little textarea for practice:</p>
+
+ <form action="">
+ <p>
+ <textarea name="practice" cols="40" rows=
+ "5">This text cannot be submitted. Normally lines like
+these would be part of a form that is filled out and
+then submitted. You can move around here and delete
+or add text as you like, using the Line-Editor keys.
+</textarea><input type="reset" value="[reset content]">
+ </p>
+ </form>
+
+ <h2><a name="special_keys" id="special_keys">Special keys</a></h2>
+
+ <p><samp><dfn>Ctrl-</dfn><strong>key</strong> means
+ Control+<strong><kbd>key</kbd></strong>.
+ <dfn><code>Ctrl-x</code></dfn> <strong>key</strong> means first
+ Control+<kbd>x</kbd>, then <strong><kbd>key</kbd></strong>.
+ <dfn>M-</dfn>key means Meta+<strong><kbd>key</kbd></strong>,
+ where Meta is a modifier that can be entered in a variety of
+ ways:</samp>
+ </p>
+
+ <ul>
+ <li>First ESC, then the <strong><kbd>key</kbd></strong>. This
+ does not work with all systems or on all connections, and if it
+ does may not work for some keys (because the ESC character is
+ also part of code sequences for "normal" function keys).</li>
+
+ <li>Alt+<strong><kbd>key</kbd></strong>. This works if the
+ terminal, console, or comm program is set up to interpret Alt
+ as a modifier to send ESC. The Linux console acts like that by
+ default for most keys; Kermit can be set up to do it, xterm can
+ be for some keys, and so on. But the same caveats as for the
+ previous item apply. This Alt mapping may also be possible,
+ independent of the ESC character, for some keys in
+ <strong>Lynx</strong> for DOS/i386 or for Win32.</li>
+
+ <li>Ctrl-x <strong><kbd>key</kbd></strong>. Actually, currently
+ the same internal table is used for Meta and the Ctrl-x prefix.
+ Therefore all M-<strong><kbd>key</kbd></strong> combinations
+ can also be typed as Ctrl-x <strong><kbd>key</kbd></strong>,
+ and vice versa.</li>
+ </ul>
+
+ <p>A few key names may be less familiar now than when
+ <strong>Lynx</strong> was first written: <em>Find</em>,
+ <em>Select</em> and <em>Remove</em>. The <a href=
+ "https://invisible-island.net/xterm/xterm.faq.html#xterm_keypad">XTerm
+ FAQ</a> shows some typical keypad layouts of emulators for VT220
+ and other DEC terminals.</p>
+
+ <p>The VT220 did not have a &ldquo;backspace&rdquo; key but
+ <strong>Lynx</strong>'s default bindings mention it. Both ASCII
+ <samp>BS</samp> (backspace) and <samp>DEL</samp> are bound by
+ default to the same functions. <samp>DEL</samp> (occasionally
+ referred to as <samp>RUBOUT</samp>) is not the same as
+ <samp>Delete</samp>: the former is a single character while the
+ latter is usually a sequence of characters.</p>
+
+ <h2><a name="notes" id="notes">Notes</a></h2>
+
+ <ol>
+ <li id="note_1">"next" means the character "under" a box or
+ underline style cursor; it means "to the immediate right of" an
+ I-beam (between characters) type cursor.</li>
+
+ <li id="note_2">Follow Ctrl-V with any recognized key command,
+ to "escape" from a text input field.</li>
+
+ <li id="note_3">For other key combinations using Ctrl-X as a
+ prefix key, see the Help page for the <a rel="Sibling" title=
+ "Bash-Like Binding" href=
+ "bashlike_edit_help.html">Bash-Like</a> Binding.</li>
+ </ol>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/environments.html b/lynx_help/keystrokes/environments.html
new file mode 100644
index 0000000..1d7245a
--- /dev/null
+++ b/lynx_help/keystrokes/environments.html
@@ -0,0 +1,558 @@
+<!-- $LynxId: environments.html,v 1.22 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Help on Lynx's Environment variables</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Describes environment variables used by Lynx. Some are specific to Lynx, others are common with similar programs.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Environment Variables</a></li>
+
+ <li><a href="#env">Variables Used By Lynx</a></li>
+
+ <li><a href="#setenv">Variables Set or Modified By Lynx</a></li>
+
+ <li><a href="#cgi">Simulated CGI Support</a></li>
+
+ <li><a href="#language">Native Language Support</a></li>
+
+ <li><a href="#proxy">Proxy details and examples</a></li>
+
+ <li><a href="#dos">Win32 (95/NT) and 386 DOS</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Environment Variables</a></h2>
+
+ <pre>
+ In addition to various &ldquo;standard&rdquo; environment variables
+ such as HOME, PATH, USER, DISPLAY, TMPDIR, etc, <strong>Lynx</strong> utilizes
+ several <strong>Lynx</strong>-specific environment variables, <a href="#env">if they exist</a>.
+
+ Others may be created or modified by <strong>Lynx</strong> to pass data to
+ an external program, or for other reasons. These are
+ listed separately <a href="#setenv">below</a>.
+
+ See also the sections on <a href=
+"#cgi">Simulated CGI Support</a> and
+ <a href="#language">Native Language Support</a>, below.
+
+ Note: Not all environment variables apply to all types of
+ platforms supported by <strong>Lynx</strong>, though most do. Feedback on
+ platform dependencies is solicited. See also <a href=
+"#dos">win32/dos</a> specific
+ variables.
+</pre>
+ <h2><a name="env" id="env">Variables Used By Lynx</a></h2>
+
+ <pre>
+ COLORTERM
+ If set, color capability for the terminal
+ is forced on at startup time. The actual
+ value assigned to the variable is ignored.
+ This variable is only meaningful if <strong>Lynx</strong>
+ was built using the slang screen-handling
+ library.
+
+ LYNX_CFG
+ This variable, if set, will override
+ the default location and name of the
+ global configuration file (normally,
+ lynx.cfg) that was defined by the
+ LYNX_CFG_FILE constant in the
+ userdefs.h file, during installation.
+ See the userdefs.h file for more
+ information.
+
+ LYNX_HELPFILE
+ If set, this variable overrides the
+ compiled-in URL and configuration file
+ URL for the <strong>Lynx</strong> help file.
+
+ LYNX_LOCALEDIR
+ If set, this variable overrides the
+ compiled-in location of the locale
+ directory which contains native lan-
+ guage (NLS) message text.
+
+ LYNX_LSS
+ This variable, if set, specifies the
+ location of the default <strong>Lynx</strong> character
+ style sheet file. [Currently only
+ meaningful if <strong>Lynx</strong> was built using
+ experimental color style support.]
+
+ LYNX_SAVE_SPACE
+ This variable, if set, will override
+ the default path prefix for files
+ saved to disk that is defined in the
+ lynx.cfg SAVE_SPACE: statement. See
+ the lynx.cfg file for more information.
+
+ LYNX_TEMP_SPACE
+ This variable, if set, will override
+ the default path prefix for temporary
+ files that was defined during installation,
+ as well as any value that may
+ be assigned to the TMPDIR variable.
+
+ LYNX_TRACE
+ If set, causes <strong>Lynx</strong> to write a trace
+ file as if the -trace option were sup-
+ plied.
+
+ LYNX_TRACE_FILE
+ If set, overrides the compiled-in name
+ of the trace file, which is either
+ Lynx.trace or LY-TRACE.LOG (the latter
+ on the DOS platform). The trace file
+ is in either case relative to the home
+ directory.
+
+ MAIL
+ This variable specifies the default
+ inbox <strong>Lynx</strong> will check for new mail, if
+ such checking is enabled in the
+ lynx.cfg file.
+
+ NEWS_ORGANIZATION
+ This variable, if set, provides the
+ string used in the Organization:
+ header of USENET news postings. It will
+ override the setting of the ORGANIZATION
+ environment variable, if it is also set
+ (and, on UNIX, the contents of an
+ /etc/organization file, if present).
+
+ NNTPSERVER
+ If set, this variable specifies the
+ default NNTP server that will be used
+ for USENET news reading and posting
+ with <strong>Lynx</strong>, via news: URL's.
+
+ ORGANIZATION
+ This variable, if set, provides the
+ string used in the Organization:
+ header of USENET news postings. On
+ UNIX, it will override the contents of
+ an /etc/organization file, if present.
+
+ <em>PROTOCOL</em>_proxy
+ <strong>Lynx</strong> supports the use of proxy servers
+ that can act as firewall gateways and
+ caching servers. They are preferable
+ to the older gateway servers (see
+ WWW_access_GATEWAY, below).
+ Each protocol used by <strong>Lynx</strong> (http, ftp,
+ gopher, etc), can be mapped separately
+ by setting environment variables of
+ the form <em>PROTOCOL</em>_proxy (literally:
+ http_proxy, ftp_proxy, gopher_proxy,
+ etc), to &ldquo;http://some.server.dom:port/&rdquo;.
+ See <a href=
+"#proxy">Proxy details and examples</a>.
+
+ WWW_<em>access</em>_GATEWAY
+ <strong>Lynx</strong> still supports use of gateway
+ servers, with the servers specified
+ via &ldquo;WWW_<em>access</em>_GATEWAY&rdquo; variables
+ (where &ldquo;access&rdquo; is lower case and can
+ be &ldquo;http&rdquo;, &ldquo;ftp&rdquo;, &ldquo;gopher&rdquo; or &ldquo;wais&rdquo;),
+ however most gateway servers have been
+ discontinued. Note that you do not
+ include a terminal &ldquo;/&rdquo; for gateways,
+ but do for proxies specified by <em>PROTOCOL</em>_proxy
+ environment variables. See <a href=
+"#proxy">Proxy details</a>.
+
+ WWW_HOME
+ This variable, if set, will override
+ the default startup URL specified in
+ any of the <strong>Lynx</strong> configuration files.
+</pre>
+ <h2><a name="setenv" id="setenv">Variables Set or Modified By
+ Lynx</a></h2>
+
+ <pre>
+ LYNX_PRINT_DATE This variable is set by the <strong>Lynx</strong>
+ p(rint) function, to the &ldquo;Date:&rdquo; string
+ seen in the document's &ldquo;Information
+ about&rdquo; page (= cmd), if any. It is
+ created for use by an external program,
+ as defined in a lynx.cfg
+ PRINTER: definition statement. If the
+ field does not exist for the document,
+ the variable is set to a null string
+ under UNIX, or &ldquo;No Date&rdquo; under VMS.
+
+ LYNX_PRINT_LASTMOD This variable is set by the <strong>Lynx</strong>
+ p(rint) function, to the Last Mod:
+ string seen in the document's &ldquo;Information
+ about&rdquo; page (= cmd), if any.
+ It is created for use by an external
+ program, as defined in a lynx.cfg
+ PRINTER: definition statement. If the
+ field does not exist for the document,
+ the variable is set to a null string
+ under UNIX, or &ldquo;No LastMod&rdquo; under VMS.
+
+ LYNX_PRINT_TITLE This variable is set by the <strong>Lynx</strong>
+ p(rint) function, to the Linkname:
+ string seen in the document's &ldquo;Information
+ about&rdquo; page (= cmd), if any.
+ It is created for use by an external
+ program, as defined in a lynx.cfg
+ PRINTER: definition statement. If the
+ field does not exist for the document,
+ the variable is set to a null string
+ under UNIX, or &ldquo;No Title&rdquo; under VMS.
+
+ LYNX_PRINT_URL This variable is set by the <strong>Lynx</strong>
+ p(rint) function, to the URL: string
+ seen in the document's &ldquo;Information
+ about&rdquo; page (= cmd), if any. It is
+ created for use by an external program,
+ as defined in a lynx.cfg
+ PRINTER: definition statement. If the
+ field does not exist for the document,
+ the variable is set to a null string
+ under UNIX, or &ldquo;No URL&rdquo; under VMS.
+
+ LYNX_VERSION This variable is always set by <strong>Lynx</strong>,
+ and may be used by an external program
+ to determine if it was invoked by
+ <strong>Lynx</strong>. See also the comments in the
+ distribution's sample mailcap file,
+ for notes on usage in such a file.
+
+ SSL_CERT_DIR Set to the directory containing trusted
+ certificates.
+
+ SSL_CERT_FILE Set to the full path and filename for
+ your file of trusted certificates.
+
+ TERM Normally, this variable is used by
+ <strong>Lynx</strong> to determine the terminal type
+ being used to invoke <strong>Lynx</strong>. If, however,
+ it is unset at startup time (or
+ has the value &ldquo;unknown&rdquo;), or if the
+ -term command-line option is used,
+ <strong>Lynx</strong> will set or modify its value
+ to the user specified terminal type
+ (for the <strong>Lynx</strong> execution environment).
+ Note: If set/modified by <strong>Lynx</strong>, the values of
+ the LINES and/or COLUMNS environment
+ variables may also be changed.
+</pre>
+ <h2><a name="cgi" id="cgi">Simulated CGI Support</a></h2>
+
+ <p>If built with the cgi-links option enabled,
+ <strong>Lynx</strong> allows access to a cgi script directly
+ without the need for an http daemon.</p>
+
+ <p>When executing such &ldquo;lynxcgi scripts&rdquo; (if
+ enabled), the following variables may be set for simulating a CGI
+ environment:</p>
+
+ <pre>
+ CONTENT_LENGTH
+
+ CONTENT_TYPE
+
+ DOCUMENT_ROOT
+
+ HTTP_ACCEPT_CHARSET
+
+ HTTP_ACCEPT_LANGUAGE
+
+ HTTP_USER_AGENT
+
+ PATH_INFO
+
+ PATH_TRANSLATED
+
+ QUERY_STRING
+
+ REMOTE_ADDR
+
+ REMOTE_HOST
+
+ REQUEST_METHOD
+
+ SERVER_SOFTWARE
+</pre>
+ <p>Other environment variables are not inherited by the script,
+ unless they are provided via a LYNXCGI_ENVIRONMENT statement in
+ the configuration file. See the lynx.cfg file, and the (draft)
+ CGI 1.1 Specification
+ &lt;http://Web.Golux.Com/coar/cgi/draft-coar-cgi-v11-00.txt&gt;
+ for the definition and usage of these variables.</p>
+
+ <p>The CGI Specification, and other associated documentation,
+ should be consulted for general information on CGI script
+ programming.</p>
+
+ <h2><a name="language" id="language">Native Language Support</a></h2>
+
+ <p>If configured and installed with Native Language Support,
+ <strong>Lynx</strong> will display status and other messages in
+ your local language. See the file ABOUT_NLS in the source
+ distribution, or at your local GNU site, for more information
+ about internationalization.</p>
+
+ <p>The following environment variables may be used to alter
+ default settings:</p>
+
+ <pre>
+ LANG This variable, if set, will override
+ the default message language. It is
+ an ISO 639 two-letter code identifying
+ the language. Language codes are NOT
+ the same as the country codes given in
+ ISO 3166.
+
+ LANGUAGE This variable, if set, will override
+ the default message language. This is a
+ GNU extension that has higher priority for
+ setting the message catalog than LANG or
+ LC_ALL.
+
+ LC_ALL and
+
+ LC_MESSAGES These variables, if set, specify the
+ notion of native language formatting
+ style. They are POSIXly correct.
+
+ LINGUAS This variable, if set prior to configuration,
+ limits the installed languages to specific values.
+ It is a space-separated list of two-letter codes.
+ Currently, it is hard-coded to a wish list.
+
+ NLSPATH This variable, if set, is used as the
+ path prefix for message catalogs.
+</pre>
+ <h2><a name="proxy" id="proxy">Proxy details and examples</a></h2>
+
+ <p>To set your site's NTTP server as the default host for news
+ reading and posting via <strong>Lynx</strong>, set the
+ environment variable NNTPSERVER so that it points to its Internet
+ address. The variable &ldquo;NNTPSERVER&rdquo; is used to specify
+ the host which will be used as the default for news URLs.</p>
+
+ <dl>
+ <dt>UNIX</dt>
+
+ <dd>
+ <pre>
+setenv NNTPSERVER "news.server.dom"
+</pre>
+ </dd>
+
+ <dt>VMS</dt>
+
+ <dd>
+ <pre>
+define/system NNTPSERVER "news.server.dom"
+</pre>
+ </dd>
+ </dl>
+
+ <p><strong>Lynx</strong> still supports use of gateway servers,
+ with the servers specified via the variables
+ &ldquo;WWW_access_GATEWAY&rdquo;, where &ldquo;access&rdquo; is
+ lower case and can be &ldquo;http&rdquo;, &ldquo;ftp&rdquo;,
+ &ldquo;gopher&rdquo; or &ldquo;wais&rdquo;. Most of the gateway
+ servers have been discontinued, but
+ &ldquo;http://www.w3.org:8001&rdquo; is available for wais
+ searches (note that you do not include a terminal &ldquo;/&rdquo;
+ for gateways, but do for proxies; see below).</p>
+
+ <p><strong>Lynx</strong> version 2.2 and beyond supports the use
+ of proxy servers that can act as firewall gateways and caching
+ servers. They are preferable to the older gateway servers. Each
+ protocol used by <strong>Lynx</strong> can be mapped separately
+ using <em>PROTOCOL</em>_proxy environment variables as shown
+ below:</p>
+
+ <dl>
+ <dt>UNIX</dt>
+
+ <dd>
+ <blockquote>
+ <pre>
+setenv http_proxy "http://some.server.dom:port/"
+setenv https_proxy "http://some.server.dom:port/"
+setenv ftp_proxy "http://some.server.dom:port/"
+setenv gopher_proxy "http://some.server.dom:port/"
+setenv news_proxy "http://some.server.dom:port/"
+setenv newspost_proxy "http://some.server.dom:port/"
+setenv newsreply_proxy "http://some.server.dom:port/"
+setenv snews_proxy "http://some.server.dom:port/"
+setenv snewspost_proxy "http://some.server.dom:port/"
+setenv snewsreply_proxy "http://some.server.dom:port/"
+setenv nntp_proxy "http://some.server.dom:port/"
+setenv wais_proxy "http://some.server.dom:port/"
+setenv finger_proxy "http://some.server.dom:port/"
+setenv cso_proxy "http://some.server.dom:port/"
+</pre>
+ </blockquote>
+ </dd>
+
+ <dt>VMS</dt>
+
+ <dd>
+ <blockquote>
+ <pre>
+define "http_proxy" "http://some.server.dom:port/"
+define "https_proxy" "http://some.server.dom:port/"
+define "ftp_proxy" "http://some.server.dom:port/"
+define "gopher_proxy" "http://some.server.dom:port/"
+define "news_proxy" "http://some.server.dom:port/"
+define "newspost_proxy" "http://some.server.dom:port/"
+define "newsreply_proxy" "http://some.server.dom:port/"
+define "snews_proxy" "http://some.server.dom:port/"
+define "snewspost_proxy" "http://some.server.dom:port/"
+define "snewsreply_proxy" "http://some.server.dom:port/"
+define "nntp_proxy" "http://some.server.dom:port/"
+define "wais_proxy" "http://some.server.dom:port/"
+define "finger_proxy" "http://some.server.dom:port/"
+define "cso_proxy" "http://some.server.dom:port/"
+</pre>
+ </blockquote>
+
+ <p>(Encase *BOTH* strings in double-quotes to maintain lower
+ case for the <em>PROTOCOL</em>_proxy variable and for the
+ http access type; include /system if you want proxying for
+ all clients on your system.)</p>
+ </dd>
+ </dl>
+
+ <p>If you wish to override the use of a proxy server for specific
+ hosts or entire domains you may use the &ldquo;no_proxy&rdquo;
+ environment variable. The no_proxy variable can be a
+ comma-separated list of strings defining no-proxy zones in the
+ DNS domain name space. If a tail substring of the domain-path for
+ a host matches one of these strings, transactions with that node
+ will not be proxied. Here is an example use of
+ &ldquo;no_proxy&rdquo;:</p>
+
+ <dl>
+ <dt>UNIX</dt>
+
+ <dd>
+ <pre>
+setenv no_proxy "host.domain.dom, domain1.dom, domain2"
+</pre>
+ </dd>
+
+ <dt>VMS</dt>
+
+ <dd>
+ <pre>
+define "no_proxy" "host.domain.dom, domain1.dom, domain2"
+</pre>
+ </dd>
+ </dl>
+
+ <p>You can include a port number in the no_proxy list to override
+ use of a proxy server for the host accessed via that port, but
+ not via other ports. For example, if you use
+ &ldquo;host.domain.dom:119&rdquo; and/or
+ &ldquo;host.domain.dom:210&rdquo;, then news (port 119) URLs
+ and/or any wais (port 210) searches on that host would be
+ excluded, but http, ftp, and gopher services (if normally
+ proxied) would still be included, as would any news or wais
+ services on other hosts.</p>
+
+ <p>Warning: Note that setting &ldquo;il&rdquo; as an entry in
+ this list will block proxying for the .mil domain as well as the
+ .il domain. If the entry is &ldquo;.il&rdquo; this will not
+ happen.</p>
+
+ <p>If you wish to override the use of a proxy server completely
+ (i.e., globally override any existing proxy variables), set the
+ value of &ldquo;no_proxy&rdquo; to &ldquo;*&rdquo;. This is the
+ only allowed use of * in no_proxy.</p>
+
+ <p>Note that <strong>Lynx</strong> treats file URLs on the local
+ host as requests for direct access to the file, and does not
+ attempt ftp if that fails. It treats both ftp URLs and file URLs
+ on remote hosts as ftp URLs, and does not attempt direct file
+ access for either. If ftp URLs are being proxied, file URLs on a
+ remote host will be converted to ftp URLs before submission by
+ <strong>Lynx</strong> to the proxy server, so no special
+ procedure for inducing the proxy server to handle them is
+ required. Other WWW clients may require that the http server's
+ configuration file have &ldquo;Map file:* ftp:*&rdquo; in it to
+ perform that conversion.</p>
+
+ <p>If you have not set NNTPSERVER, proxy or no_proxy environment
+ variables you can set them at run time via the configuration file
+ lynx.cfg (this will not override external settings).</p>
+
+ <h2><a name="dos" id="dos">Win32 (95/NT) and 386 DOS</a></h2>
+
+ <p>(adapted from &ldquo;readme.txt&rdquo; by Wayne Buttles<br>
+ and &ldquo;readme.dos&rdquo; by Doug Kaufman)</p>
+
+ <p>Here are some environment variables that should be set,
+ usually in a batch file that runs the <strong>Lynx</strong>
+ executable. Make sure that you have enough room left in your
+ environment. You may need to change your &ldquo;SHELL=&rdquo;
+ setting in config.sys. In addition, <strong>Lynx</strong> looks
+ for a &ldquo;SHELL&rdquo; environment variable when shelling to
+ DOS. If you wish to preserve the environment space when shelling,
+ put a line like this in your AUTOEXEC.BAT file also &ldquo;SET
+ SHELL=C:\COMMAND.COM /E:2048&rdquo;. It should match
+ CONFIG.SYS.</p>
+
+ <pre>
+ HOME Where to keep the bookmark file and personal config files.
+ TEMP or TMP Bookmarks are kept here with no HOME. Temp files here.
+ USER Set to your login name
+ LYNX_CFG Set to the full path and filename for lynx.cfg
+</pre>
+ <p>386 version only:<br></p>
+
+ <pre>
+ WATTCP.CFG Set to the full path for the WATTCP.CFG directory
+</pre>
+ <p>(Depending on how you compiled libtcp.a, you may have to use
+ WATCONF.)</p>
+
+ <p>Define these in your batch file for running
+ <strong>Lynx</strong>. For example, if your application line is
+ &ldquo;D:\win32\lynx.bat&rdquo;, lynx.bat for Win32 may look
+ like:</p>
+
+ <pre>
+ @ECHO OFF
+ set home=d:\win32
+ set temp=d:\tmp
+ set lynx_cfg=d:\win32\lynx.cfg
+ d:\win32\lynx.exe %1 %2 %3 %4 %5
+</pre>
+ <p>In lynx_386, a typical batch file might look like:</p>
+
+ <pre>
+ @echo off
+ set HOME=f:/lynx2-8
+ set USER=your_login_name
+ set LYNX_CFG=%HOME%/lynx.cfg
+ set WATTCP.CFG=%HOME%
+ f:\lynx2-8\lynx %1 %2 %3 %4 %5 %6 %7 %8 %9
+</pre>
+ <p>You will also need to make sure that the WATTCP.CFG file has
+ the correct information for IP number, Gateway, Netmask, and
+ Domain Name Server. This can also be automated in the batch
+ file.</p>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/follow_help.html b/lynx_help/keystrokes/follow_help.html
new file mode 100644
index 0000000..1c9ca08
--- /dev/null
+++ b/lynx_help/keystrokes/follow_help.html
@@ -0,0 +1,286 @@
+<!-- $LynxId: follow_help.html,v 1.17 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Help on the Follow link (or page) number feature</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Lynx allows the user to select a link using a single-digit shortcut. There are several configuration choices which apply to this feature.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#numbering">Zero and other digits</a></li>
+
+ <li><a href="#suffixes">Suffixes</a></li>
+
+ <li><a href="#form_fields">Specifics for Form Fields</a></li>
+
+ <li><a href="#hidden_links">Hidden Links</a></li>
+
+ <li><a href="#goto_hidden_link">Navigating to Hidden
+ Links</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p>If a user has set one of these modes, (as the default or for
+ the current session via the <em>Options menu</em>) then hypertext
+ links (and form fields, depending on the keypad mode) are
+ prefixed with numbers in square brackets:</p>
+
+ <ul>
+ <li><em>Keypad mode</em> to <em>Links are numbered</em>,
+ or</li>
+
+ <li><em>Form fields are numbered</em>, or</li>
+
+ <li><em>Links and form fields are numbered</em>
+ </li>
+ </ul>
+
+ <p>Entering a keyboard or keypad number is treated as an
+ <em>F_LINK_NUM</em> command, and should invoke the <em>Follow
+ link (or goto link or page) number:</em> statusline prompt for a
+ potentially multiple digit number corresponding to an indicated
+ link number.</p>
+
+ <h2><a name="numbering" id="numbering">Zero and other digits</a></h2>
+
+ <p>The prompt can be invoked via typing a zero (<em>0</em>), but
+ it will not be treated as the lead digit for the number entry,
+ whereas digits 1 through 9 both invoke the prompt and are treated
+ as the first digit.</p>
+
+ <p>In <em>Form fields are numbered</em> or <em>Links and form
+ fields are numbered</em> mode, if the number corresponds to a
+ form field you will be positioned on that field, but if it is a
+ submit button it will not be ACTIVATE-ed.</p>
+
+ <p>If the user has set <em>Keypad mode</em> to <em>Numbers act as
+ arrows</em>, then only a zero digit will be treated as an
+ <em>F_LINK_NUM</em> command for invoking the <em>Follow link (or
+ goto link or page) number:</em> prompt.</p>
+
+ <h2><a name="suffixes" id="suffixes">Suffixes</a></h2>
+
+ <p>After accepting a number at the prompt, <strong>Lynx</strong>
+ accepts an optional suffix:</p>
+
+ <dl>
+ <dt><em>RETURN</em> (activate)</dt>
+
+ <dd>Without a suffix, e.g., If <em>RETURN</em> is pressed to
+ terminate the number entry (e.g., <em>123</em>) and it
+ corresponds to a hypertext link, <strong>Lynx</strong> will
+ retrieve the document for that link as if you had paged or used
+ other navigation commands to make it the current link and then
+ ACTIVATE-ed it.</dd>
+
+ <dt><code><strong>g</strong></code> (go)</dt>
+
+ <dd>
+ <p>If the number entered at the prompt has a
+ &ldquo;<em>g</em>&rdquo; suffix (e.g., <em>123g</em>), then
+ <strong>Lynx</strong> will make the link corresponding to
+ that number the current link, paging as appropriate if the
+ link does not appear in the currently displayed page. The
+ &ldquo;<em>g</em>&rdquo; suffix is inferred (need not be
+ entered) for form fields in <em>Form fields are numbered</em>
+ or <em>Links and form fields are numbered</em> mode.</p>
+ </dd>
+
+ <dt><code><strong>p</strong></code> (page)</dt>
+
+ <dd>
+ <p>Alternatively, if the number is given a
+ &ldquo;<em>p</em>&rdquo; suffix (e.g., <em>123p</em>),
+ <strong>Lynx</strong> will make the page corresponding to
+ that number the currently displayed page, and the first link
+ on that page, if any, the current link. The
+ &ldquo;<em>g</em>&rdquo; and &ldquo;<em>p</em>&rdquo;
+ suffixes thus convert the <em>Follow link (or goto link or
+ page) number:</em> feature to an advanced navigation aid.</p>
+ </dd>
+
+ <dt><code><strong>+</strong></code> or
+ <code><strong>-</strong></code> (jump)</dt>
+
+ <dd>
+ <p>Finally, a user may add a <em>+</em> or <em>-</em> suffix
+ to a number command to indicate jumping forward or back
+ relative to the current link or page. For example, typing
+ <em>1g+</em> followed by RETURN will move the current link to
+ the next numbered link, skipping any intervening pages or
+ unnumbered links; <em>1g-</em> goes to the preceding numbered
+ link. On a page without links, <em>3g+</em> goes to the 3rd
+ link <em>following</em> the page. <em>5p+</em> skips ahead 5
+ pages, and so on. You can also enter <em>5+</em> or
+ <em>5-</em>, which will activate the 5th link ahead/behind
+ where you are currently positioned. Note that typing
+ <em>1g+</em> is different from typing a down arrow in that
+ <em>1g+</em> skips pages containing no links, or intervening
+ non-numbered links, such as form fields when form fields are
+ not numbered. It also differs from the <em>&lt;tab&gt;</em>
+ command in that <em>1g+</em> does not skip over whole
+ textareas, unless form fields are not numbered.</p>
+
+ <p><em>NOTE:</em> <em>1+g 1-g 1+p 1-p</em> are all recognized
+ as equivalent to <em>1g+ 1g- 1p+ 1p-</em> . Any other
+ (mistyped) characters end the formula: e.g. <em>1gh+</em> is
+ treated as <em>1g</em>.</p>
+ </dd>
+ </dl>
+
+ <h2><a name="form_fields" id="form_fields">Specifics for Form
+ Fields</a></h2>
+
+ <p>Numbers are associated with form fields only when</p>
+
+ <ul>
+ <li><em>Form fields are numbered</em> or</li>
+
+ <li><em>Links and form fields are numbered</em> mode has been
+ selected.</li>
+ </ul>
+
+ <p>If you have selected <em>Numbers act as arrows</em> or
+ <em>Links are numbered</em> mode, you can seek form fields in the
+ document via WHEREIS searches for strings in their displayed
+ values. If they are INPUT or TEXTAREA fields with no values as
+ yet, you can use two or more underscores as the search string,
+ because underscores are used as placeholders for form fields in
+ the displayed document.</p>
+
+ <p id="select-option">When you have invoked a popup window for a
+ list of OPTIONs in a form's SELECT block:</p>
+
+ <ul>
+ <li>each OPTION is associated with a number, and that number
+ will be displayed in <em>Form fields are numbered</em> or
+ <em>Links and form fields are numbered</em> mode.</li>
+
+ <li>In any keypad mode, the <em>F_LINK_NUM</em>
+ (&ldquo;<em>0</em>&rdquo;) command will invoke a <em>Select
+ option (or page) number:</em> prompt, and you can enter a
+ number, and optionally a &ldquo;<em>g</em>&rdquo; or
+ &ldquo;<em>p</em>&rdquo; suffix, to select or seek an OPTION in
+ that list.</li>
+
+ <li>If only a number is entered at the prompt, the
+ corresponding OPTION will be selected and the popup will be
+ retracted.</li>
+
+ <li>If the &ldquo;<em>g</em>&rdquo; suffix is included, then
+ you will be positioned on the corresponding OPTION in the list,
+ paging through the list if necessary, but it will not be
+ treated as selected unless you enter the ACTIVATE (RETURN or
+ right-arrow) command when positioned on the OPTION.</li>
+
+ <li>For purposes of paging (e.g., in conjunction with the
+ &ldquo;<em>p</em>&rdquo; suffix), a <em>page</em> is defined as
+ the number of OPTIONs displayed within the vertical dimension
+ of the popup window.</li>
+
+ <li>Finally, the <em>+</em> and <em>-</em> suffixes can be used
+ to move forward or back from the current option or page in a
+ popup menu, similarly to the way they are used for links.</li>
+ </ul>
+
+ <p>For example, while viewing a popup window, the user can type
+ <em>3p+</em> and RETURN to skip ahead 3 pages, and <em>50g-</em>
+ will move the current selection back 50 options. This will work
+ whether or not <em>keypad mode</em> is <em>Form fields are
+ numbered</em> or <em>Links and form fields are numbered</em>
+ since options are numbered internally. If form field numbering is
+ turned off, the option numbers will not appear on screen, but the
+ user can still navigate using these commands.</p>
+
+ <h2><a name="hidden_links" id="hidden_links">Hidden Links</a></h2>
+
+ <p>HTML can be structured so that it includes <em>hidden
+ links</em>, i.e., without a visible link name intended for
+ ACTIVATE-ing the link. Such links may be created, for example,
+ by</p>
+
+ <ul>
+ <li>making an IMG element the sole content of an Anchor
+ element, and including an ALT="" attribute name/value pair to
+ suppress access to the link when the browser does not have
+ support for image handling available.</li>
+
+ <li>having truly empty Anchor content, in cases for which the
+ value of an Anchor's HREF attribute is intended as a navigation
+ aid for robots (typically indexers) and not as content for a
+ browser's rendition of the document.</li>
+
+ <li>using the <em>-ismap</em> command line switch, which makes
+ <strong>Lynx</strong> additionally treat a link to a
+ server-side image maps as hidden if there also is a client-side
+ map for the same image.</li>
+
+ <li>bad HTML, which may produce <em>hidden links</em>.</li>
+ </ul>
+
+ <p><em>Hidden links</em> differ from Anchors that have only a
+ NAME or ID attribute name/value pair (intended as positioning
+ targets from other links which do have HREF attributes and values
+ that include a fragment).</p>
+
+ <p><strong>Lynx</strong> respects instructions for <em>hidden
+ links</em> and normally does not include them in the rendition of
+ the document. However, if the command line switch
+ <em>-hiddenlinks=merge</em> is used, such links will still be
+ numbered in sequence with other links which are not hidden, and
+ if <em>Links are numbered</em> mode is also on, link numbers will
+ appear for them in the displayed text (except for links to image
+ maps which are hidden because of <em>-ismap</em>). If
+ <em>-hiddenlinks=listonly</em> or <em>-hiddenlinks=ignore</em> is
+ in effect, <em>hidden links</em> will not be shown in the text
+ even in <em>links are numbered</em> mode. Not using a
+ <em>-hiddenlinks</em> flag at all is equivalent to
+ <em>-hiddenlinks=listonly</em>.</p>
+
+ <h2><a name="goto_hidden_link" id="goto_hidden_link">Navigating
+ to Hidden Links</a></h2>
+
+ <p>If a document includes <em>hidden links</em>, they will be
+ reported, with appropriate labeling, in the menus created for the
+ LIST (&ldquo;<em>l</em>&rdquo;) or ADDRLIST
+ (&ldquo;<em>A</em>&rdquo;) commands, unless
+ <em>-hiddenlinks=ignore</em> is used. They can then be
+ ACTIVATE-ed via those menus.</p>
+
+ <p>If a link was hidden because of an ALT attribute in an IMG
+ element, it will be converted to a <em>visible link</em> whenever
+ the IMAGE_TOGGLE (&ldquo;<em>*</em>&rdquo;) command is used to
+ create links for SRC attribute values of IMG elements, because
+ this indicates that the user does have some form of image
+ handling enabled via a helper application, or wishes to download
+ files for subsequent use with a graphic browser or other suitable
+ software.</p>
+
+ <p>HTML forms may have fields with a HIDDEN attribute, indicating
+ that a name/value pair for the fields should be included in the
+ content submitted for the form, but the value should not be
+ displayed in the rendered form. <strong>Lynx</strong> respects
+ this attribute as well, and neither displays the HIDDEN field,
+ nor assigns it a number for the F_LINK_NUM
+ (&ldquo;<em>0</em>&rdquo;) command and <em>Form fields are
+ numbered</em> or <em>Links and form fields are numbered</em>
+ keypad mode handling, nor includes an entry for it in the menus
+ created for the LIST (&ldquo;<em>l</em>&rdquo;) or ADDRLIST
+ (&ldquo;<em>A</em>&rdquo;) commands. However, the HIDDEN
+ name/value pairs are included in any displays of submitted form
+ content in the <em>Information about the current document</em>
+ that is invoked by the INFO (&ldquo;<em>=</em>&rdquo;)
+ command.</p>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/gopher_types_help.html b/lynx_help/keystrokes/gopher_types_help.html
new file mode 100644
index 0000000..ac6b090
--- /dev/null
+++ b/lynx_help/keystrokes/gopher_types_help.html
@@ -0,0 +1,87 @@
+<!-- $LynxId: gopher_types_help.html,v 1.13 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Listing of Gopher types</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "This is a list of the file-types which are known to Lynx in its gopher interface.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Listing of Gopher types</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Listing of Gopher types</a></h2>
+
+ <dl>
+ <dt>(FILE)</dt>
+
+ <dd>An ASCII file</dd>
+
+ <dt>(DIR)</dt>
+
+ <dd>A directory listing</dd>
+
+ <dt>(CSO)</dt>
+
+ <dd>The Computing Services Organizations nameserver
+ interface</dd>
+
+ <dt>(BIN)</dt>
+
+ <dd>
+ A binary file with one of the following meanings
+ <ul>
+ <li>A Binary file with PC extensions</li>
+
+ <li>A Binary file with UNIX extensions</li>
+ </ul>
+ </dd>
+
+ <dt>(HQX)</dt>
+
+ <dd>A Macintosh file that has been BinHexed</dd>
+
+ <dt>(?)</dt>
+
+ <dd>A searchable database</dd>
+
+ <dt>(IMG)</dt>
+
+ <dd>An unknown image type<br>
+ You must have an <a href="xterm_help.html">X terminal</a> to
+ view images</dd>
+
+ <dt>(GIF)</dt>
+
+ <dd>An image in Graphics Interchange Format<br>
+ You must have an <a href="xterm_help.html">X terminal</a> to
+ view images</dd>
+
+ <dt>(HTML)</dt>
+
+ <dd>A World Wide Web hypertext file</dd>
+
+ <dt>(TEL)</dt>
+
+ <dd>The link will open a connection to another host using
+ telnet</dd>
+
+ <dt>(3270)</dt>
+
+ <dd>The link will open a connection to another host using
+ tn3270</dd>
+
+ <dt>(UKN)</dt>
+
+ <dd>An unknown or unsupported type</dd>
+ </dl>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/history_help.html b/lynx_help/keystrokes/history_help.html
new file mode 100644
index 0000000..62f45df
--- /dev/null
+++ b/lynx_help/keystrokes/history_help.html
@@ -0,0 +1,58 @@
+<!-- $LynxId: history_help.html,v 1.10 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Help on the History Page</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Lynx provides a history page, showing all of the links which have been traversed to reach the current point. The user can revisit any of these links.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#navigation">Navigation</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p><strong>Lynx</strong>'s History Page displays all of the links
+ that you have traveled through to reach your current point,
+ including any temporary menu or list files that included links,
+ bookmark files, and any documents associated with POST content.
+ If you entered a document and then left it by using the
+ <em>left-arrow</em> key, it will <em>not</em> be in the history
+ stack. If you entered a document and left it by selecting another
+ link within that document, it <em>will</em> be in the history
+ stack.</p>
+
+ <h2><a name="navigation" id="navigation">Navigation</a></h2>
+
+ <p>You may <a href="movement_help.html">select</a> any link on
+ the History Page to review a document that you have previously
+ visited. That link, and any subsequent to it, will not be removed
+ from the history stack if you return to it via the History Page.
+ You thus should use a History Page link, rather than the
+ <em>left-arrow</em> key, if you wish to review previous documents
+ without needing to remember and repeat the series of selections
+ for reaching your currently displayed document.</p>
+
+ <p>Upon using <em>left-arrow</em> in the document selected via
+ the History Page, you will be returned to the document from which
+ you initially went to the History Page.</p>
+
+ <p>If a previously visited link has been removed from the history
+ stack, and it was not a temporary menu or list file, bookmark
+ file, or document associated with POST content, it can still be
+ selected conveniently via the <a href="visited_help.html">Visited
+ Links Page</a>. The latter also will include links which were
+ &ldquo;<em>d</em>&rdquo;ownloaded or passed to a helper
+ application, and thus were not included in the history stack.</p>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/keystroke_help.html b/lynx_help/keystrokes/keystroke_help.html
new file mode 100644
index 0000000..68043ff
--- /dev/null
+++ b/lynx_help/keystrokes/keystroke_help.html
@@ -0,0 +1,177 @@
+<!-- $LynxId: keystroke_help.html,v 1.22 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Help on Lynx Keystroke Commands</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Lynx recognizes many single-character commands. This is an overview to their default bindings, with links to more detailed documentation.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#movement">Movement</a></li>
+
+ <li><a href="#scrolling">Scrolling</a></li>
+
+ <li><a href="#dired">Dired</a></li>
+
+ <li><a href="#other">Other</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p><strong>Lynx</strong> recognizes many single-character
+ commands. This is an overview to their default bindings, with
+ links to more detailed documentation.</p>
+
+ <h2><a name="movement" href="movement_help.html" id=
+ "movement">Movement</a></h2>
+
+ <pre>
+ Down arrow - Highlight next topic
+ Up arrow - Highlight previous topic
+ Right arrow, - Jump to highlighted topic
+ Return, Enter - Follow selected link
+ Left arrow - Return to previous topic
+</pre>
+ <h2><a name="scrolling" href="scrolling_help.html" id=
+ "scrolling">Scrolling</a></h2>
+
+ <pre>
+ + - Scroll down to next page (Page-Down)
+ - - Scroll up to previous page (Page-Up)
+ SPACE - Scroll down to next page (Page-Down)
+ b - Scroll up to previous page (Page-Up)
+ CTRL-A - Go to first page of the current document (Home)
+ CTRL-E - Go to last page of the current document (End)
+ CTRL-B - Scroll up to previous page (Page-Up)
+ CTRL-F - Scroll down to next page (Page-Down)
+ CTRL-N - Go forward two lines in the current document
+ CTRL-P - Go back two lines in the current document
+ ) - Go forward half a page in the current document
+ ( - Go back half a page in the current document
+ ^ - Go to the first link on the current line
+ $ - Go to the last link on the current line
+ &lt; - Go to the previous link in the current column
+ &gt; - Go to the next link in the current column
+ # - Go to Toolbar or Banner in the current document
+</pre>
+ <h2><a name="dired" href="dired_help.html" id="dired">Dired</a></h2>
+
+ <pre>
+ c - Create a new file
+ d - Download selected file
+ e - Edit selected file
+ f - Show a full menu of options for current file
+ m - Modify the name or location of selected file
+ r - Remove selected file
+ t - Tag highlighted file
+ u - Upload a file into the current directory
+</pre>
+ <h2><a name="other" href="other_help.html" id="other">Other</a></h2>
+
+ <pre>
+ ? (or h) - Help (this screen)
+ a - Add the current link to a bookmark file
+ c - Send a comment to the document owner
+ d - Download the current link
+ e - Edit the current file
+ E - Edit the current link's URL (or ACTION) and
+ use that as a goto URL.
+ g - Goto a user specified <a href=
+"../lynx_url_support.html">URL</a> or file
+ G - Edit the current document's URL and use that
+ as a goto URL.
+ i - Show an index of documents
+ j - Execute a jump operation
+ k - Show list of actual key mappings
+ l - List references (links) in current document
+ m - Return to main screen
+ o - Set your <a href=
+"option_help.html">options</a>
+ p - <a href=
+"print_help.html">Print</a> to a file, mail, printers, or other
+ q - Quit (Capital &ldquo;Q&rdquo; for quick quit)
+ / - Search for a string within the current document
+ s - Enter a search string for an external search
+ n - Go to the next search string
+ N - Go to the previous search string
+ v - View a <a href=
+"bookmark_help.html">bookmark file</a>
+ V - Go to the <a href=
+"visited_help.html">Visited Links Page</a>
+ x - Force submission of form or link with no-cache
+ z - Cancel transfer in progress
+ [backspace] - Go to the <a href=
+"history_help.html">History Page</a>
+ = - Show info about current document, URL and link
+ \ - Toggle document source/rendered view
+ ! - Spawn your default shell
+ ' - Toggle "historical" vs minimal or valid comment
+ parsing
+ _ - Clear all authorization info for this session
+ ` - Toggle minimal or valid comment parsing
+ * - Toggle image_links mode on and off
+ @ - Toggle raw 8-bit translations or CJK mode
+ on or off
+ . - Run external program on the current link.
+ , - Run external program on the current document.
+ { - Shift the screen left.
+ } - Shift the screen right.
+ | - Toggle line-wrap mode. When line-wrap is
+ off, you may use { and } to shift the screen
+ left/right. The screen width is set to 999.
+ ~ - Toggle parsing of nested tables (experimental).
+ [ - Toggle pseudo_inlines mode on and off
+ ] - Send a HEAD request for the current doc or link
+ " - Toggle valid or "soft" double-quote parsing
+ CTRL-R - Reload current file and refresh the screen
+ CTRL-L - Refresh the screen
+
+ CTRL-V - Outside of a text input line or field,
+ switch to <a href=
+"option_help.html#tagsoup">alternative parsing</a> of HTML.
+ - In a form text input field,
+ CTRL-V prompts for a key command (allows
+ <a href=
+"../Lynx_users_guide.html#CtrlVNote">escaping</a> from the field).
+
+ Note that on most UNIX hosts, CTRL-V is bound
+ via stty to the lnext (literal-next) code but
+ the exact behavior of that is implementation
+ specific. On Solaris you must type CTRL-V
+ twice to use it, since it quotes the following
+ keystroke.
+
+ CTRL-U - Inside text input line or field,
+ erase input line (<a href=
+"edit_help.html">more input line commands</a>)
+ - Outside of text input or field,
+ undo returning to previous topic.
+
+ CTRL-G - Cancel input or transfer
+
+ CTRL-T - Toggle trace mode on and off
+ ; - View the Lynx Trace Log for the current session
+ CTRL-K - Invoke the <a href=
+"cookie_help.html">Cookie Jar Page</a>
+ CTRL-X - Invoke the <a href=
+"../Lynx_users_guide.html#Cache">Cache Jar Page</a>
+ <em>numbers</em> - Invoke the prompt
+ <a href=
+"follow_help.html">Follow link (or goto link or page) number:</a>
+ or the
+ <a href=
+"follow_help.html#select-option">Select option (or page) number:</a>
+ prompt
+</pre>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/movement_help.html b/lynx_help/keystrokes/movement_help.html
new file mode 100644
index 0000000..1ba648e
--- /dev/null
+++ b/lynx_help/keystrokes/movement_help.html
@@ -0,0 +1,78 @@
+<!-- $LynxId: movement_help.html,v 1.11 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Help on Lynx Movement commands</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "These are the Lynx keystroke-movement commands which are usable in all non-editing contexts, for traversing links.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#notes">Notes</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p>These are the Lynx <a href=
+ "keystroke_help.html#movement">keystroke-movement</a> commands
+ which are usable in all non-editing contexts, for traversing
+ links.</p>
+
+ <pre>
+ Down arrow, - Move to the next hypertext link,
+ TAB or scroll down if there are no more
+ links on the page to move to.
+
+ Up arrow - Move to the previous hypertext link,
+ or scroll up if there are no links
+ above the current one, and there are
+ previous pages to move to.
+
+ Right arrow, - select the link that the cursor is
+ Return, Enter positioned on.
+
+ Left arrow - Retreat from a link. Go back to the
+ previous topic.
+</pre>
+ <h2><a name="notes" id="notes">Notes</a></h2>
+
+ <ol>
+ <li>If <em>VI Keys</em> are enabled from the options menu or
+ from the <code>.lynxrc</code> file, lowercase h,j,k,l will move
+ left, down, up, and right, respectively.</li>
+
+ <li>If <em>Emacs Keys</em> are enabled from the options menu or
+ from the <code>.lynxrc</code> file, Ctrl-B, Ctrl-N, Ctrl-P,
+ Ctrl-F will move left, down, up, and right, respectively.</li>
+
+ <li>If the <em>Num Lock</em> on your keyboard is on,
+ <strong>Lynx</strong> will translate the numbers of your keypad
+ into movement commands. The translation corresponds with the
+ labels on numeric keypad, but can be used from the main
+ keyboard. It is as follows.</li>
+ </ol>
+
+ <blockquote>
+ <pre>
+ 9 - page up
+ 8 - up arrow
+ 7 8 9 7 - moves to the top of a document
+ \|/ 6 - right arrow
+ 4 - 5 - 6 5 - nothing
+ /|\ 4 - left arrow
+ 1 2 3 3 - page down
+ 2 - down arrow
+ 1 - moves to the end of a document
+</pre>
+ </blockquote>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/option_help.html b/lynx_help/keystrokes/option_help.html
new file mode 100644
index 0000000..3138572
--- /dev/null
+++ b/lynx_help/keystrokes/option_help.html
@@ -0,0 +1,823 @@
+<!-- $LynxId: option_help.html,v 1.34 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Form-based Options Menu : Help</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Lynx's options menu allows you to set and modify many features. Some features persist only during the current session unless specially enabled in lynx.cfg">
+</head>
+<body>
+ <h2><a name="overview" id="overview">Options Menu</a></h2>
+
+ <p>The <em>Options Menu</em> allows you to set and modify many
+ Lynx features.<br>
+ <strong>Lynx</strong>'s <em>Options Menu</em> is grouped visually
+ (by skipping a line) into sections. This description follows the
+ same arrangement. Some options appear on the screen only if they
+ have been compiled in or chosen in
+ <code><strong>lynx.cfg</strong></code>.</p>
+
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Options Menu</a></li>
+
+ <li>
+ <a href="#GP">General Preferences</a>
+ <ul>
+ <li><a href="#UM">User Mode</a></li>
+
+ <li><a href="#ED">Editor</a></li>
+
+ <li><a href="#ST">Type of Search</a></li>
+ </ul>
+ </li>
+
+ <li>
+ <a href="#SP">Security and Privacy</a>
+ <ul>
+ <li><a href="#CK">Cookies</a></li>
+
+ <li><a href="#IK">Invalid-Cookie Prompting</a></li>
+
+ <li><a href="#SK">SSL Prompting</a></li>
+ </ul>
+ </li>
+
+ <li>
+ <a href="#KI">Keyboard Input</a>
+ <ul>
+ <li><a href="#KM">Keypad mode</a></li>
+
+ <li><a href="#EM">Emacs keys</a></li>
+
+ <li><a href="#VI">VI keys</a></li>
+
+ <li><a href="#LE">Line edit style</a></li>
+ </ul>
+ </li>
+
+ <li>
+ <a href="#DP">Display and Character Set</a>
+ <ul>
+ <li><a href="#LC">Use locale-based character set</a></li>
+
+ <li><a href="#H5">Use HTML5 charset replacements</a></li>
+
+ <li><a href="#DC">Display Character set</a></li>
+
+ <li><a href="#AD">Assumed document character set</a></li>
+
+ <li><a href="#JK">Raw 8-bit or CJK mode</a></li>
+
+ <li><a href="#DV">X DISPLAY variable</a></li>
+ </ul>
+ </li>
+
+ <li>
+ <a href="#AP">Document Appearance</a>
+ <ul>
+ <li><a href="#SC">Show color</a></li>
+
+ <li><a href="#CS">Color style</a></li>
+
+ <li><a href="#C0">Default colors</a></li>
+
+ <li><a href="#CL">Show cursor for current link or
+ option</a></li>
+
+ <li><a href="#UK">Underline links</a></li>
+
+ <li><a href="#SS">Show scrollbar</a></li>
+
+ <li><a href="#PU">Pop-ups for select fields</a></li>
+
+ <li><a href="#tagsoup">HTML error recovery</a></li>
+
+ <li><a href="#BH">Bad HTML messages</a></li>
+
+ <li><a href="#SI">Show Images</a></li>
+
+ <li><a href="#VB">Verbose Images</a></li>
+ </ul>
+ </li>
+
+ <li>
+ <a href="#HP">Headers Transferred to Remote Servers</a>
+ <ul>
+ <li><a href="#PM">Personal mail address</a></li>
+
+ <li><a href="#PN">Personal name for mail</a></li>
+
+ <li><a href="#PW">Password for anonymous ftp</a></li>
+
+ <li><a href="#PT">Preferred media type</a></li>
+
+ <li><a href="#PE">Preferred encoding</a></li>
+
+ <li><a href="#PC">Preferred Document Charset</a></li>
+
+ <li><a href="#PL">Preferred Document Language</a></li>
+
+ <li><a href="#SA">Send User-Agent header</a></li>
+
+ <li><a href="#UA">User Agent</a></li>
+ </ul>
+ </li>
+
+ <li>
+ <a href="#LP">Listing and Accessing Files</a>
+ <ul>
+ <li><a href="#PF">Use Passive FTP</a></li>
+
+ <li><a href="#FT">FTP sort criteria</a></li>
+
+ <li><a href="#LD">Local directory sort criteria</a></li>
+
+ <li><a href="#LO">Local directory sort order</a></li>
+
+ <li><a href="#DF">Show dot files</a></li>
+
+ <li><a href="#PZ">Pause when showing message</a></li>
+
+ <li><a href="#LL">Execution links</a></li>
+
+ <li><a href="#TX">Show transfer rate</a></li>
+ </ul>
+ </li>
+
+ <li>Special Files and Screens
+ <ul>
+ <li><a href="#MB">Multi-bookmarks</a></li>
+
+ <li><a href="#BF">Bookmark file</a></li>
+
+ <li><a href="#AZ">Auto Session</a></li>
+
+ <li><a href="#SZ">Session file</a></li>
+
+ <li><a href="#VP">Visited Pages</a></li>
+ </ul>
+ </li>
+ </ul>
+ </div>
+
+ <h2><a name="GP" id="GP">General Preferences</a></h2>
+
+ <h3><a name="UM" id="UM">User Mode</a></h3>
+
+ <dl>
+ <dt><em>Novice</em>: Shows 2 extra lines of help at the bottom
+ of the screen for beginners.</dt>
+
+ <dt><em>Intermediate (normal)</em>: Normal status-line messages
+ appear.</dt>
+
+ <dt><em>Advanced</em>: The URL is shown on the status
+ line.</dt>
+ </dl>
+
+ <h3><a name="ED" id="ED">Editor</a></h3>
+
+ <p>This is the editor to be invoked when editing browsable files,
+ sending mail or comments, or filling form's textarea (multiline
+ input field). The full pathname of the editor command should be
+ specified when possible. It is assumed the text editor supports
+ the same character set you have for "display character set" in
+ Lynx.</p>
+
+ <h3><a name="ST" id="ST">Type of Search</a></h3>
+
+ <p>This allows you to tell Lynx whether to search the current
+ document ignoring case (case insensitive) or not.</p>
+
+ <h2><a name="SP" id="SP">Security and Privacy</a></h2>
+
+ <h3><a name="CK" id="CK">Cookies</a></h3>
+
+ <p>This can be set to accept or reject all cookies or to ask each
+ time. See the Users Guide for details of <a href=
+ "../Lynx_users_guide.html#Cookies">cookie usage</a>.</p>
+
+ <h3><a name="IK" id="IK">Invalid-Cookie Prompting</a></h3>
+
+ <p>This allows you to tell how to handle invalid cookies:</p>
+
+ <ul>
+ <li><em>prompt normally</em> to prompt for each cookie</li>
+
+ <li><em>force yes-response</em> to reply "yes" to each
+ prompt</li>
+
+ <li><em>force no-response</em> to reply "no" to each
+ prompt.</li>
+ </ul>
+
+ <h3><a name="SK" id="SK">SSL Prompting</a></h3>
+
+ <p>This allows you to tell how to handle errors detected in SSL
+ connections:</p>
+
+ <ul>
+ <li><em>prompt normally</em> to prompt for each cookie</li>
+
+ <li><em>force yes-response</em> to reply "yes" to each
+ prompt</li>
+
+ <li><em>force no-response</em> to reply "no" to each
+ prompt.</li>
+ </ul>
+
+ <h2><a name="KI" id="KI">Keyboard Input</a></h2>
+
+ <h3><a name="KM" id="KM">Keypad mode</a></h3>
+
+ <p>This gives the choice between navigating with the keypad (as
+ arrows; see Lynx Navigation) and having every link numbered
+ (numbered links) so that the links may be selected by numbers
+ instead of moving to them with the arrow keys. You can also
+ number form fields.</p>
+
+ <h3><a name="EM" id="EM">Emacs keys</a></h3>
+
+ <p>If set to &ldquo;ON&rdquo; 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).</p>
+
+ <p>Note: setting emacs keys does not affect the line-editor
+ bindings.</p>
+
+ <h3><a name="VI" id="VI">VI keys</a></h3>
+
+ <p>If set to &ldquo;ON&rdquo; then the lowercase h, j, k and l
+ keys will be mapped to left-arrow, down-arrow, up-arrow and
+ right-arrow respectively.</p>
+
+ <p>The uppercase H, J, K, and L keys remain mapped to their
+ configured bindings (normally HELP, JUMP, KEYMAP and LIST,
+ respectively).</p>
+
+ <p>Note: setting vi keys does not affect the line-editor
+ bindings.</p>
+
+ <h3><a name="LE" id="LE">Line edit style</a></h3>
+
+ <p>This allows you to set alternate key bindings for the built-in
+ line editor, if <a href="alt_edit_help.html">Alternate
+ Bindings</a> have been installed. Otherwise, Lynx uses the
+ <a href="edit_help.html">Default Binding</a>.</p>
+
+ <h2><a name="DP" id="DP">Display and Character Set</a></h2>
+
+ <h3><a name="LC" id="LC">Use locale-based character set</a></h3>
+
+ <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>
+
+ <h3><a name="H5" id="H5">Use HTML5 charset replacements</a></h3>
+
+ <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>
+
+ <h3><a name="DC" id="DC">Display Character set</a></h3>
+
+ <p>This 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, <a href="test_display.html">try the test here</a>.</p>
+
+ <h3><a name="AD" id="AD">Assumed document character set</a></h3>
+
+ <p>This 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 HTTP protocol). Unfortunately, many non-English web
+ pages forget to include proper charset info; this option helps
+ you browse those broken pages if you know somehow 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. Option is active when &ldquo;Raw
+ 8-bit or CJK Mode&rdquo; is OFF.</p>
+
+ <h3><a name="JK" id="JK">Raw 8-bit or CJK mode</a></h3>
+
+ <p>This is set automatically, but can be toggled manually in
+ certain cases: it toggles whether 8-bit characters are assumed to
+ correspond with the display character set and therefore are
+ processed without translation via the chartrans conversion
+ tables. ON by default when the display character set is one of
+ the Asian (CJK) sets and the 8-bit characters are Kanji
+ multibytes. 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 have
+ no better idea than viewing it as from display character set (see
+ &ldquo;assumed document character set&rdquo; for best choice).
+ Should be OFF when an Asian (CJK) set is selected but the
+ document is ISO-8859-1 or another &ldquo;assumed document
+ character set&rdquo;. The setting can also be toggled via the
+ RAW_TOGGLE command, normally mapped to &ldquo;@&rdquo;, and at
+ startup via the -raw switch.</p>
+
+ <h3><a name="DV" id="DV">X DISPLAY variable</a></h3>
+
+ <p>This option is only relevant to X Window users. It specifies
+ the DISPLAY (Unix) or DECW$DISPLAY (VMS) variable. It is picked
+ up automatically from the environment if it has been previously
+ set.</p>
+
+ <h2><a name="AP" id="AP">Document Appearance</a></h2>
+
+ <h3><a name="SC" id="SC">Show color</a></h3>
+
+ <p>This will be present if color support is available.</p>
+
+ <ul>
+ <li>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.</li>
+
+ <li>If set to OFF or NEVER, color mode will be turned off.</li>
+
+ <li>ALWAYS and NEVER are not offered in anonymous accounts. If
+ saved to a &ldquo;.lynxrc&rdquo; file in non-anonymous
+ accounts, ALWAYS will cause Lynx to set color mode on at
+ startup if supported.</li>
+ </ul>
+
+ <p>If Lynx is built with slang, this is equivalent to having
+ included the -color command line switch or having the COLORTERM
+ 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 start-up. It is similar to the -nocolor switch, but
+ (when the slang library is used) can be overridden with the
+ -color switch. If the setting is OFF or ON when the current
+ options are saved to a &ldquo;.lynxrc&rdquo; file, the default
+ start-up 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 slang is used) if forced
+ on via the -color switch or COLORTERM variable. This default
+ behavior always is used in anonymous accounts, or if the
+ &ldquo;option&rdquo;_save restriction is set explicitly. If for
+ any reason the start-up color mode is incorrect for your
+ terminal, set it appropriately on or off via this option.</p>
+
+ <h3><a name="CS" id="CS">Color style</a></h3>
+
+ <p>At startup, Lynx identifies the available color-style
+ configuration files in the same directory as its default ".lss"
+ file. At runtime, you can switch between these files using this
+ options-menu feature.</p>
+
+ <h3><a name="C0" id="C0">Default colors</a></h3>
+
+ <p>Depending on the default foreground and background colors
+ which your terminal uses, some color-styles would look better if
+ Lynx did not use those in combination with the style for the
+ background. Use this option to enable/disable the default-color
+ feature.</p>
+
+ <h3><a name="CL" id="CL">Show cursor for current link or
+ option</a></h3>
+
+ <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 is also
+ 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 display.</p>
+
+ <h3><a name="UK" id="UK">Underline links</a></h3>
+
+ <p>Use underline-attribute rather than bold for links.</p>
+
+ <h3><a name="SS" id="SS">Show scrollbar</a></h3>
+
+ <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>
+
+ <h3><a name="PU" id="PU">Pop-ups for select fields</a></h3>
+
+ <p>Lynx normally uses a pop-up 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
+ pop-up 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>
+
+ <h3><a name="tagsoup" id="tagsoup">HTML error recovery</a></h3>
+
+ <p>Lynx often has to deal with invalid HTML markup. It always
+ tries to recover from errors, but there is no universally correct
+ way for doing this. As a result, there are two parsing modes:
+ "<dfn>SortaSGML</dfn>" attempts to enforce valid nesting of most
+ tags at an earlier stage of processing, while
+ "<dfn>TagSoup</dfn>" relies more on the HTML rendering stage to
+ mimic the behavior of some other browsers. You can also switch
+ between these modes with the CTRL-V key, and the default can be
+ changed in lynx.cfg or with the -tagsoup command line switch.</p>
+
+ <p>The "SortaSGML" mode will often appear to be more strict, and
+ makes some errors apparent that are otherwise unnoticeable. One
+ particular difference is the handling of block elements or
+ &lt;li&gt;..&lt;/li&gt; inside &lt;a
+ HREF="some.url"&gt;..&lt;/a&gt;. Invalid nesting like this may
+ turn anchors into hidden links which cannot be easily followed,
+ this is avoided in "TagSoup" mode. See the <a href=
+ "follow_help.html">help on following links by number</a> for more
+ information on hidden links. Often pages may be more readable in
+ "TagSoup" mode, but sometimes the opposite is true. Most
+ documents with valid HTML, and documents with only minor errors,
+ should be rendered the same way in both modes.</p>
+
+ <p>If you are curious about what goes on behind the scenes, but
+ find that the information from the -trace switch is just too
+ much, Lynx can be started with the -preparsed switch; going into
+ SOURCE mode (&ldquo;\&rdquo; key) and toggling the parsing mode
+ (with CTRL-V) should then show some of the differences.</p>
+
+ <h3><a name="BH" id="BH">Bad HTML messages</a></h3>
+
+ <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>
+
+ <dt>Add to trace-file</dt>
+
+ <dd>add the detailed warning message to the trace-file.</dd>
+
+ <dt>Add to LYNXMESSAGES</dt>
+
+ <dd>add the detailed warning message to the message page at
+ "LYNXMESSAGES:".</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>
+ </dl>
+
+ <h3><a name="SI" id="SI">Show Images</a></h3>
+
+ <p>This option combines the effects of the &ldquo;*&rdquo; &amp;
+ &ldquo;[&rdquo; keys as follows:</p>
+
+ <pre>
+ <em>ignore</em> all images which lack an ALT= text string,
+ <em>show labels</em>, e.g. [INLINE] &mdash; see &ldquo;Verbose Images&rdquo; below &mdash; ,
+ <em>use links</em> for every image, enabling downloading.
+</pre>
+ <p>This option setting cannot be saved between sessions. See
+ <a href="../Lynx_users_guide.html#Images">Users Guide</a> &amp;
+ <em>lynx.cfg</em> for more details.</p>
+
+ <h3><a name="VB" id="VB">Verbose Images</a></h3>
+
+ <p>This allows you to replace [LINK], [INLINE] and [IMAGE]
+ &mdash; for images without ALT &mdash; with filenames: this can
+ be helpful by revealing which images are important &amp; which
+ are merely decoration, e.g. <em>button.gif</em>,
+ <em>line.gif</em>. See <a href=
+ "../Lynx_users_guide.html#Images">Users Guide</a> &amp;
+ <em>lynx.cfg</em> for more details.</p>
+
+ <h2><a name="HP" id="HP">Headers Transferred to Remote
+ Servers</a></h2>
+
+ <h3><a name="PM" id="PM">Personal Mail Address</a></h3>
+
+ <p>You may set your mail address here so that when mailing
+ messages to other people or mailing files to yourself, your email
+ address can be automatically filled in. Your email address will
+ also be sent to HTTP servers in a &ldquo;from:&rdquo; field.</p>
+
+ <h3><a name="PN" id="PN">Personal mail name</a></h3>
+
+ <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
+ <em>lynx.cfg</em>.</p>
+
+ <h3><a name="PW" id="PW">Password for anonymous ftp</a></h3>
+
+ <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>
+
+ <h3><a name="PT" id="PT">Preferred media type</a></h3>
+
+ <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.</p>
+
+ <dl>
+ <dt>Accept lynx's internal types</dt>
+
+ <dd>list only the types that are compiled into lynx.</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>
+
+ <dt>Also accept user's types</dt>
+
+ <dd>lists types from the PERSONAL_EXTENSION_MAP setting in
+ lynx.cfg</dd>
+
+ <dt>Also accept system's types</dt>
+
+ <dd>lists types from the GLOBAL_EXTENSION_MAP setting in
+ lynx.cfg</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>
+ </dl>
+
+ <h3><a name="PE" id="PE">Preferred encoding</a></h3>
+
+ <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>
+
+ <h3><a name="PC" id="PC">Preferred Document Charset</a></h3>
+
+ <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 make your order of
+ preference explicit by using &ldquo;q factors&rdquo; as defined
+ by the HTTP protocol, for servers which understand it: e.g.,
+ <kbd>iso-8859-5, utf-8;q=0.8</kbd>.</p>
+
+ <h3><a name="PL" id="PL">Preferred Document Language</a></h3>
+
+ <p>The language you prefer if multi-language files are available
+ from servers. Use RFC 1766 tags, e.g., &ldquo;en&rdquo; English,
+ &ldquo;fr&rdquo; French. Can be a comma-separated list, and you
+ can use &ldquo;q factors&rdquo; (see previous help item): e.g.,
+ <kbd>da, en-gb;q=0.8, en;q=0.7</kbd> .</p>
+
+ <h3><a name="SA" id="SA">Send User-Agent header</a></h3>
+
+ <p>This controls whether the user-agent string will be sent.</p>
+
+ <h3><a name="UA" id="UA">User Agent header</a></h3>
+
+ <p>The header string which Lynx sends to servers to indicate the
+ User-Agent is displayed here. Changes may be disallowed via the
+ -restrictions switch. Otherwise, the header can be changed
+ temporarily to e.g., L_y_n_x/2.8.3 for access to sites which
+ discriminate against Lynx based on checks for the presence of
+ &ldquo;Lynx&rdquo; in the header. If changed during a Lynx
+ session, the default User-Agent header can be restored 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 Options Menu. Changes
+ of the header are not saved in the .lynxrc file.</p>
+
+ <p>Caveat: Netscape Communications Corp. (for example) claimed
+ that false transmissions of &ldquo;Mozilla&rdquo; as the
+ User-Agent are a copyright infringement, which would be
+ prosecuted. The <em>Options Menu</em> issues a warning about
+ possible copyright infringement whenever the header is changed to
+ one which does not include <strong>Lynx</strong> or
+ <strong>lynx</strong>.</p>
+
+ <h2><a name="LP" id="LP">Listing and Accessing Files</a></h2>
+
+ <h3><a name="PF" id="PF">Use Passive FTP</a></h3>
+
+ <p>This allows you to change whether Lynx uses passive ftp
+ connections.</p>
+
+ <h3><a name="FT" id="FT">FTP sort criteria</a></h3>
+
+ <p>This allows you to specify how files will be sorted within FTP
+ listings. The current options include
+ &ldquo;By&nbsp;Filename&rdquo;, &ldquo;By&nbsp;Size&rdquo;,
+ &ldquo;By&nbsp;Type&rdquo;, &ldquo;By&nbsp;Date&rdquo;.</p>
+
+ <h3><a name="LD" id="LD">List directory style</a></h3>
+
+ <p>Applies to Directory Editing. Files and directories can be
+ presented in the following ways:</p>
+
+ <dl>
+ <dt><em>Mixed style</em>: Files and directories are listed
+ together in alphabetical order.</dt>
+
+ <dt><em>Directories first</em>: Files and directories are
+ separated into 2 alphabetical lists: directories are listed
+ first.</dt>
+
+ <dt><em>Files first</em>: Files and directories are separated
+ into 2 alphabetical lists: files are listed first.</dt>
+ </dl>
+
+ <h3><a name="LO" id="LO">Local directory sort order</a></h3>
+
+ <p>Lynx also allows you to sort by the file attributes:</p>
+
+ <dl>
+ <dt>By name</dt>
+
+ <dd>by filename (the default)</dd>
+
+ <dt>By size</dt>
+
+ <dd>by file size, in descending order</dd>
+
+ <dt>By date</dt>
+
+ <dd>by file modification time, in descending order</dd>
+
+ <dt>By mode</dt>
+
+ <dd>by file protection</dd>
+
+ <dt>By type</dt>
+
+ <dd>by filename suffix, e.g., the text beginning with
+ &ldquo;.&rdquo;</dd>
+
+ <dt>By user</dt>
+
+ <dd>by file owner's user-id</dd>
+
+ <dt>By group</dt>
+
+ <dd>by file owner's group-id</dd>
+ </dl>
+
+ <h3><a name="DF" id="DF">Show dot files</a></h3>
+
+ <p>If display/creation of hidden (dot) files/directories is
+ enabled, you can turn the feature on or off via this setting.</p>
+
+ <h3><a name="PZ" id="PZ">Pause when showing message</a></h3>
+
+ <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>
+
+ <h3><a name="LL" id="LL">Execution links</a></h3>
+
+ <p>If set to &ldquo;ALWAYS ON&rdquo;, Lynx will locally execute
+ commands contained inside any links. This can be <strong>HIGHLY
+ DANGEROUS</strong>, so it is recommended that they remain
+ &ldquo;ALWAYS OFF&rdquo; or &ldquo;FOR LOCAL FILES
+ ONLY&rdquo;.</p>
+
+ <h3><a name="TX" id="TX">Show transfer rate</a></h3>
+
+ <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:</p>
+
+ <ul>
+ <li>Do not show rate</li>
+
+ <li>Local directory sort order</li>
+
+ <li>Show dot files</li>
+
+ <li>Execution links</li>
+
+ <li>Pause when showing message</li>
+
+ <li>Show transfer rate</li>
+ </ul>
+
+ <h3><a name="MB" id="MB">Multi-bookmarks</a></h3>
+
+ <p>Manage multiple bookmark files:</p>
+
+ <ul>
+ <li>When OFF, the default bookmark file is used for the
+ &ldquo;v&rdquo;iew-bookmarks and &ldquo;a&rdquo;dd-bookmark
+ link commands.</li>
+
+ <li>If set to STANDARD, a menu of available bookmarks is always
+ invoked when you seek to view a bookmark file or add a link,
+ and you select the bookmark file by its letter token in that
+ menu.</li>
+
+ <li>If set to ADVANCED, you are instead prompted for the letter
+ of the desired bookmark file, but can enter &ldquo;=&rdquo; to
+ invoke the STANDARD selection menu, or RETURN for the default
+ bookmark file.</li>
+ </ul>
+
+ <h3><a name="BF" id="BF">Bookmark file</a></h3>
+
+ <p>Manage the default bookmark file:</p>
+
+ <ul>
+ <li>If non-empty and multi-bookmarks is OFF, it specifies your
+ default &ldquo;<a href="bookmark_help.html">Bookmark
+ file</a>&rdquo;.</li>
+
+ <li>If multi-bookmarks is STANDARD or ADVANCED, entering
+ &ldquo;B&rdquo; will invoke a menu in which you can specify
+ filepaths and descriptions of up to 26 bookmark files.</li>
+ </ul>
+
+ <p>The filepaths must be from your home directory and begin with
+ &ldquo;./&rdquo; if subdirectories are included (e.g.,
+ &ldquo;./BM/lynx_bookmarks.html&rdquo;).</p>
+
+ <p>Lynx will create bookmark files when you first
+ &ldquo;a&rdquo;dd a link, but any subdirectories in the filepath
+ must already exist.</p>
+
+ <h3><a name="AZ" id="AZ">Auto Session</a></h3>
+
+ <p>Lynx can save and restore useful information about your
+ browsing history. Use this setting to enable or disable the
+ feature.</p>
+
+ <h3><a name="SZ" id="SZ">Session file</a></h3>
+
+ <p>Define the file name where lynx will store user sessions. This
+ setting is used only when <em>Auto Session</em> is enabled.</p>
+
+ <h3><a name="VP" id="VP">Visited Pages</a></h3>
+
+ <p>This allows you to change the appearance of the <a href=
+ "visited_help.html">Visited Links Page</a> Normally it shows a
+ list, in reverse order of the pages visited. The popup menu
+ allows you these choices:</p>
+
+ <dl>
+ <dt><em>By First Visit</em>: The default appearance, shows the
+ pages based on when they were first visited. The list is shown
+ in reverse order, to make the current page (usually) at the top
+ of the list.</dt>
+
+ <dt><em>By First Visit Reversed</em> The default appearance,
+ shows the pages based on when they were first visited. The list
+ is shown in order, to make the current page (usually) at the
+ bottom of the list.</dt>
+
+ <dt><em>As Visit Tree</em> Combines the first/last visited
+ information, showing the list in order of the first visit, but
+ using the indentation level of the page immediately previous to
+ determine indentation of new entries. That gives a clue to the
+ order of visiting pages when moving around in the History or
+ Visited Pages lists.</dt>
+
+ <dt><em>By Last Visit</em> The default appearance, shows the
+ pages based on when they were last visited. The list is shown
+ in reverse order, to make the current page (usually) at the top
+ of the list.</dt>
+
+ <dt><em>By Last Visit Reversed</em> The default appearance,
+ shows the pages based on when they were last visited. The list
+ is shown in order, to make the current page (usually) at the
+ bottom of the list.</dt>
+ </dl>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/other_help.html b/lynx_help/keystrokes/other_help.html
new file mode 100644
index 0000000..8202bd3
--- /dev/null
+++ b/lynx_help/keystrokes/other_help.html
@@ -0,0 +1,196 @@
+<!-- $LynxId: other_help.html,v 1.19 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Help on Miscellaneous Lynx Commands</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "This is a table listing with brief descriptions miscellaneous Lynx commands, along with links to related topics">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#command_list">Summary of Commands</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="command_list" id="command_list">Summary of
+ Commands</a></h2>
+
+ <pre>
+ a - Places the link that you are currently positioned
+ on into a personal <a href=
+"bookmark_help.html">bookmark file</a>.
+
+ c - Allows you to send a mail message to the owner
+ or maintainer of the data that you are currently
+ viewing. In the case that no owner is known,
+ you cannot send a comment.
+
+ d - Downloads the file pointed to by the current link
+ and displays an option menu allowing the file to
+ be saved or transferred by configurable options.
+ Can also be used when positioned on a form SUBMIT
+ button to download the reply to a form submission.
+
+ e - Allows you to edit the current document if it is a
+ local file.
+
+ E - Allows you to edit the current link's URL (or ACTION) and
+ use that as a <em>goto</em> URL.
+
+ g - Allows you to enter any <a href=
+"http://www.ietf.org/rfc/rfc1738.txt">URL</a> or filename that
+ you wish to view, and then <em>goto</em> it.
+
+ G - Allows you to edit the current document's URL and use that
+ as a <em>goto</em> URL.
+
+ ? or H - Hypertext help to explain how to navigate in
+ <strong>Lynx</strong> and use its features.
+
+ i - Shows an index of files or subjects,
+ which may be changed in <em>lynx.cfg</em>.
+
+ j - Allows you to enter a short name to goto an URL,
+ if a jumps file has been defined. Press "?"
+ and ENTER to see the list of defined jump commands.
+
+ k - Shows a list of key mappings. Keys remapped in
+ "lynx.cfg" show up in this list.
+
+ l - Brings up a list of references (links) in the current
+ document, which can be used for rapid access to the
+ links in large documents.
+
+ m - Returns to the first screen and empties the
+ history stack.
+
+ p - Brings up a list of <a href=
+"print_help.html">print commands</a>.
+
+ o - Brings up a list of settable <a href=
+"option_help.html">options</a>.
+
+ q - Quits <strong>Lynx</strong>. (&ldquo;Q&rdquo; quits without asking)
+
+ / - Search for a string of characters in the current document
+ (case insensitive or case sensitive
+ depending on the <a href=
+"option_help.html">options</a> set).
+
+ s - Search through an external searchable indexed document.
+
+ n - Move to the next instance of a search string if you
+ have searched previously.
+
+ v - View a <a href=
+"bookmark_help.html">Bookmark file</a>.
+
+ V - Go to the <a href=
+"visited_help.html">Visited Links Page</a>
+
+ x - Force submission of form or link with no-cache.
+
+ z - Abort a network transfer in progress. If any partial
+ data has been transferred it will be displayed.
+
+ &lt;backspace&gt; - displays the <a href=
+"history_help.html">History Page</a>.
+
+ = - Show information about the file and link that you
+ are currently viewing.
+
+ \ - Toggles between viewing the HTML source of a
+ document and the rendered version of the document.
+
+ ! - Spawns your default operating system shell.
+
+ ' - Toggles "historical" vs minimal or valid comment parsing.
+ When historical, any close-angle-bracket will be treated
+ as a comment terminator, emulating the parsing bug in old
+ versions of Mosaic and Netscape, rather than validly
+ requiring pairs of two successive dashes to delimit
+ comments within the angle-brackets.
+
+ _ - Clears all authorization info for the current session. Can
+ be used when leaving one's terminal without ending the <strong>Lynx</strong>
+ session, to guard against someone else retrieving protected
+ documents with previously entered username/password info.
+ Note that any protected documents that are still in cache
+ can still be accessed.
+
+ ` - Toggles minimal or valid comment parsing. When minimal, any
+ two successive dashes followed by a close-angle-bracket will
+ be treated as a comment terminator, emulating the parsing bug
+ in Netscape v2.0. If historical comment parsing is set, that
+ will override minimal or valid comment parsing.
+
+ * - Toggles image_links mode on and off. When on, links will
+ be created for all images, including inlines.
+
+ @ - Toggles raw 8-bit translations or CJK mode on and off, only
+ for documents which does not specify character set explicitly.
+ Should be on when the document's charset matches the
+ display character set, and otherwise off so that 8-bit
+ characters will be translated by <strong>Lynx</strong> with respect to the
+ Assumed document charset, using approximations if necessary
+ (see <a href="option_help.html">options</a>).
+
+ [ - Toggles pseudo_inlines mode on and off. When on, inline
+ images which have no ALT string specified will have an
+ "[INLINE]" pseudo-ALT string inserted in the <strong>Lynx</strong> 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.
+
+ ] - Sends a HEAD request 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., <strong>Lynx</strong>
+ does not retrieve any previous server replies from its
+ cache. Note that for form submissions, http servers vary
+ in whether they will treat HEAD requests as valid and return
+ the CGI script's headers, or treat it as invalid and return
+ an error message.
+
+ " - Toggles valid or "soft" double-quote parsing. When soft,
+ a close-angle-bracket will serve as both a close-double-
+ quote and close-tag, emulating the parsing bug in old
+ versions of Mosaic and Netscape.
+
+ CTRL-R - Reloads the current document and resets the display.
+
+ CTRL-V - Switches to an alternative way of parsing HTML documents.
+ This may help to get a more readable rendering of some
+ documents with invalidly placed HTML tags, <a href=
+"option_help.html#tagsoup">more details</a>.
+
+ CTRL-W - Resets or cleans up the display.
+
+ CTRL-U - Clears text from an input field or prompt.
+
+ CTRL-G - Cancels any input prompt, mail message or data transfer.
+
+ CTRL-T - Toggles trace mode on and off.
+
+ ; - Views the <em>Lynx Trace Log</em> for the current session.
+
+ CTRL-K - Invokes the Cookie Jar Page.
+
+ numbers - <strong>Lynx</strong> offers other, advanced navigation features when
+ numbers are used to invoke the
+ <a href=
+"follow_help.html">Follow link (or goto link or page) number:</a> or
+ <a href=
+"follow_help.html#select-option">Select option (or page) number:</a>
+ prompts.
+</pre>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/print_help.html b/lynx_help/keystrokes/print_help.html
new file mode 100644
index 0000000..fb7738e
--- /dev/null
+++ b/lynx_help/keystrokes/print_help.html
@@ -0,0 +1,62 @@
+<!-- $LynxId: print_help.html,v 1.10 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Lynx Print Help and Configuration Summary</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Describe Lynx's print command, showing the different ways that a document's content can be saved as plain text, e.g., mail, local-file, user-defined.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#command_options">Print-command Options</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p>After entering the <code><strong>p</strong></code> command you
+ will be presented with a list of print options. In all cases the
+ file will be printed in ASCII format with the hypertext links
+ removed. The number of options depends on the level of printing
+ that your system allows.</p>
+
+ <h2><a name="command_options" id="command_options">Print-command
+ Options</a></h2>
+
+ <p>The following print options may be available:</p>
+
+ <dl>
+ <dt>Print to a local file:</dt>
+
+ <dd>This allows you to save the current file as ASCII text to
+ your local disk. You will be asked for a path and filename to
+ save the file to. If no path is given, the file will be saved
+ to the directory that you were in when you began
+ <strong>Lynx</strong>.</dd>
+
+ <dt>Print to the screen:</dt>
+
+ <dd>This option simply scrolls the entire document up the
+ screen and is intended for those who wish to capture the
+ document with their terminal.</dd>
+
+ <dt>Mail the file to yourself:</dt>
+
+ <dd>This option allows you to mail the file, in ASCII form, to
+ any valid e-mail address.</dd>
+
+ <dt>Custom print options:</dt>
+
+ <dd>Any number of custom print options may be defined in
+ <em>lynx.cfg</em>.</dd>
+ </dl>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/scrolling_help.html b/lynx_help/keystrokes/scrolling_help.html
new file mode 100644
index 0000000..b6f086b
--- /dev/null
+++ b/lynx_help/keystrokes/scrolling_help.html
@@ -0,0 +1,117 @@
+<!-- $LynxId: scrolling_help.html,v 1.13 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Lynx Scrolling/Paging Help Summary</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "This gives an overview and some details on Lynx's scrolling/paging commands. A diagram shows keypad shortcuts.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#paging_keys">Paging shortcuts</a></li>
+
+ <li><a href="#keypad_keys">Keypad shortcuts</a></li>
+
+ <li><a href="#control_keys">Control-characters</a></li>
+
+ <li><a href="#other_keys">Ordinary characters</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p>This gives an overview and some details on Lynx's
+ scrolling/paging commands. A diagram shows keypad shortcuts.</p>
+
+ <h2><a name="paging_keys" id="paging_keys">Paging shortcuts</a></h2>
+
+ <blockquote>
+ <pre>
+ + (or SPACE, - If the bottom of the screen informs you
+ or CTRL-F) that there is &ldquo;more&rdquo; to see, you may
+ move to the next page (Page-Down).
+
+ - (or b, - If you have moved down in a document, this
+ or CTRL-B) will bring you back up one page (Page-Up).
+</pre>
+ </blockquote>
+
+ <h2><a name="keypad_keys" id="keypad_keys">Keypad shortcuts</a></h2>
+
+ <p><strong>Lynx</strong> can use the digits 0-9 as movement
+ shortcuts. They are designed to work best when the <em>Num
+ Lock</em> on your keyboard is on, so that <strong>Lynx</strong>
+ can translate the numbers of your keypad into <a href=
+ "movement_help.html">movement commands</a>:</p>
+
+ <blockquote>
+ <pre>
+ 9 - page up
+ 8 - up arrow
+ 7 8 9 7 - moves to the top of a document
+ \|/ 6 - right arrow
+ 4 - 5 - 6 5 - nothing
+ /|\ 4 - left arrow
+ 1 2 3 3 - page down
+ 2 - down arrow
+ 1 - moves to the end of a document
+</pre>
+ </blockquote>
+
+ <h2><a name="control_keys" id=
+ "control_keys">Control-characters</a></h2>
+
+ <blockquote>
+ <pre>
+ CTRL-A (or Find) - This Control key, and Function key synonym,
+ brings you back to the first page of the
+ current document (Home).
+
+ CTRL-E (or Select) - This Control key, and Function key synonym,
+ takes you to the last page of the current
+ document (End).
+
+ CTRL-N (or Remove) - This Control key, and Function key synonym,
+ moves you forward two lines in the current
+ document (Down-Two).
+
+ CTRL-P (or Insert) - This Control key, and Function key synonym,
+ moves you back two lines in the current
+ document (Up-Two).
+</pre>
+ </blockquote>
+
+ <h2><a name="other_keys" id="other_keys">Ordinary characters</a></h2>
+
+ <blockquote>
+ <pre>
+ ) - Moves you forward half a page in the current
+ document (Down-Half).
+
+ ( - Moves you back half a page in the current
+ document (Up-Half).
+
+ ^ - Go to the first link on the current line.
+
+ $ - Go to the last link on the current line.
+
+ &lt; - Go to the previous link in the current column.
+
+ &gt; - Go to the next link in the current column.
+
+ # - Jumps you to the pseudo Toolbar or Banner if
+ present in the current document. Use left-arrow
+ to return from there to your previous position
+ in the document.
+</pre>
+ </blockquote>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/test_display.html b/lynx_help/keystrokes/test_display.html
new file mode 100644
index 0000000..adbe3ef
--- /dev/null
+++ b/lynx_help/keystrokes/test_display.html
@@ -0,0 +1,82 @@
+<!-- $LynxId: test_display.html,v 1.12 2021/07/01 21:02:38 tom Exp $ -->
+<!-- do not use tidy for this page -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Quick test for identifying display character set</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Display a test-page for common problems with Lynx's display character set and/or locale problems.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#configuration">Configuration</a></li>
+
+ <li><a href="#test_screen">Test-screen</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p>Display a test-page for common problems with Lynx's display
+ character set and/or locale problems.</p>
+
+ <h2><a name="configuration" id="configuration">Configuration</a></h2>
+
+ <p>If you see several letters instead of a single &ndash; your
+ promised display charset does not support this character so "7
+ bit approximation" is in effect. If you see any single letter
+ which is unexpected, you have incorrect <strong>Lynx</strong>
+ settings.</p>
+
+ <blockquote>
+ <p><em>Press &ldquo;o&rdquo; for Options menu and change
+ "Display character set"</em>.<br>
+ Try again if necessary.</p>
+ </blockquote>
+
+ <p>When you are satisfied save your changes in Options menu,
+ thanks.</p>
+
+ <h2><a name="test_screen" id="test_screen">Test-screen</a></h2>
+
+ <p>This is only a quick test to see obvious problems.</p>
+
+ <pre>
+
+0x00A9 &copy; # COPYRIGHT SIGN
+
+0x00C7 &Ccedil; # LATIN CAPITAL LETTER C WITH CEDILLA
+
+0x00DC &Uuml; # LATIN CAPITAL LETTER U WITH DIAERESIS
+
+0x00D1 &Ntilde; # LATIN CAPITAL LETTER N WITH TILDE
+
+0x0107 &#263; # LATIN SMALL LETTER C WITH ACUTE
+0x0108 &#264; # LATIN CAPITAL LETTER C WITH CIRCUMFLEX
+0x010C &#268; # LATIN CAPITAL LETTER C WITH CARON
+
+0x03BB &lambda; # GREEK SMALL LETTER LAMDA
+
+0x041B &#1051; # CYRILLIC CAPITAL LETTER EL
+0x042E &#1070; # CYRILLIC CAPITAL LETTER YU
+0x043B &#1083; # CYRILLIC SMALL LETTER EL
+0x044E &#1102; # CYRILLIC SMALL LETTER YU
+
+0x2026 &hellip; # HORIZONTAL ELLIPSIS
+0x2122 &trade; # TRADE MARK SIGN
+
+0x255D &#9565; # BOX DRAWINGS DOUBLE UP AND LEFT
+0x255E &#9566; # BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE
+
+0xFB01 &#64257; # LATIN SMALL LIGATURE FI
+</pre>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/visited_help.html b/lynx_help/keystrokes/visited_help.html
new file mode 100644
index 0000000..14a83c1
--- /dev/null
+++ b/lynx_help/keystrokes/visited_help.html
@@ -0,0 +1,63 @@
+<!-- $LynxId: visited_help.html,v 1.12 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Help on the Visited Links Page</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Lynx provides an alternative to its history page, the visited-links page which highlights those which are of most interest.">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li><a href="#overview">Overview</a></li>
+
+ <li><a href="#navigation">Navigation</a></li>
+
+ <li><a href="#configuration">Configuration</a></li>
+ </ul>
+ </div>
+
+ <h2><a name="overview" id="overview">Overview</a></h2>
+
+ <p><strong>Lynx</strong>'s <em>Visited Links Page</em> displays
+ all of the links that you have traveled through during the
+ current Lynx session, except for any temporary menu or list
+ files, bookmark files, or any documents associated with POST
+ content. The VLINKS keystroke command for invoking this page
+ normally is mapped to uppercase &ldquo;<em>V</em>&rdquo;. The
+ list of Visited Links is normally in order of recency (most
+ recently visited links first), without repetitions in the list if
+ a link was visited more than once during the session (unless the
+ URLs differ due to appended fragments), and is supplementary to
+ the <a href="history_help.html">History Page</a>.</p>
+
+ <h2><a name="navigation" id="navigation">Navigation</a></h2>
+
+ <p>You may <a href="movement_help.html">select</a> any link on
+ the Visited Links Page to retrieve a document that you had
+ previously visited, or you can use this list to save such links
+ in your <a href="bookmark_help.html">bookmark files</a>, or to
+ <a href="../Lynx_users_guide.html#RemoteSource">Download</a>
+ them.</p>
+
+ <p>In contrast to the History Page, the Visited Links Page
+ includes any links which were retrieved for
+ &ldquo;<em>d</em>&rdquo;ownloading or were passed to helper
+ applications, i.e., not just the links that were rendered and
+ displayed by Lynx, itself.</p>
+
+ <h2><a name="configuration" id="configuration">Configuration</a></h2>
+
+ <p>You may change the appearance of the Visited Links Page via a
+ popup menu on that page (which also appears on the <a href=
+ "option_help.html#VP">Options Menu</a>). The menu allows you to
+ choose whether to view the list ordered by the first or last
+ visit, forward or reversed &ndash; or a mixture (a tree
+ structure).</p>
+</body>
+</html>
diff --git a/lynx_help/keystrokes/xterm_help.html b/lynx_help/keystrokes/xterm_help.html
new file mode 100644
index 0000000..84ac3df
--- /dev/null
+++ b/lynx_help/keystrokes/xterm_help.html
@@ -0,0 +1,52 @@
+<!-- $LynxId: xterm_help.html,v 1.11 2021/07/01 21:02:38 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>X Terminal Help</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "This outlines what is meant by an X terminal, for gopher support, i.e., something which can display images">
+</head>
+<body>
+ <div class="nav">
+ <ul>
+ <li>X Terminal Help</li>
+
+ <li>Notes</li>
+ </ul>
+ </div>
+
+ <h2>X Terminal Help</h2>
+
+ <p>An X terminal is an electronic display terminal that
+ communicates with a host computer system using the X Window
+ protocol developed at the Massachusetts Institute of
+ Technology.</p>
+
+ <p>The X Window protocol allows a program running on the host
+ computer system to display both formatted text and graphics on
+ the X terminal. Since the X Window protocol is defined to work
+ over any TCP/IP network, X terminals connected to the Internet
+ can be connected to hosts located anywhere on the Internet.</p>
+
+ <p>Personal computers (including both PCs and Macintoshes) can
+ execute programs, usually called X servers, that make them act
+ like X Window terminals and are frequently used as X
+ terminals.</p>
+
+ <h2>Notes</h2>
+
+ <dl>
+ <dt>Terminology</dt>
+
+ <dd>The terminology used to describe processes associated with
+ X terminals can be confusing. An X terminal is also known as an
+ "X display server," and the program running on the host
+ computer is usually known as the "X client."</dd>
+ </dl>
+</body>
+</html>
diff --git a/lynx_help/lynx-dev.html b/lynx_help/lynx-dev.html
new file mode 100644
index 0000000..ebf417c
--- /dev/null
+++ b/lynx_help/lynx-dev.html
@@ -0,0 +1,101 @@
+<!-- $LynxId: lynx-dev.html,v 1.20 2021/07/01 21:02:17 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>Lynx-Dev Discussion List</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Summarizes the Lynx development, provides links to the development site and mailing list. The mailing list is moderated and archived.">
+</head>
+<body>
+ <blockquote>
+ <p>[ <a href=
+ "http://mail.gnu.org/mailman/listinfo/lynx-dev/">Lynx-Dev
+ Archive</a> | <a href="about_lynx.html">About Lynx</a> ]</p>
+ </blockquote>
+
+ <h2>The Lynx Development Process</h2>
+
+ <p><strong>Lynx</strong> is maintained and improved by an
+ international co-operative of volunteers. Newcomers are welcome
+ to join the group: you need not be a super programmer, but you
+ should be prepared to listen and learn, as well as to contribute
+ patches if you can. Since everyone is a volunteer, you will
+ usually be expected to try to implement any suggestions you
+ make.</p>
+
+ <h2>Lynx-Dev Discussion List</h2>
+
+ <p>The developers communicate through a mailing list &mdash; see
+ below for details &mdash; which is open to interested users as
+ well as programmers. Topics include fixing bugs, increasing
+ <strong>Lynx</strong>'s tools and powers, meeting the
+ ever-changing demands of the Internet and porting
+ <strong>Lynx</strong> to new systems.</p>
+
+ <p>Anyone may read what has been said on the list by visiting
+ <a href="http://mail.gnu.org/mailman/listinfo/lynx-dev/">the
+ Archive</a>.</p>
+
+ <h2>Development Versions of Lynx</h2>
+
+ <p>Besides <em>releases</em>, which are stable versions of
+ <strong>Lynx</strong> which come out once or twice a year and can
+ be obtained from <a href=
+ "https://lynx.invisible-island.net/release/">the release
+ site</a>, there are <em>development</em> versions, which are
+ experimental &mdash; though usually stable enough to use &mdash;
+ and appear every few weeks, depending on current activity.</p>
+
+ <p>You can find the latest <em>development</em> version of
+ <strong>Lynx</strong> by visiting <a href=
+ "https://lynx.invisible-island.net/current/">the development
+ site</a>.</p>
+
+ <h2>Subscribing to Lynx-Dev</h2>
+
+ <p>If you are interested in joining the <strong>Lynx</strong>
+ mailing list, send e-mail to <a href=
+ "mailto:lynx-dev-request@nongnu.org?subject=subscribe">&nbsp;lynx-dev-request@nongnu.org</a>
+ with "subscribe" as the subject line.</p>
+
+ <p>You will need to answer one follow-up question to confirm you
+ want to subscribe. Mailman will then enroll you and send all
+ messages which you address to <em>lynx-dev@nongnu.org</em> to all
+ subscribers; you will also receive all messages sent by other
+ subscribers.</p>
+
+ <h2>Unsubscribing from Lynx-Dev</h2>
+
+ <p>To <em>unsubscribe</em>, send an e-mail to <a href=
+ "mailto:lynx-dev-request@nongnu.org?subject=unsubscribe">&nbsp;lynx-dev-request@nongnu.org</a>
+ with "unsubscribe" as the subject line.</p>
+
+ <h2>Casual Inquiries</h2>
+
+ <p>Anyone may ask a question or offer a comment by sending e-mail
+ to <a href="mailto:lynx-dev@nongnu.org">&nbsp;the list</a>. Since
+ all subscribers are volunteers, you depend on their goodwill and
+ will be more likely to get a response if you give the e-mail a
+ meaningful &ldquo;Subject&rdquo; and include details of your
+ version of <strong>Lynx</strong>, hardware and software. You can
+ check the Archive to find any responses.</p>
+
+ <p>Messages from non-subscribers are not immediately distributed
+ to avoid spam. Usually, if your message appears genuine, it will
+ be retrieved from the pile headed for the wastebasket within a
+ day or so and distributed to the list. For best results,
+ subscribe as described above.</p>
+
+ <h2>The Lynx-Dev Archive</h2>
+
+ <p>Messages posted to lynx-dev are archived in html format so
+ that you can view them using <strong>Lynx</strong>: go to the
+ <a href="http://mail.gnu.org/mailman/listinfo/lynx-dev/">Mail
+ Archive</a>.</p>
+</body>
+</html>
diff --git a/lynx_help/lynx_help_main.html b/lynx_help/lynx_help_main.html
new file mode 100644
index 0000000..f24878e
--- /dev/null
+++ b/lynx_help/lynx_help_main.html
@@ -0,0 +1,180 @@
+<!-- $LynxId: lynx_help_main.html,v 1.56 2021/07/01 21:02:17 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>The Lynx Help Page &ndash; quick-links and detailed
+ documentation</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "This is the top-level page for Lynx's help-files, quick links, external resources and detailed user-documentation.">
+</head>
+<body>
+ <h2>Lynx help files (usually in your local directories):</h2>
+
+ <p>These <strong>Lynx</strong> documents are part of your local
+ configuration:</p>
+
+ <ul>
+ <li><a href="Lynx_users_guide.html">Lynx Users Guide</a>
+ &mdash; complete account of all Lynx features</li>
+
+ <li><a href="keystrokes/keystroke_help.html">Key-stroke
+ Commands</a> &mdash; quick outline of what various keys do</li>
+
+ <li><a href="keystrokes/edit_help.html">Line Editor</a> &mdash;
+ when entering URLs etc</li>
+
+ <li><a href="lynx_url_support.html">Supported URLs</a> &mdash;
+ how Lynx handles various types of URL</li>
+
+ <li><a href="about_lynx.html">About Lynx</a> &mdash; credits,
+ copyright etc</li>
+
+ <li><a href="lynx-dev.html">About Lynx-Dev</a> &mdash; the
+ developers &amp; how to contact them</li>
+ </ul>
+
+ <h2>Other sources of Lynx help:</h2>
+
+ <p>The <strong>Lynx</strong> configuration guide may also be
+ local.</p>
+
+ <ul>
+ <li><a href=
+ "https://lynx.invisible-island.net/release/breakout/lynx_help/cattoc.html">
+ lynx.cfg options</a> &mdash; a reference for advanced
+ configurations</li>
+
+ <li><a href=
+ "https://lynx.invisible-island.net/release/breakout/docs/">lynx
+ documentation</a> &mdash; supplementary documentation</li>
+
+ <li><a href=
+ "http://www.chass.utoronto.ca/%7Epurslow/lhfb.html">Lynx Help
+ for Beginners</a> &mdash; quick help on many common
+ problems</li>
+
+ <li><a href="http://leb.net/blinux/blynx/">Blynx</a> &mdash;
+ Speech-Friendly Help for the visually impaired</li>
+ </ul>
+
+ <h2>World Wide Web Consortium documents:</h2>
+
+ <ul>
+ <li>HTML &mdash; <a href="http://www.w3.org/TR/html51/">5.1</a>
+ &mdash; <a href="http://www.w3.org/TR/REC-html40/">4.0</a>
+ &mdash; <a href="http://www.w3.org/TR/REC-html32">3.2</a>
+ &mdash; <a href=
+ "http://www.w3.org/MarkUp/html3/Contents.html">3.0</a> &mdash;
+ <a href=
+ "http://www.w3.org/MarkUp/html-spec/html-spec_toc.html">2.0</a></li>
+
+ <li>HTTP &mdash; <a href="http://www.w3.org/Protocols/">1.1</a>
+ &mdash; <a href=
+ "http://www.isi.edu/in-notes/rfc1945.txt">1.0</a></li>
+
+ <li>XHTML &mdash; <a href=
+ "http://www.w3.org/TR/xhtml1/">1.0</a></li>
+
+ <li><a href="http://www.w3.org/Addressing/">Web Naming &amp;
+ Addressing Overview: URIs, URLs etc</a></li>
+
+ <li><a href="http://www.w3.org/International/">HTML
+ Internationalization</a></li>
+
+ <li><a href="http://www.w3.org/">WWW Consortium: home page</a></li>
+ </ul>
+
+ <h2>Help with HTML:</h2>
+
+ <ul>
+ <li><a href="http://www.htmlhelp.com/reference/html40/">HTML
+ 4.0 Reference</a></li>
+
+ <li><a href=
+ "http://www.w3schools.com/html/default.asp">W3Schools</a></li>
+
+ <li><a href="http://www.htmlgoodies.com/primers/html/">HTML
+ Goodies</a></li>
+
+ <li><a href="http://www.htmlcodetutorial.com/">HTML Code
+ Tutorial</a></li>
+
+ <li><a href=
+ "http://www.simplehtmlguide.com/cheatsheet.php">HTML Cheat
+ Sheet &ndash; A Simple Guide to HTML</a></li>
+ </ul>
+
+ <h2>HTML validation services:</h2>
+
+ <ul>
+ <li><a href="http://validator.w3.org/">W3C HTML Validation
+ Service</a></li>
+
+ <li><a href="http://www.htmlhelp.com/tools/validator/">WDG HTML
+ Validator</a></li>
+ </ul>
+
+ <h2>Other browsing software:</h2>
+
+ <ul>
+ <li><a href="http://wget.addictivecode.org/">GNU wget</a>
+ &mdash; powerful &amp; flexible non-interactive downloader</li>
+
+ <li><a href="http://www.pavuk.org/">Pavuk</a> &mdash; powerful
+ &amp; an even more-featured downloader</li>
+
+ <li><a href="http://curl.haxx.se/">cURL</a> &mdash;
+ non-interactive downloader which supports HTTPS</li>
+
+ <li><a href="http://www.xach.com/snarf/">snarf</a> &mdash;
+ small simple 1-file non-interactive downloader</li>
+ </ul>
+
+ <h2>Historical interest</h2>
+
+ <ul>
+ <li><a href=
+ "http://web.archive.org/web/2005050785333/http://archive.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html">
+ NCSA Mosaic</a></li>
+ </ul>
+
+ <h2>Search engines:</h2>
+
+ <p>These work with <strong>Lynx</strong> as of 2014/01/10:</p>
+
+ <ul>
+ <li><a href="http://www.ask.com/">Ask.com</a></li>
+
+ <li><a href="http://www.baidu.com/">Baidu</a> (Chinese)</li>
+
+ <li><a href="http://www.bing.com/">Bing</a></li>
+
+ <li><a href="http://www.dogpile.com/">Dogpile</a></li>
+
+ <li><a href="http://labs.goo.ne.jp/">goo</a> (Japanese)</li>
+
+ <li><a href="http://www.google.com/">Google</a></li>
+
+ <li><a href="http://hakia.com/">Hakia</a></li>
+
+ <li><a href="http://www.icerocket.com/">IceRocket</a></li>
+
+ <li><a href="http://www.indeed.com/">Indeed</a></li>
+
+ <li><a href="http://www.lexxe.com/">Lexxe</a></li>
+
+ <li><a href="http://www.rambler.ru/">Rambler</a> (Russian)</li>
+
+ <li><a href="http://www.search.com/">Search.com</a></li>
+
+ <li><a href="http://www.webcrawler.com/">WebCrawler</a></li>
+
+ <li><a href="http://www.yahoo.com/">Yahoo!</a></li>
+ </ul>
+</body>
+</html>
diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html
new file mode 100644
index 0000000..52ba2fb
--- /dev/null
+++ b/lynx_help/lynx_url_support.html
@@ -0,0 +1,796 @@
+<!-- $LynxId: lynx_url_support.html,v 1.37 2021/07/01 21:02:17 tom Exp $ -->
+<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN">
+<html>
+<head>
+ <meta name="generator" content=
+ "HTML Tidy for HTML5 for Linux version 5.6.0">
+ <title>URL Schemes Supported in Lynx</title>
+ <link rev="made" href="mailto:lynx-dev@nongnu.org">
+ <meta http-equiv="Content-Type" content=
+ "text/html; charset=us-ascii">
+ <meta name="description" content=
+ "Enumerate, describe and provide examples of Lynx's URL support on Unix and VMS. Lynx supports both Web standards and extensions.">
+</head>
+<body>
+ <blockquote>
+ <p><em>[</em><a href="#http_url">http, https</a> <em>|</em>
+ <a href="#telnet_url">telnet, tn3270, rlogin</a> <em>|</em>
+ <a href="#gopher_url">gopher</a> <em>|</em> <a href=
+ "#file_url">file</a> <em>|</em> <a href="#ftp_url">ftp</a>
+ <em>|</em> <a href="#wais_url">wais</a> <em>|</em> <a href=
+ "#news_url">news, nntp, snews</a> <em>|</em> <a href=
+ "#newspost_url">newspost, newsreply, snewspost, snewsreply</a>
+ <em>|</em> <a href="#mailto_url">mailto</a> <em>|</em> <a href=
+ "#finger_url">finger</a> <em>|</em> <a href="#cso_url">cso</a>
+ <em>|</em> <a href="#bibp_url">bibp</a> <em>|</em> <a href=
+ "#exec_url">lynxexec, lynxprog</a> <em>|</em> <a href=
+ "#cgi_url">lynxcgi</a><em>|</em> <a href="#ncftp_url">NcFTP</a>
+ <em>|</em> <a href="#internal_url">internal</a><em>]</em></p>
+ </blockquote>
+
+ <h1><em>URL Schemes Supported in Lynx</em>
+ </h1>
+
+ <p><strong>Lynx</strong> handles a number of URL types, that are
+ enumerated below. For more details about URLs (Uniform Resource
+ Locators) see <em>RFC1738</em>:</p>
+
+ <ul>
+ <li><a href=
+ "http://www.w3.org/Addressing/rfc1738.txt">http://www.w3.org/Addressing/rfc1738.txt</a></li>
+
+ <li><a href=
+ "ftp://ftp.rfc-editor.org/in-notes/rfc1738.txt">ftp://ftp.rfc-editor.org/in-notes/rfc1738.txt</a></li>
+ </ul>
+
+ <p><strong>Lynx</strong> resolves partial or relative URLs in
+ documents with respect to the BASE if one was specified,
+ otherwise with respect to the document's absolute URL, using the
+ rules described in <em>RFC1808</em>:</p>
+
+ <ul>
+ <li><a href=
+ "http://www.w3.org/Addressing/rfc1808.txt">http://www.w3.org/Addressing/rfc1808.txt</a></li>
+
+ <li><a href=
+ "ftp://ftp.rfc-editor.org/in-notes/rfc1808.txt">ftp://ftp.rfc-editor.org/in-notes/rfc1808.txt</a></li>
+ </ul>
+
+ <p>and in subsequent drafts of the <em>IETF</em>:</p>
+
+ <ul>
+ <li><a href=
+ "https://web.archive.org/web/20130116065936/http://ftp.ics.uci.edu/pub/ietf/uri/">
+ Uniform Resource Identifiers (URI) Working Group</a></li>
+ </ul>
+
+ <p>When entering a URL on the command line to be used as the
+ <em>startfile</em>, or at the prompt for a
+ &ldquo;<em>g</em>&rdquo;oto entry, a partial host field can be
+ used and the scheme field can be omitted if the scheme and fully
+ qualified domain name can be constructed internally by using the
+ URL_DOMAIN_PREFIXES and URL_DOMAIN_SUFFIXES definitions in the
+ <strong>Lynx</strong> configuration file. See the explanation of
+ those definitions and their use in your <em>lynx.cfg</em>.</p>
+
+ <p>For example, <em>wfbr</em> will be treated as
+ <em>http://www.wfbr.edu/</em>, and <em>wfbr/dir/lynx</em> will be
+ treated as <em>http://www.wfbr.edu/dir/lynx</em>, but
+ <em>gopher.wfbr.edu/11/_fileserv/_lynx</em> will be treated as
+ <em>gopher://gopher.wfbr.edu/11/_fileserv/_lynx</em>.</p>
+
+ <p>For files or directories on the local host, a tilde
+ (<em>~</em>) is expanded to the path of the account's login
+ directory, e.g., <em>~/foo</em> will be expanded to
+ <em>file://localhost/your/login/directory/foo</em>. The tilde
+ expansion is done homologously on Unix and VMS.</p>
+
+ <p>On VMS, <strong>Lynx</strong> also will expand any file or
+ directory spec recognizable to DCL into a valid URL, e.g.,
+ <em>[]</em> will be expanded to
+ <em>file://localhost/current/default/directory</em>.</p>
+
+ <p>These expansions are <em>SOLELY</em> for <em>startfile</em> or
+ &ldquo;<em>g</em>&rdquo;oto entries! Any partial or relative URLs
+ within HTML documents are resolved according to the rules
+ specified in RFC1808 and subsequent IETF drafts.</p>
+
+ <hr>
+
+ <h2><a name="http_url" id="http_url">The <em>http</em> and
+ <em>https</em> URLs:</a></h2>
+
+ <p><strong>Lynx</strong> handles http URLs exactly as specified
+ in RFC1738. The format is:</p>
+
+ <pre>
+ <em>http://host:port/path?searchpart#fragment</em>
+</pre>
+ <p>where <em>:port</em> is optional and defaults to <em>:80</em>,
+ <em>/path</em> if present is a slash-separated series of symbolic
+ elements, and <em>?searchpart</em> if present is the query for an
+ ISINDEX search or the content of a FORM with METHOD="GET". The
+ <em>#fragment</em> field if present indicates a location in the
+ document to seek for display, based on a NAME-ed anchor or an ID
+ attribute within the document, and is technically an instruction
+ rather than part of the URL. <strong>Lynx</strong> will treat ID
+ attributes as NAME-ed anchors for all tags in the BODY of a
+ document which can correspond to positions in the rendering of
+ the document.</p>
+
+ <p>The https URL has the same format, but the default port is
+ <em>:443</em>.</p>
+
+ <p><strong>Lynx</strong> relies for https support on external
+ libraries (OpenSSL or GnuTLS) whose capabilities have evolved
+ over time. In turn, those libraries may depend upon external
+ resources for verifying SSL certificates. For instance,
+ certification revocation may be provided via the Online
+ Certificate Status Protocol (OCSP) which is an external service.
+ Without this facility, <strong>Lynx</strong> may not warn about
+ websites using revoked SSL certificates.</p>
+
+ <hr>
+
+ <h2><a name="telnet_url" id="telnet_url">The <em>telnet</em>,
+ <em>tn3270</em>, and <em>rlogin</em> URLs:</a></h2>
+
+ <p>A <em>telnet</em> URL generally results in
+ <strong>Lynx</strong> spawning a telnet session.
+ <strong>Lynx</strong> implements the complete telnet URL scheme,
+ i.e.:</p>
+
+ <pre>
+ <em>telnet://user:password@host:port</em>
+</pre>
+ <p>The <em>user</em> and/or <em>:password</em> fields may be
+ omitted, and the <em>@</em> should be omitted if neither is
+ present. The port defaults to <em>:23</em> when omitted in the
+ URL.</p>
+
+ <p>A <em>tn3270</em> or <em>rlogin</em> URL is specified
+ equivalently, and similarly spawns a tn3270 or rlogin session.
+ The actual behavior is dependent on the TCP-IP software installed
+ on the local and target hosts.</p>
+
+ <p>It is unwise to include the <em>:password</em> field except
+ for URLs which point to anonymous or other public access
+ accounts, and for most TCP-IP software you will be prompted for a
+ password whether or not one was included in the URL.</p>
+
+ <hr>
+
+ <h2><a name="gopher_url" id="gopher_url">The <em>gopher</em>
+ URL:</a></h2>
+
+ <p>The gopher URL takes the form:</p>
+
+ <pre>
+ <em>gopher://host:port/gopher-path</em>
+</pre>
+ <p>where <em>:port</em> is optional and defaults to <em>:70</em>,
+ and the <em>/gopher-path</em> is opaque (not fully equivalent to
+ the slash-separated series of symbolic elements of http paths) as
+ explained in RFC1738. Typically, the gopher-path consists of a
+ <a href=
+ "keystrokes/gopher_types_help.html"><em>gophertype</em></a>
+ indicating the file or service type (e.g., <em>0</em> or
+ <em>I</em> for plain text or an image, respectively, <em>7</em>
+ for a search, or <em>1</em> for a directory), followed by a
+ platform-specific <em>selector</em>. Any reserved characters in
+ the selector should be hex escaped (<em>%hh</em>), including
+ slashes, although hex escaping of slashes is not required by
+ <strong>Lynx</strong> in gopher URLs.</p>
+
+ <p><strong>Lynx</strong> does not overtly support the gopher+
+ protocol, and does not represent itself as gopher+ capable when
+ communicating with gopher servers. <strong>Lynx</strong> might
+ transmit any (hex-escaped-tab-separated) extended gopher+ fields
+ in a URL if an author included them in a document, but is likely
+ to mishandle what the gopher server returns in such cases, and
+ would not generate and transmit them itself. For pre-formed URLs
+ to submit gopher searches, it may be better to use a <em>?</em>
+ rather than hex-escaped tab (<em>%09</em>) as the separator for
+ the <em>searchpart</em> in the <em>selector</em>, e.g.:<br>
+ <em>gopher://gopher.wfbr.edu/77/_shell/search.shell%20/_shell/walker?lynx*</em>
+ <strong>Lynx</strong> will handle the <em>%09</em> if you use
+ that instead of <em>?</em>, but other WWW clients may mishandle
+ it.</p>
+
+ <p>For the <em>gophertype</em> which signifies HTML (<em>h</em>),
+ if the <em>selector</em> begins with <em>GET%20/</em>
+ <strong>Lynx</strong> will convert the gopher URL to an http URL,
+ e.g.:<br></p>
+
+ <pre>
+<em>gopher://www.wfbr.edu:80/hGET%20/</em>
+</pre>
+ <p>will become:<br></p>
+
+ <pre>
+<em>http://www.wfbr.edu/</em>
+</pre>
+ <p>The port field will be retained if it is not <em>:80</em>, and
+ will default to <em>:70</em> if it was defaulted originally.
+ These conventions were adopted during development of the
+ University of Minnesota gopher software to facilitate the
+ offering of links to MIME-capable http servers in the listings
+ returned by gopher servers, but should be considered Lynxisms and
+ UMN Gopherisms.</p>
+
+ <hr>
+
+ <h2><a name="file_url" id="file_url">The <em>file</em> URL:</a></h2>
+
+ <p>The file URL is used to retrieve files or generate a directory
+ listing on the local host. The host field can be
+ <em>localhost</em> or a domain name for the local host:<br></p>
+
+ <pre>
+<em>file://localhost/path</em>
+</pre>
+ <p>If you do not use <em>localhost</em> or a domain name for the
+ local host, <strong>Lynx</strong> will substitute <em>ftp://</em>
+ for <em>file://</em> and treat it as an ftp URL.</p>
+
+ <p>The <em>/path</em> is treated as originating at the root,
+ unless you include a tilde (<em>~</em>), e.g.:</p>
+
+ <pre>
+ <em>file://localhost/~/foo</em> will be converted to:
+ <em>file://localhost/your/login/directory/foo</em>
+</pre>
+ <p>The latter feature is a Lynxism, is done homologously on Unix
+ and VMS, and should be used ONLY in local documents intended for
+ <strong>Lynx</strong>.</p>
+
+ <p>On VMS, the first element of the path, if not a tilde, is
+ assumed to be a device, e.g.:</p>
+
+ <pre>
+ <em>file://localhost/www_root/directory/filename.suffix</em>
+</pre>
+ <p>should be used for:
+ <em>www_root:[directory]filename.suffix</em><br>
+ If you are unsure how to specify a file URL in local documents on
+ VMS, invoke <strong>Lynx</strong> with the desired file or
+ directory as the <em>startfile</em> using any spec acceptable to
+ DCL, and then use the <em>showinfo</em> command (<em>=</em>) to
+ see the file URL which <strong>Lynx</strong> created for it.</p>
+
+ <hr>
+
+ <h2><a name="ftp_url" id="ftp_url">The <em>ftp</em> URL:</a></h2>
+
+ <p>The ftp URL has the general format:</p>
+
+ <pre>
+ <em>ftp://host:port/path;type=[D,I, or A]</em>
+ <em>ftp://username@host:port/path;type=[D,I, or A]</em>
+</pre>
+ <p>The default port is <em>:21</em> and the default
+ <em>username</em> is <em>anonymous</em>. If <em>username</em> is
+ included, <strong>Lynx</strong> will prompt you for the password.
+ For anonymous ftp, <strong>Lynx</strong> uses your
+ <em>personal_mail_address</em> (user@host) as the
+ <em>password</em> if it has been defined via the
+ &ldquo;<em>o</em>&rdquo;ptions menu. Otherwise,
+ <strong>Lynx</strong> uses the dummy password <em>WWWUser</em>.
+ (A password can also be embedded in the URL, by replacing
+ <em>username</em> with <em>username:password</em>. This is
+ strongly discouraged for &ldquo;real&rdquo; passwords that must
+ be kept secret, since URLs with the completely unencrypted
+ <em>password</em> may show up on the screen, in HISTORY and LIST
+ pages etc., and may even become visible to remote sites for
+ example through Referer headers.) Do not include the <em>@</em>
+ if neither <em>username</em> nor <em>:password</em> is
+ included.</p>
+
+ <p>The <em>;type=</em> parameter can be used with value
+ <em>D</em>, <em>I</em>, or <em>A</em> to force handling of the
+ URL as, respectively, a directory listing, binary file, or ASCII
+ file. The <strong>Lynx</strong> ftp gateway normally determines
+ this itself, but the parameter can be used if the internal
+ procedure draws an incorrect inference about the nature of the
+ ftp URL.</p>
+
+ <p>The <em>/path</em> is treated according to RFC1738 for VMS and
+ VM/CMS ftp servers. The lead slash (<em>/</em>) is treated purely
+ as a separator, not as a designator for the root, and the
+ <em>path</em> string if present is treated as in or under the
+ login directory. For VMS ftp servers, if you wish to have the
+ first element treated as a device rather than file or
+ subdirectory name, begin it with a hex-escaped slash
+ (<em>%2f</em>), e.g.:</p>
+
+ <pre>
+ <em>ftp://user@myhost/%2fsys$common/syshlp</em>
+</pre>
+ <p>can be used for a listing of sys$common:[syshlp]<br>
+ Also, on VM/CMS ftp servers, if the <em>path</em> string begins
+ with <em>vmsysu%3a</em> it receives special handling as an SFS
+ path, e.g.:</p>
+
+ <pre>
+ <em>ftp://ubvm.cc.buffalo.edu/vmsysu%3alistserv.webshare</em>
+</pre>
+ <p>For Unix and Unix-emulation ftp servers, RFC1738 is not
+ respected and the lead slash is treated as the root, i.e., the
+ <em>/path</em> is handled equivalently to that in file URLs. The
+ distinction is irrelevant for anonymous ftp, but matters when
+ using ftp for non-anonymous accounts. If you are using ftp with a
+ Unix server and do wish to get a listing of the login directory
+ or have the <em>path</em> string treated as a file or path under
+ the login directory, include a tilde (<em>~</em>) as for <a href=
+ "#file_url">file</a> URLs, e.g.:</p>
+
+ <pre>
+ <em>ftp://user@myhost/~</em>
+</pre>
+
+ <hr>
+
+ <h2><a name="wais_url" id="wais_url">The <em>wais</em> URL:</a></h2>
+
+ <p>The wais URL is used to retrieve resources using the Wide Area
+ Information System protocol. The format is:</p>
+
+ <pre>
+ <em>wais://host:port/database</em>
+ <em>wais://host:port/database?wais_query</em>
+ <em>wais://host:port/database/wais_type/wais_path</em>
+</pre>
+ <p>where <em>:port</em> defaults to <em>:210</em></p>
+
+ <p>Direct wais support is built into <strong>Lynx</strong> for
+ VMS, and can be compiled into <strong>Lynx</strong> on Unix.</p>
+
+ <p>If only a <em>database</em> is indicated in the URL,
+ <strong>Lynx</strong> returns an ISINDEX cover page for searching
+ that <em>database</em>, and will submit your search with the
+ <em>wais_query</em> appended. <strong>Lynx</strong> will convert
+ the server's reply into a hit list with URLs that include the
+ <em>wais_type</em> and <em>wais_path</em> for retrieving items
+ from the hit list.</p>
+
+ <hr>
+
+ <h2><a name="news_url" id="news_url">The <em>news</em>,
+ <em>nntp</em>, and <em>snews</em> URLs:</a></h2>
+
+ <p>The news and nntp URLs are handled by <strong>Lynx</strong> as
+ specified in RFC1738, but for compatibility with other clients,
+ <strong>Lynx</strong> allows inclusion of host and port fields in
+ news URLs, which properly should be used <em>only</em> in nntp
+ and snews URLs. If not included in news URLs,
+ <strong>Lynx</strong> will use the nntp server pointed to by the
+ NNTPSERVER environment variable or configuration symbol (see
+ lynx.cfg), with default port <em>:119</em>. A host field must be
+ included in nntp URLs, and the port field is optional with the
+ same default.</p>
+
+ <p>If the URL requires authentication, <strong>Lynx</strong> will
+ prompt you for the username and password. These are cached during
+ a session, for reuse on the same host. If $HOME/.newsauth exists,
+ <strong>Lynx</strong> initializes its cache from this file. The
+ .newsauth file contents are one line per entry: hostname,
+ password and username (in that order) separated by a space.</p>
+
+ <p>The formats are:<br></p>
+
+ <pre>
+ <em>news:newsgroup</em> (retrieves list of messages in newsgroup)
+ <em>news:messageID</em> (retrieves the message)
+ <em>news:*</em> (retrieves list of all available newsgroups)
+ <em>nntp://host:port/newsgroup</em>
+ <em>nntp://host:port/messageID</em>
+ <em>nntp://host:port/*</em>
+</pre>
+ <p>(snews same as nntp, but the default port is
+ <em>:563</em>)</p>
+
+ <p>The <em>messageID</em> is the message's unique identifier,
+ consisting of an identification string and the host of origin for
+ the message (<em>ident_string@origin_host</em>).</p>
+
+ <p><strong>Lynx</strong> also supports wildcarding via an
+ asterisk for listings of news hierarchies or sub-hierarchies,
+ e.g.:</p>
+
+ <pre>
+ <em>news:comp.infosystems.*</em>
+ <em>nntp://host:port/comp.infosystems.*</em>
+</pre>
+ <p>(snews same as nntp, but the default port is
+ <em>:563</em>)<br>
+ This is not in RFC1738 and may not be supported by all other
+ clients.</p>
+
+ <p><strong>Lynx</strong> allows you both to <em>reply</em> to the
+ author of a news message via email, and, if news posting has been
+ enabled, to send a <em>followup</em> message to the newsgroup
+ (see <a href="#newspost_url">newspost, newsreply, snewspost,
+ snewsreply</a>).</p>
+
+ <p><strong>Lynx</strong> converts any strings in news messages
+ which appear to be a URL with a supported scheme into a link for
+ accessing that URL.</p>
+
+ <p><strong>Lynx</strong> also supports the newsgroup and message
+ number URL scheme:<br></p>
+
+ <pre>
+ <em>news:newsgroup/startNo-endNo</em> (lists message range in newsgroup)
+ <em>news:newsgroup/messageNo</em> (retrieves the message by number)
+ <em>nntp://host:port/newsgroup/startNo-endNo</em>
+ <em>nntp://host:port/newsgroup/messageNo</em>
+</pre>
+ <p>(snews same as nntp, but the default port is
+ <em>:563</em>)<br>
+ Use of this scheme is not recommended, because the message
+ numbers are specific to each nntp server, unlike the unique
+ identifiers for news messages.</p>
+
+ <hr>
+
+ <h2><a name="newspost_url" id="newspost_url">The
+ <em>newspost</em>, <em>newsreply</em>, <em>snewspost</em>, and
+ <em>snewsreply</em> URLs:</a></h2>
+
+ <p>When <strong>Lynx</strong> receives group listings or articles
+ via <em>news</em>, <em>nntp</em> or <em>snews</em> URLs, it also
+ checks whether the nntp server supports posting from the
+ <strong>Lynx</strong> user's site, and if so, includes links for
+ posting new messages to that server, or for posting followups
+ (replies) to previously posted messages. RFC1738, and IETF URL
+ drafts through this release of <strong>Lynx</strong>, do not
+ include any schemes for posting to news groups.
+ <strong>Lynx</strong> has long supported newspost and newreply
+ URL schemes for posting new messages or sending followups,
+ respectively, to standard nntp servers, with default port
+ <em>:119</em>. <strong>Lynx</strong> now also supports homologous
+ snewspost and snewsreply URLs for use with SSL capable nntp
+ servers.</p>
+
+ <p>The formats are:</p>
+
+ <pre>
+ <em>newspost://host:port/newsgroup(s)</em> (post a new message)
+ <em>newsreply://host:port/newsgroup(s)</em> (post a followup message)
+</pre>
+ <p>(snewspost and snewsreply have the same formats, but the
+ default port is <em>:563</em>)</p>
+
+ <p>If the host field is omitted, it defaults to that pointed to
+ by the NNTPSERVER configuration or environmental variable.
+ Inclusion of at least one newsgroup in the URL is required, and
+ additional groups can be specified as a comma-separated list.
+ Wildcarding of newsgroup names is not supported for these URLs.
+ For newsreply and snewsreply URLs, if an external editor has been
+ defined via the <em>Options Menu</em>, the user is offered an
+ option to include the currently displayed document, which
+ presumably is a news article with a <em>followup</em> link that
+ was activated, and if confirmed, each line of that document is
+ prefixed with a right-angle-bracket. The user is expected to edit
+ such an inclusion so that only the passages relevant to the
+ followup message are retained.</p>
+
+ <p>These URLs can be used as command line startfiles (in which
+ case, <strong>Lynx</strong> will exit after posting the message,
+ and the newreply or snewsreply URLs degrade to newspost or
+ snewpost URLs, respectively). They also can be used as HREF
+ attribute values in any HTML document homologously to <a href=
+ "#mailto_url">mailto</a> URLs, with the qualification that they
+ presently are supported only by <strong>Lynx</strong>.</p>
+
+ <hr>
+
+ <h2><a name="mailto_url" id="mailto_url">The <em>mailto</em>
+ URL:</a></h2>
+
+ <p>The mailto URL is used to provide links that when activated
+ can be used to send a comment or the content of a FORM to an
+ Internet email address (user@host). The format is:</p>
+
+ <pre>
+ <em>mailto:user@host</em>
+</pre>
+ <p>The description of the mailto URL in RFC1738 has been
+ interpreted by some as allowing only a single recipient, but
+ <strong>Lynx</strong> invented the mailto URL, has always
+ supported a series of user@host addresses as a comma-separated
+ list, and still does. For compatibility with Explorer,
+ <strong>Lynx</strong> also accepts a semi-colon-separated
+ list.</p>
+
+ <p>For compatibility with Netscape, <strong>Lynx</strong> parses
+ any <em>?subject=The%20Subject</em> appended to the URL, trims
+ the URL at the <em>?</em>, and uses the value as the default
+ Subject: for the message or FORM content mailing. This is not
+ recommended practice. The preferred way to indicate the default
+ Subject: for a LINK or Anchor with a mailto HREF, or a FORM with
+ a mailto ACTION, is via a TITLE attribute with the subject string
+ as its value, e.g.:</p>
+
+ <pre>
+ <em>&lt;LINK REV="made"
+ HREF="mailto:me@myhost,her@herhost" TITLE="The Subject"&gt;</em>
+
+ <em>&lt;A HREF="mailto:user@host" TITLE="The Subject"&gt;...&lt;/A&gt;</em>
+
+ <em>&lt;FORM METHOD="post" ENCTYPE="text/plain"
+ ACTION="mailto:WebMaster@host" TITLE="The Subject"&gt;
+ ...
+ &lt;/FORM&gt;</em>
+</pre>
+ <p>Note that a TITLE attribute for FORM is now included in the
+ HTML specifications. Some clients use a SUBJECT attribute for
+ this purpose in FORM tags, and <strong>Lynx</strong> recognizes
+ that as a synonym for TITLE.</p>
+
+ <p><strong>Lynx</strong> also will process any
+ <em>to=address(es)</em>, <em>cc=address(es)</em>,
+ <em>keywords=word_list</em> and/or <em>body=message</em> fields
+ in <em>?searchpart</em> tack-ons to mailto URLs. The <em>to</em>
+ and/or <em>cc</em> values can be single addresses, or comma- or
+ semi-colon-separated lists of addresses. All addresses, and any
+ <em>body</em> values, will be offered for approval by the user
+ before proceeding with a mailing. Any other name=value pairs in
+ the <em>?searchpart</em> will be ignored. Also, if the mailto URL
+ is the ACTION for a FORM, any <em>body</em> in a
+ <em>?searchpart</em> tack-on will be ignored, because the body of
+ the mailing must be constructed solely from the the FORM's
+ content. <strong>Lynx</strong> expects multiple name=value pairs
+ in a <em>?searchpart</em> tack-on to be separated by ampersands,
+ as in the original Netscape implementation, and in an equally
+ ill-advised IETF draft of that implementation (<a href=
+ "ftp://ftp.isi.edu/internet-drafts/draft-hoffman-mailto-url-03.txt">draft-hoffman-mailto-url-03.txt</a>).
+ These should be represented as entities (<em>&amp;amp;</em>) in
+ the HTML markup. This functionality is generally desired, but the
+ IETF backward compatibility principal normally would lead to a
+ new scheme being used (e.g., <em>mail:</em>, or <em>smtp:</em>),
+ rather than breaking <em>mailto:</em> implementations.</p>
+
+ <p>If <em>ENCTYPE="text/plain"</em> is specified for a FORM with
+ a mailto ACTION, <strong>Lynx</strong> will not hex escape the
+ name=value pairs of the FORM's content, and will use physical
+ newlines instead of &ldquo;<em>&amp;</em>&rdquo; or
+ &ldquo;<em>;</em>&rdquo; to separate the pairs, so that the
+ content will be readable directly. Otherwise,
+ <strong>Lynx</strong> will mail the content with the default:</p>
+
+ <pre>
+ <em>ENCTYPE="application/x-www-form-urlencoded"</em> (&ldquo;<em>&amp;</em>&rdquo; separates pairs)
+</pre>
+ <p>or:</p>
+
+ <pre>
+ <em>ENCTYPE="application/sgml-form-urlencoded"</em> (&ldquo;<em>;</em>&rdquo; separates pairs)
+</pre>
+ <p>if the latter was indicated.</p>
+
+ <p>Note that when mailing FORM content <strong>Lynx</strong>
+ wraps any lines longer than 78 characters, to avoid buffer
+ overflows in mail software and to ensure reliable transmission
+ across gateways. If the ENCTYPE was not <em>text/plain</em>, any
+ script which decodes the mailed content should ignore the
+ physical newlines and recognize only hex escaped newline
+ characters as intended to be present in the decoded content.</p>
+
+ <p>If the mailto URL is not the ACTION for a FORM, and if an
+ external editor has been defined via the <em>Options Menu</em>,
+ the user is offered an option to include the currently displayed
+ document. If this option is accepted, each line of that document
+ is prefixed with a right-angle-bracket, and the prefixed
+ inclusion should be trimmed by the user to just those passages
+ relevant to the message which will be sent.</p>
+
+ <hr>
+
+ <h2><a name="finger_url" id="finger_url">The <em>finger</em>
+ URL:</a></h2>
+
+ <p><strong>Lynx</strong> has full support for the finger
+ protocol, but a format for finger URLs has not yet been adopted
+ by the IETF. The formats supported by <strong>Lynx</strong>
+ therefore include every possibility not inconsistent with
+ RFC1738, including:</p>
+
+ <pre>
+ finger://host finger://@host
+ finger://host/ finger://@host/
+ finger://host/%2fw finger://@host/w
+ finger://host/w finger://host/w/
+ finger://host/username[@host] finger://username@host
+ finger://host/username[@host]/ finger://username@host/
+ finger://host/w/username[@host] finger://username@host/w
+ finger://host/%2fw%20username[@host] finger://host/username[@host]/w
+ finger://host/w/username
+</pre>
+ <p>Activating a finger URL will send a request to the finger
+ server via port 79 on the host specified. You can include
+ <em>:79</em> in the URL, but no other value is allowed. The
+ <em>/w</em> or <em>/%2fw</em> is used to request a full report
+ for finger servers which support it, and is not case sensitive
+ (i.e., can be <em>/W</em> or <em>/%2fW</em>). Any strings in the
+ report which appear to be a URL with a supported scheme will be
+ converted into a link for accessing that URL.</p>
+
+ <p>An alternative way to access finger servers is via gopher URLs
+ with port 79 and the plain text (<em>0</em>) <em>gophertype</em>
+ specified:<br>
+ <em>gopher://host:79/0</em><br>
+ <strong>Lynx</strong> will handle such URLs equivalently to overt
+ finger URLs, including creation of links for any strings which
+ appear to be supported URLs.</p>
+
+ <hr>
+
+ <h2><a name="cso_url" id="cso_url">The <em>cso</em> URL:</a></h2>
+
+ <p>The cso URL is intended to provide a gateway to CSO/PH (QI)
+ servers. The requests are made on port 105 by default
+ (<em>:105</em>), with the following overt cso URL format:<br></p>
+
+ <pre>
+ <em>cso://host</em>
+</pre>
+ <p>You also can use a gopher URL format with port 105 and the CSO
+ (<em>2</em>) <em>gophertype</em> specified:</p>
+
+ <pre>
+ <em>gopher://host:105/2</em>
+</pre>
+ <p><strong>Lynx</strong> will parse the stream returned by the
+ server for the above URLs and create a FORM for submitting
+ additional requests (searches) to the server. Any strings in the
+ reports returned for these requests (searches) which appear to be
+ a URL with a supported scheme will be converted into a link for
+ accessing that URL.</p>
+
+ <hr>
+
+ <h2><a name="bibp_url" id="bibp_url">The <em>bibp</em> URL:</a></h2>
+
+ <p><strong>Lynx</strong> provides built-in support for
+ bibliographic protocol (BibP). BibP links are links to published
+ works such as books or journal articles, without a predefined
+ server. BibP links are intended for resolution by a local bibhost
+ server (http://bibhost/) if it exists. Otherwise, resolution is
+ performed by a document-specified server or a known global
+ server.</p>
+
+ <h2><a name="exec_url" id="exec_url">The <em>lynxexec</em> and
+ <em>lynxprog</em> URLs:</a></h2>
+
+ <p>If execution of spawned commands has been enabled in your
+ <strong>Lynx</strong> image, the lynxexec and lynxprog URLs can
+ be used to execute arbitrary system commands or invoke system
+ utilities. Any system command and associated switches or
+ qualifiers can be used, with the syntax appropriate for a shell
+ running <strong>Lynx</strong> on Unix, or for DCL on VMS,
+ e.g.:</p>
+
+ <pre>
+ <em>lynxexec:dir/date/size foo:[blah]</em> (VMS)
+ <em>lynxexec:ls -l /foo/blah</em> (Unix)
+ <em>lynxprog:news</em>
+</pre>
+ <p>(Note, however, that restrictions on acceptable commands or
+ utilities may be imposed by the system administrator.)</p>
+
+ <p>You optionally can include <em>//localhost/</em> in the URL,
+ between the scheme field and the command, but that is always
+ implied. The lynxexec and lynxprog URLs differ only in that with
+ lynxexec you are prompted to enter <em>RETURN</em> before
+ <strong>Lynx</strong> clears the screen and restores the
+ previously displayed document, so that you can read any screen
+ output generated by the spawned command, whereas no such pause is
+ imposed upon exit from the utility invoked via lynxprog.</p>
+
+ <p>These are Lynxisms and should be used only in local documents
+ intended solely for <strong>Lynx</strong>.</p>
+
+ <hr>
+
+ <h2><a name="cgi_url" id="cgi_url">The <em>lynxcgi</em> URL:</a></h2>
+
+ <p>The lynxcgi URL is implemented only on Unix, can be used as
+ the ACTION for a FORM, and if enabled in your
+ <strong>Lynx</strong> image has the format:</p>
+
+ <pre>
+ <em>lynxcgi://localhost/path_to_CGI_script</em>
+</pre>
+ <p>where <em>//localhost</em> is optional and always implied; the
+ full path should be specified, as &ldquo;~&rdquo; is not
+ recognized; if the script is in the directory
+ <strong>Lynx</strong> was started from, the simple file name is
+ adequate. The output of the script should be text/html and is
+ rendered and displayed by <strong>Lynx</strong>. Restrictions on
+ use of lynxcgi and on acceptable paths can be imposed in
+ <em>userdefs.h</em> and <em>lynx.cfg</em>, qv.</p>
+
+ <p>This is a Lynxism and should be used only in local documents
+ intended solely for <strong>Lynx</strong>, or for limited local
+ testing of CGI scripts without an http server.</p>
+
+ <hr>
+
+ <h2><a name="ncftp_url" id="ncftp_url">The <em>NcFTP</em>
+ URL:</a></h2>
+
+ <p><strong>Lynx</strong> recognizes the NcFTP-style ftp URL,
+ e.g.,</p>
+
+ <pre>
+ <cite>ftpHost</cite>:<cite>fileSpecification</cite>
+</pre>
+ <p>for example</p>
+
+ <pre>
+<code>
+ ftp.gnu.org:/pub/gnu
+</code>
+</pre>
+
+ <hr>
+
+ <h2><a name="internal_url" id="internal_url">The <em>LYNXfoo</em>
+ internal URLs:</a></h2>
+
+ <p><strong>Lynx</strong> uses a variety of private URL schemes
+ for communication among its internal modules. They start with
+ uppercase letters <code>LYNX</code> by convention, although, as
+ input, URL schemes are recognized in a case-insensitive
+ manner.</p>
+
+ <p>As you discover what they are, and are tempted to use them
+ externally in documents, you should <em>resist</em> that
+ temptation:</p>
+
+ <ul>
+ <li>There already is too much browser-specific markup
+ around...</li>
+
+ <li>The schemes, or their meanings, may change between
+ <strong>Lynx</strong> versions.</li>
+
+ <li>Even if a scheme stays the same, some aspect of its
+ behavior may be modified without notice, or the context in
+ which it is allowed may change.</li>
+
+ <li>If it does not work as expected when used outside of the
+ intended purpose, do not expect anyone to "fix" it.</li>
+ </ul>
+
+ <p>For example, tempting though it might be, do not use
+ these:</p>
+
+ <pre>
+ <em>Return to your &lt;A HREF="LYNXHIST:0"&gt;Startfile&lt;/A&gt;</em>
+ <em>Review your &lt;A HREF="LYNXKEYMAP:"&gt;Keymap&lt;/A&gt;</em>
+</pre>
+ <p>(No, they will not do any harm. Yes, they work. But do not
+ rely on it.)</p>
+
+ <p>If you must try one, the second is OK from the command
+ line:<br></p>
+
+ <pre>
+ <em>lynx LYNXKEYMAP:</em>
+</pre>
+ <p>But within <strong>Lynx</strong>, use the
+ &ldquo;<em>K</em>&rdquo; keystroke command. Sometimes it may be
+ convenient to use a private scheme with
+ &ldquo;<em>g</em>&rdquo;oto, as in:</p>
+
+ <pre>
+ <em>g LYNXMESSAGES:</em>
+ <em>g LYNXCOMPILEOPTS:</em>
+ <em>g LYNXCFG:</em>
+</pre>
+ <p>But again, there usually is a way in which those special pages
+ are meant to be reached that is more convenient.</p>
+</body>
+</html>