src - OpenBSD base system

diff options


context:
space:
mode:

author	Mats O Jansson <maja@cvs.openbsd.org>	1998-03-11 17:48:09 +0000
committer	Mats O Jansson <maja@cvs.openbsd.org>	1998-03-11 17:48:09 +0000
commit	69de3a9e357327c17caa3b7bb058035e263573bc (patch)
tree	f6260f228c4d949b174128d017a7e323c7122f32 /gnu/usr.bin/lynx/lynx_help
parent	b81973f175db7d3f4c763069b191dd57f4bd83d3 (diff)

Lynx 2.8

Diffstat (limited to 'gnu/usr.bin/lynx/lynx_help')

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/Lynx_users_guide.html

2303

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/about_lynx.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/bookmark_help.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/cookie_help.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/dired_help.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/edit_help.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/follow_help.html

132

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/gopher_types_help.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/history_help.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/keystroke_help.html

104

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/movement_help.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/option_help.html

262

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/other_help.html

171

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/print_help.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/scrolling_help.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/visited_help.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/keystrokes/xterm_help.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/lynx-dev.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/lynx_help_main.html

-rw-r--r--

gnu/usr.bin/lynx/lynx_help/lynx_url_support.html

586

20 files changed, 4275 insertions, 0 deletions

diff --git a/gnu/usr.bin/lynx/lynx_help/Lynx_users_guide.html b/gnu/usr.bin/lynx/lynx_help/Lynx_users_guide.html
new file mode 100644
index 00000000000..49cec8d355c
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/Lynx_users_guide.html

@@ -0,0 +1,2303 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<html>

+<head>

+<title>Lynx Users Guide v2.8</title>

+<link rev="made" href="mailto:lynx-dev@sig.net">

+</head>

+<body>

+<h1>Lynx Users Guide v2.8</h1>

+Lynx is a fully-featured World Wide Web (WWW) 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 Hypertext Markup Language

+(HTML) documents containing links to files on the local system, as

+well as files on remote systems running http, gopher,

+ftp, wais, nntp, finger, or

+cso/ph/qi servers, and services accessible via

+logins to telnet, tn3270 or rlogin accounts (see

+<a href="lynx_url_support.html">URL Schemes Supported by Lynx</a>).

+<a href="#32">Current</a> versions of Lynx run on Unix, VMS,

+Windows95/NT, 386DOS and OS/2 EMX.

+Lynx can be used to access information on the WWW, or to build

+information systems intended primarily for local access. For example, Lynx

+has been used to build several Campus Wide Information Systems

+(CWIS). In addition, Lynx can be used to build systems isolated

+within a single LAN.

+<h2><A NAME="TOC">Table of Contents</A></h2>

+<ul>

+<li><A HREF="#1">Lynx online help</A>

+<li><A HREF="#2">Viewing local files with Lynx</A>

+<li><A HREF="#3">Leaving Lynx</A>

+<li><A HREF="#4">Starting Lynx with a Remote File</A>

+<li><A HREF="#5">Starting Lynx with the WWW_HOME environment variable.</A>

+<li><A HREF="#6">Navigating hypertext documents with Lynx</A>

+<li><A HREF="#7">Printing, Mailing, and Saving rendered files to disk.</A>

+<li><A HREF="#8">Viewing the HTML document source and editing documents</A>

+<li><A HREF="#9">Downloading and Saving source files.</A>

+<li><A HREF="#10">Reloading files and refreshing the display</A>

+<li><A HREF="#11">Lynx searching commands</A>

+<li><A HREF="#12">Lynx Options Menu</A>

+<li><A HREF="#13">Comments and mailto: links</A>

+<li><A HREF="#14">USENET News posting</A>

+<li><A HREF="#15">Lynx bookmarks</A>

+<li><A HREF="#16">Jump command</A>

+<li><A HREF="#17">Directory Editing</A>

+<li><A HREF="#18">Scrolling and Other useful commands</A>

+<li><a href="#19">Lynx and HTML Forms</a>

+<li><a href="#20">Lynx and HTML Tables</a>

+| <a href="#21">Lynx and HTML Tabs</a>

+<li><a href="#22">Lynx and HTML Frames</a>

+| <a href="#23">Lynx and HTML Banners</a>

+<li><a href="#24">Lynx and HTML Footnotes</a>

+| <a href="#25">Lynx and HTML Notes</a>

+<li><a href="#26">Lynx and HTML Lists</a>

+<li><a href="#27">Lynx and HTML Quotes</a>

+<li><a href="#28">Lynx and Client-Side-Image-Maps</a>

+<li><a href="#29">Lynx and Client-Side-Pull</a>

+<li><a href="#30">Lynx and State Management</a> (Me want cookie!)

+<li><A HREF="#31">The Lynx command line</A>

+<li><A HREF="#32">Lynx development history</A>

+</ul>

+<h2><A NAME="1">Lynx online help</A></h2>

+Online help is available while viewing any document. Press the

+'?' or 'H' key (or the 'h key if vi-like

+key movement is not on) to see a list of help topics. See the section

+titled <A HREF="#6">Navigating hypertext documents with Lynx</A> for

+information on navigating through the help files.

+In addition, a summary description of all the Lynx keystroke commands

+and their key bindings is available by pressing the 'K' key (or

+the 'k' key if vi-like key movement is not on).

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="2">Viewing local files with Lynx</A></h2>

+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:

+<dl>

+ <dt>UNIX

+ <dd><code>lynx filename</code>

+ <dd><code>lynx /home/my-dir/filename</code>

+ <dd><code>lynx ~/filename</code>

+ <dt>VMS

+ <dd><code>lynx filename</code>

+ <dd><code>lynx dua5:[my-directory]filename</code>

+ <dd><code>lynx /dua5/my-directory/filename</code>

+ <dd><code>lynx ~/filename</code>

+ <dd><code>lynx sys$login:filename</code>

+ <dd><code>lynx /sys$login/filename</code>

+ <dt>Win32/DOS

+ <dd><code>lynx file:///filename</code>

+ <dd><code>lynx filename</code>

+ <dd><code>lynx c:/dir/filename</code>

+ <dd><code>lynx //n/dir/filename</code>

+</dl>

+When executed, Lynx will clear the screen and display as much of the

+specified file as will fit on the screen. Pressing a down-arrow

+will bring up the next screen, and pressing an up-arrow will bring

+up the previous screen. If no file is specified at startup, a default file

+will be displayed. (The default is configured by the system administrator

+when the command is installed.)

+Lynx will display local files written in the HyperText Markup

+Language (HTML), if the file's name ends with the characters

+.html, .htm, .shtml, .htmlx,

+.html3, or .ht3. 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

+hypertext document. If the filename does not have one of the

+suffixes mapped by Lynx to HTML, the -force_html command line

+option can be included to force treatment of the file as hypertext.

+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.

+The one link displayed as "highlighted" text is the currently

+"selected" link. Lynx will display the file associated with the

+selected link when a right-arrow or a Return key is

+pressed. To select a particular link, press the up-arrow or

+down-arrow keys until the desired link becomes "highlighted,"

+and then press the right-arrow or Return 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.).

+Lynx renders HTML files and saves the rendition, not the source,

+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 'x' and

+'X', instead of the right-arrow or Return 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 Control-R.

+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 'D'

+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

+Save to disk, which is disabled if Lynx is running in anonymous

+mode. Any number of additional download methods may be defined in the

+lynx.cfg file by the system administrator. Programs like kermit, zmodem

+and FTP are some possible options. [<A HREF="#TOC">ToC</A>]

+<h2><A NAME="3">Leaving Lynx</A></h2>

+To exit Lynx use the 'q' command. You will be asked whether

+you really want to quit. Answering 'y' will exit and 'n'

+will return you to the current document. Use 'Q' or

+Control-D to quit without verification. [<A HREF="#TOC">ToC</A>]

+<h2><A NAME="4">Starting Lynx with a Remote File</A></h2>

+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:

+<code>PROTOCOL :// HOST / PATH</code>

+where

+<dl>

+ <dt><code>PROTOCOL</code>

+ <dd>identifies the communications protocol (scheme) 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.

+ <dt><code>HOST</code>

+ <dd>is the Internet address of the computer system on which the

+ server is running, and

+ <dt><code>PATH</code>

+ <dd>is a scheme-specific field which for some schemes may

+ correspond to a directory path and/or filename.

+</dl>

+Here are some sample URLs.

+<dl>

+ <dt>HTTP (HyperText Transfer Protocol)

+ <dd><code>http://www.crl.com/~subir/lynx.html</code>

+ <dt>Gopher

+ <dd><code>gopher://gopher.micro.umn.edu/11/</code>

+ <dt>FTP (File Transfer Protocol)

+ <dd><code>ftp://ftp2.cc.ukans.edu/pub/lynx/README</code>

+ <dt>WAIS (Wide Area Information Service protocol)

+ <dd><code>wais://cnidr.org/directory-of-servers</code>

+ <dt>A URL may be specified to Lynx on the command line, as in:

+ <dd><code>lynx http://kufacts.cc.ukans.edu/cwis/kufacts_start.html</code>

+</dl>

+Lynx also will attempt to create a complete URL if you include adequate

+portions of it in the startfile argument. For example:

+<tab indent="34">wfbr

+<tab indent="62">will be expanded to:

+<tab indent="12">http://www.wfbr.edu/

+<tab indent="62">and:

+<tab indent="26">ftp.more.net/pub

+<tab indent="62">will be expanded to:

+<tab indent="14">ftp://ftp.more.net/pub

+See <a href="lynx_url_support.html">URL Schemes Supported by Lynx</a> for

+more detailed information. [<A HREF="#TOC">ToC</A>]

+<h2><A NAME="5"

+>Starting Lynx with the WWW_HOME environment variable.</A></h2>

+You may also specify a starting file for Lynx using the WWW_HOME

+environment variable,

+<dl>

+ <dt>UNIX

+ <dd>

+ <dl>

+ <dt>ksh

+ <dd><code>export WWW_HOME=http://www.w3.org/</code>

+ <dt>csh

+ <dd><code>setenv WWW_HOME http://www.w3.org/</code>

+ </dl>

+ <dt>VMS

+ <dd><code>define "WWW_HOME" "http://www.w3.org/"</code>

+ <dt>win32

+ <dd><code>WWW_HOME=http://www.w3.org/ [or in registry]</code>

+</dl>

+Note that on VMS the double-quoting must be included to preserve

+casing.

+<h2><A NAME="6">Navigating hypertext documents with Lynx</A></h2>

+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.

+<pre>

+ +-------+-------+-------+

+ | TOP | /|\ | Page |

+ arrow keys | of | | | UP |

+ | text 7| | 8| 9|

+ +---------+ +-------+-------+-------+

+ | SELECT | | | | |

+ | prev /|\| | <--- | | ---> |

+ | link | | | 4| 5| 6|

+ +---------+---------+---------+ +-------+-------+-------+

+ |<-- prev | next | | sel. -->| | of | | | DOWN |

+ | doc. | link \|/| link | | text 1| \|/ 2| 3|

+ +---------+---------+---------+ +-------+-------+-------+

+</pre>

+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="#18">Scrolling and Other useful commands</A>. Some

+additional commands depend on the fact that Lynx keeps a list of each

+link you visited to reach the current document, called the <a

+href="keystrokes/history_help.html">History Page</a>, and a

+list of all links visited during the current Lynx session, called the <a

+href="keystrokes/visited_help.html">Visited Links Page</a>. The

+HISTORY keystroke command, normally mapped to Backspace or

+Delete, will show you the History Page of links leading to

+your access of the current document. Any of the previous documents shown in

+the list may be revisited by selecting them from the history screen. The

+VLINKS keystroke command, normally mapped to uppercase 'V', will

+show the Visited Links Page, and you similarly can select links in

+that list. The MAIN_MENU keystroke command, normally mapped to 'm'

+and 'M', will take you back to the starting document unless you

+specified the -homepage=URL option at the command line. Also, the

+LIST keystroke command, normally mapped to 'l' and L',

+will create a compact list of all the links in the current document, and

+they can be selected via that list.

+The 'i' key presents an index of documents. The default index

+is usually a document pointing to servers around the world, but the index

+can be changed by the system administrator or on the command line using

+the -index=URL switch, and therefore depends on how the Lynx

+program you are using was configured.

+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. [<A HREF="#TOC">ToC</A>]

+<h2><A NAME="7"

+>Printing, Mailing, and Saving rendered files to disk.</A></h2>

+Rendered HTML documents, and plain text files, may be printed using the

+'p' command while viewing the document. After pressing the

+'p' key a menu of Print Options 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.

+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 Save to a local file

+option allows you to save the document into a file on your disk

+space. Any number of additional print options may also be

+available as configured by your system administrator.

+Some options, such as Save to a local file, 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 up-arrow or down-arrow keys at the prompt.

+Note that if you want exact copies of text files without any expansions

+of TAB characters to spaces you should use the <a href="#9">Download</a>

+options. [<A HREF="#TOC">ToC</A>]

+<h2><A NAME="8"

+>Viewing the HTML document source and editing documents</A></h2>

+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 '\' (backslash) key. The document must be reloaded from the

+server or disk to be displayed on the screen unrendered, since Lynx

+originally rendered what it received and does not still have it as source.

+When viewing unrendered documents you may print them as any normal document.

+Selecting the Print to a local file 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="#9">Download</a> the source.

+NOTE: When saving an HTML document it is important to name the

+document with a .html extension, if you want to read it with

+Lynx again later.

+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:

+<dl>

+<dt>Command

+ <dd><code>lynx file://localhost/FULL/PATH/FILENAME</code>

+ <dd><code>lynx path/filename.html</code>

+</dl>

+In addition, the user must also specify an editor in the

+Options Menu 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 'e' command. When the 'e'

+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. [<A HREF="#TOC">ToC</A>]

+<h2><A NAME="9">Downloading and Saving source files.</A></h2>

+If the DOWNLOAD keystroke command ('d' or D) is used

+when positioned on a link for an HTML, plain text, or binary file, Lynx

+will transfer the file, without rendering or modification, into a temporary

+location and present the user with a list of options, as when a link for a

+binary file of a type for which no viewer has been mapped is activated.

+As described above, the only default Download option is

+Save to disk, which is disabled if Lynx is running in

+anonymous mode, and any number of additional download methods such as

+kermit and zmodem may be defined in the lynx.cfg file by the

+system administrator. Downloading the sources of HTML and plain text

+files, instead of toggling to <a href="#8">display the source</a>

+('\') and then using <a href="#7">Printing</a> options, ensures

+that no modifications of the source (e.g., expansions of TAB characters

+to a series of spaces) will occur.

+Some options, such as Save to disk, 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

+up-arrow or down-arrow keys at the prompt.

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="10"

+>Reloading files and refreshing the display</A></h2>

+The RELOAD (Control-R) command will reload and re-render the file

+that you are currently viewing. The REFRESH (Control-L or

+Control-W) command will refresh or wipe the screen to remove or

+correct any errors that may be caused by operating system or other messages.

+The NOCACHE ('x' or 'X') command can be used in lieu

+of ACTIVATE (Return or right-arrow) 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 Pragma: no-cache and Cache-Control: no-cache

+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="#19">Lynx and HTML Forms</A>). [<A HREF="#TOC">ToC</A>]

+<h2><A NAME="11">Lynx searching commands</A></h2>

+Two commands activate searching in Lynx: '/' and 's'.

+While viewing a normal document use the '/' 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="#12">Options Menu</a>. The search

+options are case sensitive and case insensitive. These searches are entirely

+local to Lynx.

+Some documents are designated index documents 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 's' 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 ?searchpart

+(see <a href="lynx_url_support.html">Supported URLs</a>).

+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 up-arrow or down-arrow keys at the prompt for a search

+word or string. Also, you can use the 'n'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.

+Although <a href="#19">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

+cover page describing a WAIS database and how to formulate query

+strings for searching it, and include an element such as:

+<tab indent="12"><ISINDEX <tab id="idx">PROMPT="Enter WAIS query:"

+<tab to="idx">HREF="wais://net.bio.net/biologists-addresses">

+for submitting a search of the Biologist's Addresses database directly

+to the net.bio.net WAIS server. [<A HREF="#TOC">ToC</A>]

+<h2><A NAME="12">Lynx Options Menu</A></h2>

+The Lynx Options Menu may be accessed by pressing the 'o'

+key. The current Options Menu contains the following configurable

+options.

+<pre>

+ Options Menu

+ E)ditor : emacs

+ D)ISPLAY variable : aixtest.cc.ukans.edu:0.0

+ mu(L)ti-bookmarks: OFF B)ookmark file: lynx_bookmarks.html

+ F)TP sort criteria : By Filename

+ P)ersonal mail address : montulli@netscape.com

+ S)earching type : CASE INSENSITIVE

+ preferred document lan(G)uage: en

+ preferred document c(H)arset : NONE

+ display (C)haracter set : ISO Latin 1

+ raw 8-bit or CJK m(O)de : ON show color (&) : OFF

+ V)I keys: OFF e(M)acs keys: OFF sho(W) dot files: OFF

+ popups for selec(T) fields : ON show cursor (@) : OFF

+ K)eypad mode : Numbers act as arrows

+ li(N)e edit style : Default Binding

+ l(I)st directory style : Mixed style

+ U)ser mode : Advanced

+ user (A)gent : [User-Agent header]

+ local e(X)ecution links : FOR LOCAL FILES ONLY

+</pre>

+An option can be changed by entering the capital letter or character in

+parentheses for the option you wish to change (e.g. 'E' for Editor

+or '@' 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 Control-U can be used to erase the whole

+line. When you are done entering a change press the Return key

+to get back to the Command? prompt.

+For fields where you must choose one of two choices, press any key

+to toggle the choices and press the Return key to finish the

+change.

+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="#19">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 Return key to

+finish the change.

+When you are done changing options use the 'r' command to

+return to Lynx or the '>' command to save the options to a

+.lynxrc file and return to Lynx.

+The following table describes the options available on the

+Options Menu:

+<dl>

+ <dt>Editor

+ <dd>The editor to be invoked when editing browsable files, and

+ sending mail or comments. The full pathname of the editor

+ command should be specified when possible.

+ <dt>DISPLAY variable

+ <dd>This option is only relevant to X Window users. The DISPLAY

+ (Unix) or DECW$DISPLAY (VMS) variable is picked up automatically

+ from the environment if it has been previously set.

+ <dt>Multi-bookmarks

+ <dd>Lynx supports a default bookmark file, and up to 26 total

+ bookmark files (see below). When multi-bookmarks is OFF,

+ the default bookmark file is used for the 'v'iew

+ bookmarks and 'a'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

+ Bookmark file, below) in that menu. In ADVANCED mode,

+ you instead are prompted for the letter of the desired bookmark

+ file, but can enter '=' to invoke the STANDARD selection

+ menu, or RETURN for the default bookmark file.

+ <dt>Bookmark file

+ <dd>When multi-bookmarks is OFF, this is the filename and location

+ of your default personal bookmark file. Enter 'B' 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. Using the 'a'dd bookmark

+ link command (see <a href="#15">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. When multi-bookmarks is

+ STANDARD or ADVANCED, entering 'B' will invoke a menu

+ of up to 26 bookmark files (associated with the letters of the

+ English alphabet), for editing their filenames and locations

+ (filepath), and descriptions. Lynx will create bookmark

+ files, if they don't already exist, when you first 'a'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., not

+ [.BM]lynx_bookmarks.html).

+ For Win32, see [???].

+ <dt>FTP sort criteria

+ <dd>This option allows you to specify how files will be sorted

+ within FTP listings. The current options include

+ "<code>By Filename</code>", "<code>By Size</code>",

+ "<code>By Type</code>", and "<code>By Date</code>".

+ <dt>Personal mail address

+ <dd>This mail address will be used to help you send files to

+ yourself and will be included as the From: address in any mail

+ or comments that you send. It will also be sent as the From:

+ field in HTTP or HTTPS requests if inclusion of that header

+ has been enabled via the NO_FROM_HEADER definition in lynx.cfg

+ (the compilation default is not to send the header), or via the

+ -from command line toggle.

+ <dt>Searching type

+ <dd>Searching type has two possible values: CASE INSENSITIVE

+ (default) and CASE SENSITIVE. The searching type effects

+ inter-document searches only, and determines whether searches

+ for words within documents will be done in a case-sensitive or

+ case-insensitive manner.

+ <dt>Preferred Document Language

+ <dd>The language you prefer if multi-language files are available

+ from servers. Use RFC 1766 abbreviations, e.g., en for English,

+ fr for French, etc. Can be a comma-separated list, which may

+ be interpreted by servers as descending order of preferences.

+ You can also make your order of preference explicit by using

+ q factors as defined by the HTTP protocol, for servers which

+ understand it, for example:

+ da, en-gb;q=0.8, en;q=0.7

+ <dt>Preferred Document Charset

+ <dd>The character set you prefer if sets in addition to ISO-8859-1

+ and US-ASCII are available from servers. Use MIME notation

+ (e.g., ISO-8859-2) and do not include ISO-8859-1 or US-ASCII,

+ since those values are always assumed by default. Can be a

+ comma-separated list, which may be interpreted by servers as

+ descending order of preferences. You can also make your order

+ of preference explicit by using q factors as defined by the

+ HTTP protocol, for servers which understand it, for example:

+ iso-8859-5, utf-8;q=0.8

+ <dt>Display Character set

+ <dd>This option allows you to set up the default character set for

+ your specific terminal. The display character set provides a

+ mapping from the character encodings of viewed documents and

+ from HTML entities into viewable characters. It should be set

+ according to your terminal's character set so that characters

+ other than 7-bit ASCII can be displayed correctly, using

+ approximations if necessary. You must have the selected

+ character set installed on your terminal.

+ <dt>Raw 8-bit or CJK Mode

+ <dd>Whether 8-bit characters are assumed to correspond with the

+ selected character set and therefore are processed without

+ translation via the chartrans conversion tables. Should be ON

+ by default when the selected character set is one of the Asian

+ (CJK) sets and the 8-bit characters are Kanji multibytes.

+ Should be OFF for the other character sets, but can be turned ON

+ when the document's charset is unknown (e.g., is not ISO-8859-1

+ and no charset parameter was specified in a reply header from

+ an HTTP server to indicate what it is) but you know by some

+ means that you have the matching display character set selected.

+ Should be OFF when an Asian (CJK) set is selected but the document

+ is ISO-8859-1. The setting also can be toggled via the RAW_TOGGLE

+ command, normally mapped to '@', and at startup via the

+ -raw switch.

+ <dt>Show color.

+ <dd>This option will be present if color support is available.

+ If set to ON or ALWAYS, color mode will be forced on if possible.

+ If (n)curses color support is available but cannot be used for

+ the current terminal type, selecting ON is rejected with a message.

+ If set to OFF or NEVER, color mode will be turned off.

+ ALWAYS and

+ NEVER are not offered in anonymous accounts. If saved to a

+ .lynxrc 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 -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.

+ A saved value of NEVER will

+ cause Lynx to assume a monochrome terminal at startup.

+ 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 .lynxrc 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

+ -color switch or COLORTERM variable. This

+ default behavior always is used in anonymous accounts, or if

+ the option_save 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.

+ <dt>VI keys

+ <dd>If set to ON then the lowercase h, j, k, and l keys will be

+ mapped to left, down, up, and right arrow, respectively. The

+ uppercase H, J, K, and L keys remain mapped to their configured

+ bindings (normally HELP, JUMP, KEYMAP, and LIST, respectively).

+ <dt>Emacs keys

+ <dd>If set to ON then the CTRL-P, CTRL-N, CTRL-F, and CTRL-B keys

+ will be mapped to up-arrow, down-arrow, right-arrow, and

+ left-arrow, respectively. Otherwise, they remain mapped to

+ their configured bindings (normally UP_TWO lines, DOWN_TWO

+ lines, NEXT_PAGE, and PREV_PAGE, respectively).

+ <dt>Show dot files

+ <dd>If display/creation of hidden (dot) files/directories is

+ enabled, you can turn the feature on or off via this setting.

+ <dt>Popups for select fields

+ <dd>Lynx normally uses a popup window for the OPTIONs in form

+ SELECT fields when the field does not have the MULTIPLE

+ attribute specified, and thus only one OPTION can be selected.

+ The use of popup windows can be disabled by changing this setting

+ to OFF, in which case the OPTIONs will be rendered as a list of

+ radio buttons. Note that if the SELECT field does have the

+ MULTIPLE attribute specified, the OPTIONs always are rendered

+ as a list of checkboxes.

+ <dt>Show cursor for current link or option.

+ <dd>Lynx normally hides the cursor by positioning it to the right

+ and if possible the very bottom of the screen, so that the

+ current link or OPTION is indicated solely by its highlighting

+ or color. If show cursor is set to ON, the cursor will be

+ positioned at the left of the current link or OPTION. This

+ is helpful when Lynx is being used with a speech or braille

+ interface. It also is useful for sighted users when the

+ terminal cannot distinguish the character attributes used

+ to distinguish the current link or OPTION from the others in

+ the screen display.

+ <dt>Keypad as arrows, numbered links, or numbered links and form fields

+ <dd>This option gives the choice among navigating with the arrow

+ keys, or having every link numbered so that the links may be

+ selected or made current by numbers as well as using the arrow

+ keys, or having every link as well as every form field numbered

+ so that they can be selected or sought by numbers. See the

+  &nbsp<a href="keystrokes/follow_help.html"

+ >Follow link (or page) number:</a> and

+  &nbsp<a

+ href="keystrokes/follow_help.html#select-option"

+ >Select option (or page) number:</a>

+ help for more information.

+ <dt>Line edit style

+ <dd>This option allows you to set alternate key bindings for the

+ built-in line editor, if your system administrator has installed

+ alternates. Otherwise, Lynx uses the <a

+ href="keystrokes/edit_help.html">Default Binding</a>.

+ <dt>List directory style

+ <dd>Applies to Directory Editing. Files and directories can be

+ presented in the following ways:

+ <dl>

+ <dt>Mixed style

+ <dd>Files and directories are listed together in alphabetical

+ order.

+ <dt>Directories first

+ <dd>Files and directories are separated into two alphabetical

+ lists. Directories are listed first.

+ <dt>Files first

+ <dd>Files and directories are separated into two alphabetical

+ lists. Files are listed first.

+ </dl>

+ <dt>User Mode

+ <dd>There are three possible choices: Novice, Intermediate, and

+ Advanced.

+ <dl>

+ <dt>Novice

+ <dd>In Novice mode two lines of help are displayed at the

+ bottom of the screen.

+ <dt>Intermediate

+ <dd>Intermediate mode turns off the help lines.

+ <dt>Advanced

+ <dd>Advanced mode displays the URL of the currently selected

+ link at the bottom of the screen.

+ </dl>

+ <dt>User Agent

+ <dd>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 a string such as L_y_n_x/2.8

+ for access to sites which discriminate against Lynx based on

+ checks for the presence of "Lynx" 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 the Options Menu. Changes of

+ the header are not saved in the RC file.

+ <dd>NOTE that Netscape Communications Corp. has claimed

+ that false transmissions of "Mozilla" as the User-Agent are a

+ copyright infringement, which will be prosecuted. DO NOT

+ misrepresent Lynx as Mozilla. The Options Menu issues

+ a warning about possible copyright infringement whenever the

+ header is changed to one which does not include "Lynx"

+ or "lynx".

+ <dt>Local execution scripts or links

+ <dd>Local execution can be activated by the system administrator.

+ If it has not been activated you will not see this option

+ in the Options Menu.

+ <dd>When a local execution script is encountered Lynx checks the

+ users options to see whether the script can be executed. Users

+ have the following options:

+ <dl>

+ <dt> Always off

+ <dd>Local execution scripts will never be executed

+ <dt>For Local files only

+ <dd>Local execution scripts will only be executed if the

+ script to be executed resides on the local machine,

+ and is referenced by a URL that begins with

+ file://localhost

+ <dt>Always on

+ <dd>All local execution scripts will be executed

+ </dl>

+ <dd>If the users options permit the script to be executed Lynx will

+ spawn a shell and run the script. If the script cannot be

+ executed Lynx will show the script within the Lynx window and

+ inform the user that the script is not allowed to be executed

+ and will ask the user to check his/her options.

+ [<A HREF="#TOC">ToC</A>]

+</dl>

+<h2><A NAME="13">Comments and mailto: links</A></h2>

+At any time while viewing documents within Lynx, you may use the

+'c' command to send a mail message to the owner of the current

+document if the author of the document has specified ownership. If no

+ownership is specified then comments are disabled. Certain links called

+<a href="lynx_url_support.html#mailto">mailto:</a> links will also allow

+you to send mail to other people. Using the mail features within Lynx is

+straightforward.

+Once you have decided to send a comment or have selected a

+mailto: 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 Options Menu, your e-mail

+address will be filled in automatically. After entering the above

+information, if you have an editor defined in the Options Menu

+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.

+To finish sending the message, exit your spawned editor or, if you are

+using the simple line mode input scheme, type a '.' (period) on

+a line by itself. You will be asked a final time whether to send the

+message. If you press 'y', you will be prompted whether to

+append your signature file if one was defined in lynx.cfg and is accessible,

+and then the message will be sent, whereas if you press 'n' the

+message will be deleted. Entering Control-G in response to any prompts

+also will cancel the mailing.[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="14">USENET News posting</A></h2>

+While reading <a

+href="http://www.w3.org/hypertext/DataSources/News/Groups/Overview.html"

+>news</a> articles with Lynx you should see a link that says

+Reply to: user@host and, if the nntp server from which you

+received the article supports posting from your site, a link that says

+Followup to: newsgroup(s)

+<dl>

+ <dt>Reply to user@host

+ <dd>user@host will correspond to the mail address of the

+ person who posted the news article. Selecting the link will

+ allow you to send a message to the person who wrote the message

+ you are currently viewing. You will be given the option of

+ including the original message in your reply.

+ <dt>Followup to newsgroup(s)

+ <dd>Selecting this link will allow you to post back to the

+ newsgroup that you are currently reading and any newsgroups

+ to which the message was cross-posted. You will be given

+ the option of including the original message in your reply.

+ Once you have typed in your message, you will be asked for

+ confirmation of whether to proceed with the posting, and

+ whether to append your signature file if one was defined in

+ lynx.cfg 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">ToC</A>]

+</dl>

+<h2><A NAME="15">Lynx bookmarks</A></h2>

+It is often useful to place a bookmark to aid in returning quickly to

+a document. To use the bookmark feature you must first use the

+Options Menu to specify a bookmark filename.

+To save a bookmark to the document you wish to place in the

+bookmark file press the 'a' key and you will be asked:

+<blockquote>

+ Save D)ocument or L)ink to bookmark file or C)ancel? (d,l,c):

+</blockquote>

+Answer 'd' to save a link to the document you are currently

+viewing or 'l' to save the link that is currently selected on

+the page. Selecting 'c' will cancel without saving anything to

+your bookmark file.

+A bookmark file will be created in conjunction with acting on the

+'a'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 'a'dd command before you

+can view it.

+Use the 'v' 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.

+You can remove a link from the bookmark list by pressing the

+'r' key when positioned on that link. You also can use a

+standard text editor (e.g., via the 'e'dit command while viewing

+a bookmark file, if an external editor has been defined via the Options

+menu) to delete or re-order links in the bookmark file, or to modify

+a link name by editing the content of the Anchor element for the

+link, but you should not change the format within the line for the link,

+consisting of an LI element followed by the Anchor

+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 HREF attribute in the Anchor 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 HREF value and Anchor content, but you

+should not add any other HTML markup to the bookmark file. If the format

+and spacing (other than the Anchor content or HREF value)

+within lines is changed or other HTML markup is added, the 'a'dd

+and 'r'emove commands may not work properly.

+When multi-bookmarks (see <a href="#12">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 '=' to invoke the STANDARD selection menu, or

+RETURN for the default bookmark file.

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="16">Jump Command</a></h2>

+A feature similar to the Lynx bookmarks is the jump command. The jump

+command allows you to enter a shortcut name to access a URL. If the jump

+feature is active, typing 'j' will produce a prompt where you may

+enter the shortcut name. Type '?' at the jump prompt for a list

+of shortcut names available.

+All jump shortcut entries are saved in a circular buffer, and any

+previous entries can be retrieved for re-use by pressing the

+up-arrow or down-arrow keys at the prompt.

+Note to System Administrators: Read the lynx.cfg file on how

+to set up the jump command for your system and how to define shortcut names.

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="17">Directory Editing</a></h2>

+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

+file://localhost/path/, 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

+<dl>

+<dt><code>C)reate</code>

+<dd>Type 'c' to create a new file. New file will be empty.

+<dt><code>D)ownload</code>

+<dd>Type 'd' to download selection using one of the options defined

+ by your system administrator.

+<dt><code>E)dit</code>

+<dd>Type 'e' to spawn the editor defined in Options Menu

+ and load a selected file for editing.

+<dt><code>F)ull Menu</code>

+<dd>Type 'f' to show full menu of options available for selection.

+ Menu may vary according to type of file selected and compression

+ facilities available.

+

+<dt><code>M)odify</code>

+<dd>Type 'm' to modify the name or location of file. Then type

+ 'n' to rename the file or 'l' to move the file to

+ a different location.

+<dt><code>R)emove</code>

+<dd>Type 'r' to remove the selected file or directory.

+<dt><code>T)ag</code>

+<dd>Type 't' to tag highlighted file. Further operations will be

+ performed on tagged files instead of highlighted ones.

+<dt><code>U)pload</code>

+<dd>Type 'u' to upload a file to the present directory. Upload

+ methods are defined by your system administrator.

+</dl>

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="18">Scrolling and Other useful commands</A></h2>

+A summary of all the keystroke commands and their key bindings can

+be invoked via the KEYMAP command, normally mapped to 'k' and

+'K'. The following describes some of the most commonly used

+commands.

+<dl>

+ <dt>^A

+ <dd>Control-A jumps you to the beginning of the current

+ document. It is a synonym for the Keypad Home key, and

+ can be used also when Links are numbered mode is on. The

+ Find Function key also is a synonym, and ideally the

+ latter has been mapped to the Function key labeled Home

+ if you are using an IBM Enhanced Keyboard.

+ <dt>^E

+ <dd>Control-E jumps you to the end of the current document.

+ It is a synonym for the Keypad End key, and can be used

+ also when Links are numbered mode is on. The Select

+ Function key also is a synonym, and ideally the latter has been

+ mapped to the Function key labeled End if you are using

+ an IBM Enhanced Keyboard.

+ <dt>^B

+ <dd>Control-B normally jumps you to the previous page of

+ the current document, and thus is a synonym for the Keypad and

+ Function Page-Up keys. However, Control-B

+ acts as right-arrow when emacs-like key movement is

+ enabled (see <A HREF="#12">Lynx Options Menu</A>).

+ <dt>^F

+ <dd>Control-F normally jumps you to the next page of the

+ current document, and thus is a synonym for the Keypad and

+ Function Page-Down keys. However, Control-F

+ becomes right-arrow when emacs-like key movement is

+ enabled.

+ <dt>^N

+ <dd>Control-N normally jumps you forward two lines in the

+ current document. The Remove Function key (labeled

+ Delete on IBM Enhanced keyboards, and distinct

+ from their Backspace key) is a synonym.

+ Control-N becomes down-arrow when emacs-like

+ key movement is enabled.

+ <dt>^P

+ <dd>Control-P normally jumps you back two lines in the

+ current document. The Insert Function key is a synonym.

+ Control-P becomes up-arrow when emacs-like

+ key movement is enabled.

+ <dt>)

+ <dd>The ) command jumps you forward half a page in the

+ current document.

+ <dt>(

+ <dd>The ( command jumps you back half a page in the

+ current document.

+ <dt>#

+ <dd>The '#' command 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.

+ <dt>!

+ <dd>When '!' is pressed your default shell will be spawned.

+ When you quit or exit the shell you will return to Lynx (usually

+ exit under Unix and logout under VMS). This

+ command is usually disabled for anonymous users. On VMS,

+ '$' normally is a synonym.

+ On Win32, this has no effect [???].

+ <dt>g

+ <dd>The 'g' command allows any URL to be viewed. Pressing

+ the 'g' 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 up-arrow or

+ down-arrow keys.

+ <dt>G

+ <dd>The 'G' command allows you to edit the URL of the

+ current document and then use that as a goto URL. Pressing

+ the 'G' 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 'g' command.

+ <dt>E

+ <dd>The 'E' command allows you to edit the URL (or ACTION)

+ of the current link and then use that as a goto URL. Pressing

+ the 'E' command will bring up a prompt asking you

+ to edit the current link's URL. If you do not modify it, or

+ completely delete it, or enter Control-G, the command will be

+ cancelled. Otherwise, the request for the 'E'dited URL will be

+ sent with method GET, and will be entered into the circular

+ buffer for goto URLs so that it can be accessed for further

+ modification via the 'g' command. Note that lower

+ case 'e' invokes the editor for the current document.

+ <dt>=

+ <dd>The '=' 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.

+ <dt>^T

+ <dd>Control-T toggles Lynx trace mode on and off. This is

+ useful for diagnosing bad html. If you get a Bad HTML

+ statusline message when loading a document, enter

+ Control-T and then Control-R to reload the

+ document in trace mode. 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.

+ <dt>;

+ <dd>The ; command shows the Lynx Trace Log

+ (lynx.trace in the home directory) if one has been

+ started for the current session. If a log has not been started,

+ any trace and other stderr 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

+ -trace command line switch, or via the

+ Control-T toggle, if Lynx has been compiled to log

+ the trace and other stderr messages. If not, ability to

+ create a log can be toggled on with the -tlog switch.

+ Note that this ability is disabled in anonymous or validation

+ accounts.

+ <dt>*

+ <dd>The '*' command toggles image_links mode on and off.

+ When on, links will be created for all images, including inlines.

+ 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.

+ <dt>@

+ <dd>The '@' 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.

+ <dt>[

+ <dd>The '[' command 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 Lynx

+ display. When off, they will be treated as having ALT="" (i.e.,

+ they'll 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.

+ <dt>]

+ <dd>The ']' 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.

+ <dt>^K

+ <dd>Control-K invokes the <a

+ href="keystrokes/cookie_help.html">Cookie Jar Page</a>

+ if it contains cookies.

+ <dt>z

+ <dd>Lynx supports completely interruptible I/O processes. Press the

+ 'z' 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.

+ <dt>numbers

+ <dd>Lynx offers other, advanced navigation features when numbers

+ are used to invoke the <a

+ href="keystrokes/follow_help.html"

+ >Follow link (or goto link or page) number:</a> or

+   <a

+ href="keystrokes/follow_help.html#select-option"

+ >Select option (or page) number:</a>

+ prompts.

+ [<A HREF="#TOC">ToC</A>]

+</dl>

+<h2><A NAME="19">Lynx and HTML Forms</a></h2>

+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.

+An HTML Form provides for the use of buttons to perform an action

+(such as submit), checkboxes, radio buttons or popups to select

+options from a list, and fields for entering text.

+

+<dl>

+<dt>Buttons:

+<dd>Buttons are displayed in the same way that Lynx displays links in

+ a document. To "push" the button press the right-arrow or

+ Return key. If it is a form submission button, you also can

+ use the RESUBMIT ('x') or DOWNLOAD ('d') keystroke

+ commands to "push" the button (see below).

+<dt>Checkboxes and Radio buttons

+<dd>Checkboxes are displayed as square brackets: [ ] and radio

+ buttons are displayed as parenthesis: ( ). When a box is

+ checked or a button selected, an x appears in the brackets:

+ [x] or an asterisk appears within the parenthesis:

+ (*). To check a box or select a radio button press the

+ right-arrow or Return key.

+<dt>Selection Fields

+<dd>Selection fields are displayed as brackets with the default option

+ displayed between them: [default__]. To select an option

+ press the right-arrow or Return 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

+ up-arrow, down-arrow, page-up,

+ page-down, and other navigation keys to move the cursor

+ among options, and the right-arrow or Return key to

+ select an option. You also can use the '/' and 'n'ext

+ <a href="#11">searching</a> commands for navigating to options which

+ contain particular strings. NOTE that the popup menu

+ feature can be disabled via compilation and/or configuration options,

+ or via the <a href="#12">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

+ -popup command line switch.

+<dt> Text Entry Fields

+<dd>Text entry (INPUT) fields are displayed as a row of underscores the

+ length of the entry field: _______. 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 up-arrow, and down-arrow,

+ TAB or Return keys to move up, or down from the text

+ entry field. NOTE, however, that Return also will <a

+ href="#submit">submit</a> the form if the text entry field is the

+ only non-hidden field in the form.

+<dd>TEXTAREA fields are 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 up-arrow, and

+ down-arrow or Return keys move you to the preceding,

+ or next line of the overall message, as for INPUT fields, and the

+ TAB key will move you down beyond the bottom of the TEXTAREA

+ field, or to the first line on the next page if the overall field

+ extends beyond the currently displayed page.

+</dl>

+In general, you can move around the form using the standard Lynx navigation

+keys. The up-arrow and down-arrow keys, respectively,

+select the previous or next field, box, or button. The TAB key

+selects the next field (or next page of a TEXTAREA if it extends onto the

+next page), box, or button.

+NOTE: 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.

+To <A name="submit">submit</a> the form press

+right-arrow or Return 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

+GET, 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 RESUBMIT command ('x') when

+positioned on the submit button. The right-arrow and Return

+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:

+<tab indent="12"

+><META HTTP-EQUIV="Pragma" CONTENT="no-cache">

+<tab indent="12"

+><META HTTP-EQUIV="Cache-Control" CONTENT="no-cache">

+or the server sent a "Pragma" or "Cache-Control" MIME header with a

+no-cache directive.

+You also can use the DOWNLOAD ('d') 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.

+Forms which have POST as the METHOD, or a <a

+href="lynx_url_support.html#mailto">mailto:</a> URL as the ACTION, are always

+resubmitted, even if the content has not changed, when you activate the

+submit button. Lynx normally will not resubmit a form which has

+POST as the METHOD if the document returned by the form has links

+which you activated, and then you go back via the PREV_DOC

+(left-arrow) 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 lynx.cfg, and toggled via the

+-resubmit_posts command line switch.

+If the form has one text entry field and no other fields except,

+possibly, hidden INPUT fields not included in the display, then that field

+also serves as a submit button, and pressing right-arrow

+or Return on that field will invoke submission of the form. Be

+sure to use up-arrow, down-arrow or TAB 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 GET).

+Forms can have multiple submit 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.

+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="#28">image maps</a>, and the x,y coordinates of

+the graphic client's cursor position in the image when it was

+clicked 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. Document

+authors who use images as submit buttons, but have at least some concern

+for text clients and sight-challenged Webizens, should include VALUEs for

+the buttons in such markup. Lynx will then display the string assigned

+to the VALUE, as it would for a normal submit button. Some document

+authors incorrectly use an ALT instead of VALUE attribute for this purpose.

+Lynx "cooperates" by treating ALT as a synonym for VALUE when present in

+an INPUT tag with TYPE="image". If neither a VALUE nor an ALT attribute

+is present, Lynx displays "[IMAGE]-Submit" as the string for such buttons.

+If clickable images is set, the "[IMAGE]" portion of the string is a link

+for the image, and the "Submit" portion is the button for submitting the

+form. Otherwise, the entire string is treated as a submit button. If

+a VALUE or ALT attribute is present and clickable images is set, Lynx

+prepends "[IMAGE]" as a link for the image, followed by '-' and then

+the attribute's value as the displayed string for the submit button.

+Note that earlier versions of Lynx would send a name=value pair instead of

+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.

+Forms can have hidden 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/Contents.html">HTML 3.0</a>

+DISABLED attribute for all 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.

+Forms most commonly are submitted to http servers with the content encoded

+as ENCTYPE="application/x-www-form-urlencoded" 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">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 ENCTYPE="text/plain" in the form markup, so that

+the content will not be encoded, but remain readable as plain text.

+Lynx also supports ENCTYPE="application/sgml-form-urlencoded"

+for which all reserved characters in the content will be hex escaped, as

+with application/x-www-form-urlencoded, but semicolons

+(';') instead of ampersands ('&') will be used as

+the separator for name=value pairs in the form content. The use of

+semicolons is preferred for forms with the GET METHOD, because

+the GET METHOD causes the encoded form content to be appended

+as a ?searchpart for the form's ACTION, and if such URLs are used

+in text/html documents or bookmark files without conversion

+of the ampersands to SGML character references (&amp; or

+&#38;), their being followed by form field NAMEs which might

+correspond to SGML entities could lead to corruption of the intended URL.

+NOTE, in this regard, that Lynx converts ampersands to &amp;

+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 GET METHOD,

+and which thus have the content appended as a ?searchpart, but not

+if the METHOD was POST, because the content would be lost and the

+link thus would be invalid.

+Lynx supports ENCTYPE="multipart/form-data" 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 TYPE="file" or TYPE="range" and

+will set the DISABLED attribute for all of the form's fields if

+any INPUTs with either of those two TYPEs are present, so that the form

+can't be submitted. Otherwise, Lynx will submit the form with the multipart

+ENCTYPE.

+A Content-Disposition: file; filename=name.suffix

+header can be used by CGI scripts to set the suggested filename offered

+by Lynx for 'd'ownload and 'p'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:

+<tab indent="12"

+><META <tab id="cdis">HTTP-EQUIV="Content-Disposition"

+<tab to="cdis">CONTENT="file; filename=name.suffix">

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="20">Lynx and HTML Tables</a></h2>

+HTML includes markup for creating tables structured as arrays of

+cells aligned by columns and rows on the displayed page.

+Lynx recognizes the TABLE element and all of its associated elements

+as described in <a href="ftp://ds.internic.net/rfc/rfc1942.txt"

+>ftp://ds.internic.net/rfc/rfc1942.txt</a>

+and will process any ID attributes in the start tags for handling as NAME-ed

+anchors, but does not create actual tables. 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 table readable, preserves most of the

+intra-cell organization, and makes all of the links in the table

+accessible, but any information critically dependent on the column and row

+alignments intended for the table will be missed.

+If inherently tabular data must be presented with Lynx, one can use PRE

+formatted content, or, if the table includes markup not allowed

+for PRE content, construct the table using <a

+href="#21">HTML Tabs</a>. An example table using TAB

+elements is included in the test subdirectory of the Lynx distribution.

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="21">Lynx and HTML Tabs</a></h2>

+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 en 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

+table using TAB elements in the test subdirectory of the Lynx

+distribution as a model for using this functionality.

+Note that this Users Guide and the <a

+href="lynx_url_support.html">Supported URLs</a> page include TAB markup in

+a manner which degrades gracefully for WWW browsers which do not

+support it. Toggle to display of <a href="#8">source</a> and <a

+href="#11">search</a> for <tab to examine the use of TAB markup

+in these documents. [<A HREF="#TOC">ToC</A>]

+<h2><A NAME="22">Lynx and HTML Frames</a></h2>

+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

+frames.

+Lynx recognizes the Netscape and Microsoft Explorer FRAME, FRAMESET,

+and NOFRAMES elements, but is not capable of windowing to create the

+intended positioning of frames. Instead, Lynx creates labeled

+links to the frame 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 frame 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.

+[<A HREF="#TOC">ToC</A>]

+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.

+<h2><A NAME="23">Lynx and HTML Banners</a></h2>

+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 banners.

+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 banner, and

+a number of others which have subsequently been proposed. These

+banner tokens are Home, ToC, Contents,

+Index, Glossary, Copyright, Up,

+Next, Previous, Prev, Help,

+Search, Top, Origin, Navigator,

+Child, Disclaimer, Sibling, Parent,

+Author, Editor, Publisher, Trademark,

+Meta, URC, Hotlist, Begin,

+First, End, Last, Pointer,

+Translation, Definition, Chapter,

+Documentation, Biblioentry, Bibliography,

+Bookmark and Banner. Any LINK elements with those

+tokens as the REL attribute value, and an HREF attribute value in the LINK,

+will invoke creation of a banner 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, it's value will be

+used as the link name instead of the default. Bookmark and

+Banner are intended to be accompanied by a TITLE attribute,

+which in effect makes the namespace for REL banner tokens

+infinite.

+If the special token Help is used as the REL value and no HREF

+is included in the LINK, Lynx will use it own HELPFILE URL for that

+link. For the special token Home without an HREF, Lynx will use

+the default STARTFILE (i.e., derived from the configuration files

+or the WWW_HOME environment variable, not the command line

+startfile if one was used). However, if a -homepage=URL

+was specified on the command line, it's URL will be used as the HREF.

+For the special token Index without an HREF, Lynx will use the

+DEFAULT_INDEX_FILE derived from the configuration files, or if an

+-index=URL was specified on the command line, it's URL will be used

+as the HREF.

+Lynx does not waste screen real estate maintaining the banner at

+the top of every page, but the Lynx TOOLBAR keystroke command ('#')

+will, any time it is pressed, position you on the banner so that

+any of its links can be activated, and pressing the left-arrow when

+in the banner will return you to where you were in the current

+document. The toolbar is indicated by a '#" 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 '#' at the top, left-hand corner of the screen when the second

+or subsequent pages of the document are being displayed.

+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 banner 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 it's markup as a static banner, without any horizontal

+scrolling of its content). Lynx does not prefix the BANNER or MARQUEE

+content with a '#' because the content need not be only a series

+of links with brief, descriptive links names, but does add a '#'

+at the top, left-hand corner of the screen when the content is not being

+displayed, to indicate it's accessibility via the TOOLBAR keystroke command.

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="24">Lynx and HTML Footnotes</a></h2>

+Lynx implements the <a

+href="http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a>

+FN element similarly to a named Anchor within the current document,

+and assumes that the footnotes will be positioned at the bottom of the

+document. However, in contrast to named Anchors, 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 FOOTNOTE:

+label. For example, if the document contains:

+<tab indent="16">See the <A

+HREF="#fn1"><a href="#an1">footnote</a></A>.

+activating that link will take you to the labeled rendering of:

+<tab indent="16"><FN ID="fn1"><a name="an1">Lynx

+does not use popups for FN blocks.</a></FN>

+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

+left-arrow key. The content of an FN element can be any HTML

+markup that is valid in the BODY of the document.

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="25">Lynx and HTML Notes</a></h2>

+Lynx implements the <a

+href="http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a>

+NOTE element (Admonishment) 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 NOTE: will be used. Lynx recognizes the values

+caution and warning, for which, respectively, the labels

+CAUTION: or WARNING: will be used. The NOTE element can

+have an ID attribute, which will be treated as a named Anchor, as

+for <a href="#24">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:

+<tab indent="12"><NOTE CLASS="warning" ID="too-bad">

+<tab indent="14">The W3C vendors did not retain

+NOTE in the HTML 3.2 draft.

+<tab indent="12"></NOTE>

+It will degrade gracefully for WWW browsers which do not support

+NOTE, except for recognition of the ID attribute as a named Anchor.

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="26">Lynx and HTML Lists</a></h2>

+Lynx implements the <a

+href="http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a>

+list elements UL (Unordered List), OL (Ordered List),

+and DL (Definition List), 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 both are treated as synonyms

+for UL with the PLAIN attribute (no bullets, 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 CAPTION: or

+CREDIT: 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.

+Lynx also supports the TYPE attribute for OL elements, which can have

+values of 1 for Arabic numbers, I or i for

+uppercase or lowercase Roman numerals, or A or a 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.

+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

+-29997 to the system's maximum positive integer for Arabic numbers.

+For Roman numerals, they can range from 1 (I or i)

+to 3000 (MMM or mmm.). For alphabetical orders,

+the values can range from 1 (A or a) to

+18278 (ZZZ or zzz). 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

+1, and if you do not include a TYPE attribute, Lynx defaults to

+Arabic numbers.

+For UL blocks without the PLAIN attribute, Lynx uses *,

++, o, #, @ and - as

+bullets to indicate, progressively, the depth within the six

+nesting levels.

+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.

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="27">Lynx and HTML Quotes</a></h2>

+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 it's 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.

+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 CREDIT: label at the beginning of

+its first line.

+Lynx respects nested Q start and end tags, and will use ASCII double-quotes

+(") versus grave accent (`) and apostrophe

+('), respectively, for even versus odd depths in the nest.

+Any ID attributes in BLOCKQUOTE, BQ or Q elements will be treated as

+named Anchors. [<A HREF="#TOC">ToC</A>]

+<h2><A NAME="28">Lynx and Client-Side-Image-Maps</a></h2>

+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 clicked 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 click, for handling by a script invoked by

+the server, and have been termed server-side-image-maps. 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.

+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

+client-side-image-maps.

+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 [USEMAP] 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.

+If the IMG element also indicates a server-side-image-map

+via an ISMAP attribute, Lynx normally will create a link for that as well,

+using an [ISMAP] pseudo-ALT (followed by a hyphen to indicate its

+association with the client-side-image-map) rather than ignoring

+it, and will submit a 0,0 coordinate pair if that link is activated.

+Although, the client-side-image-map 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 (lynx.cfg), and the

+default can be toggled via the -ismap command line switch.

+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 client-side-image-maps, 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.

+The presently experimental OBJECT element encompasses much of the

+functionality of the FIG element for client-side-image-maps.

+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

+client-side-image-maps and/or server-side-image-maps.

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="29">Lynx and Client-Side-Pull</a></h2>

+HTML includes provision for passing instructions to clients via directives

+in META elements, and one such instruction, via the token Refresh,

+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

+client-side-pull. An example of such an element is:

+<tab indent="12"><META HTTP-EQUIV="Refresh" CONTENT="3;

+URL="http://host/path">

+which instructs a client to fetch the indicated URL in 3 seconds after

+receiving the current document. If the URL= field is omitted,

+the URL defaults to that of the current document. A no-cache

+directive is implied when the Refresh if for the same URL.

+Lynx recognizes and processes Refresh 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.

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="30">Lynx State Management</A>

+(Me want cookie!)</h2>

+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="#19"

+>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 Set-Cookie MIME header which contains

+information (cookies) relevant to the browser's request, and in

+subsequent requests the browser can send a Cookie MIME header

+with information derived from previously received cookies.

+State Management via cookie exchanges originally was implemented by

+Netscape, and such cookies are now designated as Version 0. A

+more elaborate format for cookies, designated as Version 1, is

+being standardized by the IETF (Internet Engineering Task Force). Lynx

+supports both Version 0 and Version 1 cookie exchanges.

+This support can be disabled by default via the SET_COOKIES symbol in the

+compilation (userdefs.h) and/or run time (lynx.cfg)

+configuration files, and that default setting can be toggled via the

+-cookies command line switch.

+When cookie support is enabled, Set-Cookie MIME headers

+received from an http server invoke confirmation prompts with possible

+replies of 'Y'es or 'N'o for acceptance of the cookie,

+'A'lways to accept the cookie and to allow all subsequent

+cookies from that domain (server's Fully Qualified Domain Name,

+or site-identifying portion of the FQDN) without further confirmation

+prompts, or ne'V'er to never allow cookies from that

+domain to be accepted (silently ignore its Set-Cookie

+MIME headers). All unexpired cookies are held in a hypothetical

+Cookie Jar which can be examined via the COOKIE_JAR keystroke

+command, normally mapped to Ctrl-K, for invoking the <a

+href="keystrokes/cookie_help.html">Cookie Jar Page</a>. The

+Cookie Jar, and any 'A'lways or ne'V'er

+'allow' settings, do not presently outlast the Lynx session.

+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 From 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.

+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.

+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 Gobble (delete) the cookies

+and/or change the 'allow' setting for its domain via the <a

+href="keystrokes/cookie_help.html">Cookie Jar Page</a>.

+[<A HREF="#TOC">ToC</A>]

+<h2><A NAME="31">The Lynx command line</A></h2>

+A summary of the Lynx command line options (switches) is returned to

+stdout if Lynx is invoked with the -help 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:

+<dl>

+ <dt><code>Command</code>

+ <dd><code>lynx [options]</code>

+ <dd><code>lynx [options] startfile</code>

+</dl>

+where

+<dl>

+ <dt><code>startfile</code>

+ <dd>is the file or URL that Lynx will load at start-up.

+ <ul>

+ <li>If startfile is not specified, Lynx will use a default

+ starting file and base directory determined during

+ installation.

+ <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>If a URL is specified, the file will be retrieved,

+ and only the server base directory will be relevant

+ to further accesses.

+ </ul>

+ <dt><code>options</code>

+ <dd>can be selected from the following list, where items in

+ all-caps indicate that a substitution must be made.

+ <dl>

+ <dt><code>-</code>

+ <dd>If the argument is only '<code>-</code>' (dash), then Lynx

+ expects to receive the arguments from stdin. This is to

+ allow for the potentially very long command line that can

+ be associated with the -get_data or

+ -post_data arguments (see below). On VMS, it

+ must be encased in double-quotes ("-") and the

+ keyboard input terminated with Control-Z or the

+ command file input terminated by a line that begins

+ with '$'. On Unix, the keyboard input terminator

+ is Control-D. On Win32, [???].

+ <dt><code>-anonymous</code>

+ <dd>used to specify the anonymous account.

+ <dt><code>-assume_charset=MIMEname</code>

+ <dd>charset for documents that don't specify it.

+ <dt><code>-assume_local_charset=MIMEname</code>

+ <dd>charset assumed for local files.

+ <dt><code>-assume_unrec_charset=MIMEname</code>

+ <dd>use this instead of unrecognized charsets.

+ <dt><code>-auth=ID:PW</code>

+ <dd>set authorization ID and password for protected documents

+ at startup. Be sure to protect any script files which use

+ this switch.

+ <dt><code>-base</code>

+ <dd>prepend a request URL comment and BASE tag to text/html

+ outputs for -source dumps.

+ <dt><code>-blink</code>

+ <dd>forces high intensity bg colors for color mode,

+ if available and supported by the terminal.

+ Lynx needs to be compiled with the slang library for this

+ flag.

+ <dt><code>-book</code>

+ <dd>use the bookmark page as the startfile. The default or

+ command line startfile is still set for the Main screen

+ command, and will be used if the bookmark page is

+ unavailable or blank.

+ <dt><code>-buried_news</code>

+ <dd>toggles scanning of news articles for buried references,

+ and converts them to news links. Not recommended because

+ email addresses enclosed in angle brackets will be

+ converted to false news links, and uuencoded messages can

+ be trashed.

+ <dt><code>-cache=NUMBER</code>

+ <dd>set the NUMBER of documents cached in memory.

+ The default is 10.

+ <dt><code>-case</code>

+ <dd>enable case-sensitive string searching.

+ <dt><code>-cfg=FILENAME</code>

+ <dd>specifies a Lynx configuration file other than the default

+ lynx.cfg.

+ <dt><code>-child</code>

+ <dd>exit on left-arrow in startfile, and disable save to disk.

+ <dt><code>-color</code>

+ <dd>forces color mode on, if available. Default color control sequences

+ which work for many terminal types are assumed if the terminal

+ capability description does not specify how to handle color.

+ Lynx needs to be compiled with the slang library for this flag.

+ A saved show_color=always setting found in a .lynxrc file at

+ startup has the same effect. A saved show_color=always found

+ in .lynxrc on startup is overridden by this flag.

+ <dt><code>-cookies</code>

+ <dd>toggles handling of Set-Cookie headers.

+ <dt><code>-core</code>

+ <dd>toggles forced core dumps on fatal errors. (Unix only)

+ <dt><code>-crawl</code>

+ <dd>with -traversal, output each page to a file.

+ with -dump, format output as with

+ -traversal, but to stdout.

+ <dt><code>-display=DISPLAY</code>

+ <dd>set the display variable for X rexe-ced programs.

+ <dt><code>-dump</code>

+ <dd>dumps the formatted output of the default document

+ or one specified on the command line to standard out.

+ This can be used in the following way:

+ lynx -dump http://www.w3.org/

+ <dt><code>-editor=EDITOR</code>

+ <dd>enable edit mode using the specified

+ EDITOR. (vi, ed, emacs, etc.)

+ <dt><code>-emacskeys</code>

+ <dd>enable emacs-like key movement.

+ <dt><code>-enable_scrollback</code>

+ <dd>toggles behavior compatible with the scrollback keys in

+ some communications software (may be incompatible with

+ some curses packages).

+ <dt><code>-error_file=FILENAME</code>

+ <dd>the status code from the HTTP request is placed in this

+ file.

+ <dt><code>-locexec</code>

+ <dd>enable local program execution from local files only

+ (if lynx was compiled with local execution enabled).

+ <dt><code>-fileversions</code>

+ <dd>include all versions of files in local VMS directory

+ listings.

+ <dt><code>-force_html</code>

+ <dd>forces the first document to be interpreted as HTML.

+ <dt><code>-force_secure</code>

+ <dd>toggles forcing of the secure flag for SSL cookies.

+ <dt><code>-from</code>

+ <dd>toggles transmissions of From headers to HTTP or HTTPS

+ servers.

+ <dt><code>-ftp</code>

+ <dd>disable ftp access.

+ <dt><code>-get_data</code>

+ <dd>properly formatted data for a get form are read in from

+ stdin and passed to the form. Input is terminated by a

+ line that starts with '---'.

+ <dt><code>-head</code>

+ <dd>send a HEAD request for the mime headers.

+ <dt><code>-help</code>

+ <dd>print this Lynx command syntax usage message.

+ <dt><code>-historical</code>

+ <dd>toggles use of '>' or '-->' as a terminator for

+ comments.

+ <dt><code>-homepage=URL</code>

+ <dd>set homepage separate from start page. Will be used

+ if a fetch of the start page fails or if it is a

+ script which does not return a document, and as the

+ <code>URL</code> for the 'm'ain menu command.

+ <dt><code>-image_links</code>

+ <dd>toggles inclusion of links for all images.

+ <dt><code>-ismap</code>

+ <dd>toggles inclusion of ISMAP links when client-side

+ MAPs are present.

+ <dt><code>-index=URL</code>

+ <dd>set the default index file to the specified URL

+ <dt><code>-link=NUMBER</code>

+ <dd>starting count for lnk#.dat files produced by

+ -crawl.

+ <dt><code>-localhost</code>

+ <dd>disable URLs that point to remote hosts.

+ <dt><code>-mime_header</code>

+ <dd>include mime headers and force source dump.

+ <dt><code>-minimal</code>

+ <dd>toggles minimal versus valid comment parsing. When

+ minimal, any '-->' serves as a terminator for a

+ comment element. When valid, pairs of '--' are

+ treated as delimiters for series of comments within

+ the overall comment element. If historical is set,

+ that overrides minimal or valid comment parsing.

+ <dt><code>-newschunksize=NUMBER</code>

+ <dd>number of articles in chunked news listings.

+ <dt><code>-newsmaxchunk=NUMBER</code>

+ <dd>maximum news articles in listings before chunking.

+ <dt><code>-nobrowse</code>

+ <dd>disable directory browsing.

+ <dt><code>-nocc</code>

+ <dd>disable Cc: prompts for self copies of mailings. Note

+ that this does not disable any CCs which are incorporated

+ within a mailto URL or form ACTION.

+ <dt><code>-nocolor</code>

+ <dd>force color mode off, overriding terminal capabilities and any

+ -color flags, COLORTERM variable, and saved .lynxrc settings.

+ <dt><code>-noexec</code>

+ <dd>disable local program execution. (DEFAULT)

+ <dt><code>-nofilereferer</code>

+ <dd>disable transmissions of Referer headers for file URLs.

+ <dt><code>-nolist</code>

+ <dd>disable the link list feature in dumps.

+ <dt><code>-nolog</code>

+ <dd>disable mailing of error messages to document owners.

+ <dt><code>-nopause</code>

+ <dd>disable forced pauses for statusline messages.

+ <dt><code>-noprint</code>

+ <dd>disable print functions.

+ <dt><code>-noredir</code>

+ <dd>don't follow URL redirections

+ <dt><code>-noreferer</code>

+ <dd>disable transmissions of Referer headers.

+ <dt><code>-nosocks</code>

+ <dd>disable SOCKS proxy usage by a SOCKSified Lynx.

+ <dt><code>-nostatus</code>

+ <dd>disable the retrieval status messages.

+ <dt><code>-number_links</code>

+ <dd>force numbering of links.

+ <dt><code>-pauth=ID:PW</code>

+ <dd>set authorization ID and password for a protected proxy

+ server at startup. Be sure to protect any script files

+ which use this switch.

+ <dt><code>-popup</code>

+ <dd>toggles handling of single-choice SELECT options via

+ popup windows or as lists of radio buttons. The default

+ configuration can be changed in userdefs.h or lynx.cfg.

+ It also can be set and saved via the 'o'ptions menu.

+ The command line switch toggles the default.

+ <dt><code>-post_data</code>

+ <dd>properly formatted data for a post form are read in from

+ stdin and passed to the form. Input is terminated by a

+ line that starts with '---'.

+ <dt><code>-preparsed</code>

+ <dd>show source preparsed and reformatted when used with

+ -source or in source view ('\').

+ <dt><code>-print</code>

+ <dd>enable print functions. (default)

+ <dt><code>-pseudo_inlines</code>

+ <dd>toggles pseudo-ALTs for inlines with no ALT string.

+ <dt><code>-raw</code>

+ <dd>toggles default setting of 8-bit character translations

+ or CJK mode for the startup character set.

+ <dt><code>-realm</code>

+ <dd>restricts access to URLs in the starting realm.

+ <dt><code>-reload</code>

+ <dd>flushes the cache on a proxy server

+ (only the first document affected).

+ <dt><code>-restrictions</code>

+ <dd>allows a list of services to be disabled

+ selectively and takes the following form:

+ <dd>lynx -restrictions=[option][,option][,option]...

+ <dd>This list is printed if no options are specified.

+ <dl>

+ <dt>all

+ <dd>restricts all options.

+ <dt>bookmark

+ <dd>disallow changing the location of the bookmark

+ file.

+ <dt>bookmark_exec

+ <dd>disallow execution links via the bookmark file.

+ <dt>change_exec_perms

+ <dd>disallow changing the eXecute permission on

+ files (but still allow it for directories) when

+ local file management is enabled.

+ <dt>default

+ <dd>same as command line option -anonymous.

+ Disables default services for anonymous users.

+ Currently set to all restricted except for:

+ inside_telnet, outside_telnet, inside_news,

+ inside_ftp, outside_ftp, inside_rlogin,

+ outside_rlogin, jump, mail and goto. Defaults

+ are settable within userdefs.h.

+ <dt>dired_support

+ <dd>disallow local file management.

+ <dt>disk_save

+ <dd>disallow saving to disk in the download and print

+ menus.

+ <dt>download

+ <dd>disallow downloaders in the download menu.

+ <dt>editor

+ <dd>disallow editing.

+ <dt>exec

+ <dd>disable execution scripts.

+ <dt>exec_frozen

+ <dd>disallow the user from changing the local

+ execution option.

+ <dt>file_url

+ <dd>disallow using G)oto, served links or bookmarks

+ for file: URLs.

+ <dt>goto

+ <dd>disable the 'g' (goto) command.

+ <dt>inside_ftp

+ <dd>disallow ftps for people coming from inside your

+ domain.

+ <dt>inside_news

+ <dd>disallow USENET news posting for people coming

+ from inside you domain.

+ <dt>inside_rlogin

+ <dd>disallow rlogins for people coming from inside

+ your domain.

+ <dt>inside_telnet

+ <dd>disallow telnets for people coming from inside

+ your domain.

+ <dt>jump

+ <dd>disable the 'j' (jump) command.

+ <dt>mail

+ <dd>disallow mailing feature.

+ <dt>multibook

+ <dd>disallow multiple bookmarks.

+ <dt>news_post

+ <dd>disallow USENET News posting.

+ <dt>options_save

+ <dd>disallow saving options in .lynxrc.

+ <dt>outside_ftp

+ <dd>disallow ftps for people coming from outside your

+ domain.

+ <dt>outside_news

+ <dd>disallow USENET news posting for people coming

+ from outside you domain.

+ <dt>outside_rlogin

+ <dd>disallow rlogins for people coming from outside

+ your domain.

+ <dt>outside_telnet

+ <dd>disallow telnets for people coming from

+ outside your domain.

+ <dt>print

+ <dd>disallow most print options.

+ <dt>shell

+ <dd>disallow shell escapes.

+ <dt>suspend

+ <dd>disallow Control-Z suspends with escape

+ to shell on Unix.

+ <dt>telnet_port

+ <dd>disallow specifying a port in telnet G)oto's.

+ <dt>useragent

+ <dd>disallow modifications of the User-Agent header.

+ </dl>

+ <dt><code>-resubmit_posts</code>

+ <dd>toggles forced resubmissions (no-cache) of forms with

+ method POST when the documents they returned are sought

+ with the PREV_DOC (left-arrow) command or from

+ the History Page.

+ <dt><code>-rlogin</code>

+ <dd>disable recognition of rlogin commands.

+ <dt><code>-selective</code>

+ <dd>require .www_browsable files to browse directories.

+ <dt><code>-show_cursor </code>

+ <dd>If enabled the cursor will not be hidden in the right hand

+ corner but will instead be positioned at the start of the

+ currently selected link. Show cursor is the default for

+ systems without FANCY_CURSES capabilities. The default

+ configuration can be changed in userdefs.h or lynx.cfg.

+ It also can be set and saved via the 'o'ptions menu.

+ The command line switch toggles the default.

+ <dt><code>-soft_dquotes</code>

+ <dd>toggles emulation of the old Netscape and Mosaic bug which

+ treated '>' as a co-terminator for

+ double-quotes and tags.

+ <dt><code>-source</code>

+ <dd>works the same as dump but outputs HTML source instead of

+ formatted text.

+ <dt><code>-startfile_ok</code>

+ <dd>allow non-http startfile and homepage with

+ -validate.

+ <dt><code>-telnet</code>

+ <dd>disable recognition of telnet commands.

+ <dt><code>-term=TERM</code>

+ <dd>tell Lynx what terminal type to assume its 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.)

+ <dt><code>-tlog</code>

+ <dd>toggles use of a Lynx Trace Log for the current

+ session. The log is named lynx.trace and is

+ created in the home directory when Lynx trace mode is

+ turned on via the -trace command line switch

+ (see below), or via the TOGGLE_TRACE (Control-T)

+ 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, ';')

+ keystroke command.

+ <dt><code>-trace</code>

+ <dd>turns on Lynx trace mode. If a Lynx Trace Log

+ (lynx.trace in the home directory) has

+ been started for the current session, all trace and

+ other stderr messages are written to that log, and

+ can be examined during the session via the TRACE_LOG

+ (normally, ';') command.

+ <dt><code>-traversal</code>

+ <dd>traverse all http links derived from startfile. When

+ used with -crawl, each link that begins with the

+ same string as startfile is output to a file, intended for

+ indexing. See CRAWL.announce for more information.

+ <dt><code>-underscore</code>

+ <dd>toggles use of _underline_ format in dumps.

+ <dt><code>-useragent=Name</code>

+ <dd>set alternate Lynx User-Agent header.

+ <dt><code>-validate</code>

+ <dd>accept only http URLs (for validation). Complete

+ security restrictions also are implemented.

+ <dt><code>-version</code>

+ <dd>print version information

+ <dt><code>-vikeys</code>

+ <dd>enable vi-like key movement.

+ <dt><code>-width=NUMBER</code>

+ <dd>number of columns for formatting of dumps, default is 80.

+ </dl>

+</dl>

+No options are required, nor is a startfile argument required.

+White space may be substituted for any equal sign ('=')

+appearing in the option list above. [<A HREF="#TOC">ToC</A>]

+<h2><A NAME="32">Lynx development history</A></h2>

+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.

+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.

+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.

+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.

+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.

+Foteos Macrides 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.

+The Lynx2-3FM code set was released as v2.4 in June 1995.

+The Lynx2-4FM code set was released as v2.5 in May 1996.

+The Lynx2-5FM code set was released as v2.6 in September 1996.

+The Lynx2-6FM code set was released as v2.7 in February 1997.

+The v2-7FM code set was released as v2.7.1 in April 1997.

+The v2-7-1FM code set was released as v2.7.2 in January 1998.

+The 2.7.1 development set was released as v2.8 in March 1998.

+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.

+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.

+Contributors have generally been acknowledged in the CHANGES

+file. Earlier CHANGES file can be found in the docs/ subdirectory

+of this distribution.

+Information on obtaining the most current version of Lynx is available

+at <a href="http://www.slcc.edu/lynx/current/index.html">the current distribution page</a>.

+[<A HREF="#TOC">ToC</A>]

+</body>

+</html>

diff --git a/gnu/usr.bin/lynx/lynx_help/about_lynx.html b/gnu/usr.bin/lynx/lynx_help/about_lynx.html
new file mode 100644
index 00000000000..33faa7cd96b
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/about_lynx.html

@@ -0,0 +1,97 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>About Lynx</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<BANNER>

+[ <A HREF="lynx-dev.html">About Lynx-Dev</A> |

+<A HREF="http://www.flora.org/lynx-dev/html/">Lynx-Dev Archives</A> ]

+</BANNER>

+<h1>About Lynx</h1>

+Lynx is a fully featured World-Wide Web browser for users on both Unix and

+VMS platforms who are connected to those systems via cursor-addressable,

+character-cell terminals or emulators. That includes VT100 terminals,

+and desktop-based software packages emulating VT100 terminals (e.g.,

+Kermit, Procomm, etc.).

+For information on how to use Lynx see the

+<A HREF="../lynx_help/Lynx_users_guide.html">Lynx User's Guide</A>, or the

+<A HREF="../lynx_help/lynx_help_main.html">Lynx help files</A>.

+<H2>Credits and Copyright</H2>

+Lynx was a product of the Distributed Computing Group within

+Academic Computing Services of <A

+HREF="http://www.cc.ukans.edu/index.html">The University of Kansas</A>.

+Lynx was originally developed by

+<A HREF="http://www.cc.ukans.edu/cwis/people/Lou.Montulli.html"

+>Lou Montulli,</A>

+<A HREF="http://www.cc.ukans.edu/cwis/people/Michael.Grobe/Michael.Grobe.html"

+>Michael Grobe,</A>

+and <A HREF="http://www.cc.ukans.edu/cwis/people/Charles.Rezac.html"

+>Charles Rezac.</A>

+<A HREF="http://www.cc.ukans.edu/cwis/people/Garrett/Garrett_Arch_Blythe.html"

+>Garrett Blythe</A> created

+<A HREF="http://www.cc.ukans.edu/about_doslynx/doslynx.html">DosLynx</A>

+and later joined the Lynx effort as well. Following the departures of

+Lou and Garrett for positions at Netscape in the summer of 1994,

+Craig Lavender provided support services for Lynx, and

+Ravikumar Kolli for DosLynx.

+Currently Lynx is being maintained and supported by members of the

+Internet community coordinated via the

+<A HREF="#lynx-dev_list">lynx-dev mailing list</A>.

+Lynx is copyrighted by the University of Kansas and is distributed

+<A HREF="COPYHEADER">without restrictions on usage or redistribution</A>

+under the <A HREF="COPYING">GNU General Public License</A>.

+Lynx was built over an early version of the Common Code Library

+developed by the CERN WWW Project. That code is copyrighted by CERN.

+Lynx contains other sections of code that are copyrighted

+by other institutions or individuals.

+The Lynx copyright does not override or invalidate those copyrights.

+Thanks to <A NAME="13"

+HREF="http://www.w3.org/hypertext/WWW/People.html#BernersLee"

+>Tim Berners-Lee</A> and the other <A NAME="14"

+HREF="http://www.w3.org/hypertext/WWW/People.html">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://www.ncsa.uiuc.edu/SDG/Software/Mosaic/NCSAMosaicHome.html"

+>Mosaic</A> developers, and to everyone out in netland who has

+contributed to Lynx's development either directly (through comments

+or bug reports) or indirectly (through inspiration and development of

+other systems).

+Also, special thanks go to Foteos Macrides who ported much of

+Lynx to VMS and did much of it's development following Lou Montulli's

+and Garrett Blythe's departures from the University of Kansas, and to

+Earl Fogel 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 Lynx which did not use the WWW libraries and

+had their own hypertext format.

+<H2><A NAME="availability">Availability</A></H2>

+Information on obtaining the most current version of Lynx is

+available via <a href="http://www.crl.com/~subir/lynx.html"

+>Lynx links</a>.

+<H2><A NAME="lynx-dev_list">Mailing List</A></H2>

+We have a listserv mailing list running for lynx 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://www.flora.org/lynx-dev/html/">archives</A> in html

+format for this mailing list.

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/bookmark_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/bookmark_help.html
new file mode 100644
index 00000000000..de08f3947f1
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/bookmark_help.html

@@ -0,0 +1,21 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Lynx Bookmark Help</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<h1>+++ Bookmark Help +++</h1>

+The Bookmark files are documents that resides on your local

+machine and you are able to edit and change. The append feature,

+invoked by pressing an 'a' while viewing a document will add

+the current document or the currently highlighted link to your default

+Bookmark file, or to one you select if multiple bookmarks are

+enabled. The remove feature, invoked by pressing an 'r' when

+a Bookmark file is being displayed, will remove the currently

+highlighted link. You may set and modify the paths and names of your

+Bookmark files, and enable or disable multiple bookmarks, in

+the <A HREF="option_help.html">options screen.</A>

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/cookie_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/cookie_help.html
new file mode 100644
index 00000000000..0fd5b255f4e
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/cookie_help.html

@@ -0,0 +1,51 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Help on the Cookie Jar Page</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<h1>+++ Cookie Jar Page Help +++</h1>

+The Cookie Jar Page displays all of the unexpired cookies you have

+accumulated in the hypothetical Cookie Jar. The cookies are

+obtained via Set-Cookie MIME headers in replies from http servers,

+and are used for <A HREF="../Lynx_users_guide.html#30">State Management</A>

+across successive requests to the servers.

+The cookies are listed by domain (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 path attribute of the cookie). When Lynx sends requests

+to an http server whose address tail-matches a domain in the

+Cookie Jar, all its cookies with a path which

+head-matches the path in the URL for that request are included as a

+Cookie MIME header. The 'allow' setting for accepting cookies

+from each domain (always, never, or via prompt) also is indicated in the

+listing.

+The listing also shows the port (normally 80) of the URL

+for the request which caused the cookie to be sent, and whether the

+secure flag is set for the cookie, in which case it will be

+sent only via secure connections (presently, only SSL). The

+Maximum Gobble Date, i.e., when the cookie is intended to

+expire, also is indicated. Note, however, that Lynx presently gobbles

+all of it's accumulated cookies on exit from the current session, even

+if the server indicated an expiration in the distant future. Also, a

+server may change the expiration date, or cause the cookie to be deleted,

+in its replies to subsequent requests from Lynx. If the server included

+any explanatory comments in its Set-Cookie MIME headers, those

+also are displayed in the listing.

+The domain=value pairs, and each cookie's name=value, are

+links in the listing. Activating a domain=value link will

+invoke a prompt asking whether all cookies in that domain

+should be Gobbled (deleted from the Cookie Jar),

+and/or whether the domain entry should be Gobbled

+if all of its cookies have been Gobbled, or whether to change

+the 'allow' setting for that domain. Activating a cookie's

+name=value link will cause that particular cookie to be Gobbled.

+You will be prompted for confirmations of deletions, to avoid any

+accidental Gobbling.

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/dired_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/dired_help.html
new file mode 100644
index 00000000000..eb1d1ae65c8
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/dired_help.html

@@ -0,0 +1,51 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<html>

+<head>

+<title>Lynx Dired Help</title>

+<link rev="made" href="mailto:lynx-dev@sig.net">

+</head>

+<body>

+<h1>+++DIRED HELP+++</h1>

+Lynx changes into Dired mode when you use a URL of the type

+file://localhost/path/. While in Dired mode, some keys are

+remapped to do the following functions:

+<pre>

+ C)reate - Create a new, empty file in the current

+ directory. You will be prompted to enter

+ a name for the file.

+ 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 screen</a>

+ and load selection for editing.

+ 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 't' again to untag

+ a file.

+ U)pload - Upload a file to the current directory using

+ one of the options listed in the upload

+ options screen.

+</pre>

+Note: Dired mode must be activated at compile time by the

+system administrator. Otherwise, the above commands will not be available

+and lynx will treat a directory listing as a HTML file.

+</body>

+</html>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/edit_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/edit_help.html
new file mode 100644
index 00000000000..52c081b2d20
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/edit_help.html

@@ -0,0 +1,40 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<html>

+<head>

+<title>Lynx Line Editor Default Key Binding</title>

+<link rev="made" href="mailto:lynx-dev@sig.net">

+</head>

+<body>

+<h1>+++DEFAULT BINDING+++</h1>

+Lynx invokes a built-in Line Editor for entering strings in

+response to prompts, in forms, and for email messages if an external editor

+has not been defined. Administrators can offer alternate key bindings

+by adding them in LYEditmap.c before compiling Lynx, and they can

+be selected via the 'o'ptions menu. This is the Default Binding:

+<pre>

+ ENTER Input complete - RETURN

+ TAB Input complete - TAB, Do

+ ABORT Input cancelled - Ctrl-G, Ctrl-O, Ctrl-C

+ ERASE Erase the line - Ctrl-U, Ctrl-X

+ 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 - Ctrl-H, DELETE, Remove

+ DELC Delete current char - Ctrl-D

+ DELN Delete next char - Ctrl-R

+ DELPW Delete prev word - Ctrl-B

+ DELNW Delete next word - Ctrl-F

+ LOWER Lower case the line - Ctrl-K

+ UPPER Upper case the line - Ctrl-T

+ LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only)

+</pre>

+</body>

+</html>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/follow_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/follow_help.html
new file mode 100644
index 00000000000..f30fbb7754b
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/follow_help.html

@@ -0,0 +1,132 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Help on the Follow link (or page) number feature</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<h1>+++ Follow link (or goto link or page) number Help +++

++++ Select option (or page) number Help +++</h1>

+If a user has set Keypad mode to Links are numbered

+or Links and form fields are numbered as the default or for

+the current session via the Options menu, then hypertext links

+(and form fields, depending on the keypad mode)

+are prefixed with numbers in square brackets. Entering a keyboard

+or keypad number is treated as an F_LINK_NUM command, and should

+invoke the Follow link (or goto link or page) number: statusline

+prompt for a

+potentially multiple digit number corresponding to an indicated link

+number. If RETURN is pressed to terminate the number entry (e.g.,

+123) and it corresponds to a hypertext link, Lynx 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. The prompt

+can be invoked via '0', but it will not be treated as the lead

+digit for the number entry, whereas '1' through '9' both

+invoke the prompt and are treated as the first digit. In Links and

+form fields are numbered 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.

+If the number entered at the prompt has a 'g' suffix (e.g.,

+123g), then Lynx 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 'g' suffix is implied (need

+not be entered) for form fields in Links and form fields are

+numbered mode.

+Alternatively, if the number is given a 'p' suffix (e.g.,

+123p), Lynx 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 'g' and 'p' suffixes thus

+convert the

+Follow link (or goto link or page) number: feature to an advanced

+navigation aid.

+If the user has set Keypad mode to Numbers act as arrows,

+then only '0', rather than every number, will be treated as an

+F_LINK_NUM command for invoking the Follow link (or goto link or page)

+number: prompt. The '0' will not be treated as the first

+digit for the number, or number plus suffix, entry.

+Numbers are associated with form fields only when Links and form

+fields are numbered mode has been selected. If you have selected

+Numbers act as arrows or Links are numbered 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.

+When you have invoked a popup window for a list of

+OPTIONs in a form's SELECT block, each OPTION is associated with a number,

+and that number will be displayed in Links and form fields are

+numbered mode. In any keypad mode, the F_LINK_NUM

+('0') command will invoke a Select option (or page)

+number: prompt, and you can enter a number, and optionally a

+'g' or 'p' suffix, to select or seek an OPTION in that

+list. If only an number is entered at the prompt, the corresponding OPTION

+will be selected and the popup will be retracted. If the 'g'

+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. For purposes of paging (e.g., in

+conjunction with the 'p' suffix), a page is defined as

+the number of OPTIONs displayed within the vertical dimension of the popup

+window.

+Note that HTML can be structured so that it includes hidden

+links, i.e., without a visible link name intended for ACTIVATE-ing

+the link. Such links may be created, for example, by 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. They also can be created by

+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. With the -ismap command line switch, Lynx will

+additionally treat a link to a server-side image maps as hidden if

+there also is a client-side map for the same image.

+Finally, in some cases links which are not intended to be hidden

+may effectively become hidden links because of bad HTML.

+The hidden links differ from Anchors which 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).

+Lynx respects instructions for hidden links and normally does

+not include them in the rendition of the document. However, if the command

+line switch -hiddenlinks=merge is used, such links will still be

+numbered in sequence with other links which are not hidden, and if Links

+are numbered 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

+-ismap). If -hiddenlinks=listonly or

+-hiddenlinks=ignore is in effect, hidden links will not be

+shown in the text even in links are numbered mode. Not using a

+-hiddenlinks flag at all is equivalent to

+-hiddenlinks=listonly.

+If a document includes

+hidden links, they will be reported, with appropriate labeling,

+in the menu created for the LIST ('l') command,

+unless -hiddenlinks=ignore is used. They can then be

+ACTIVATE-ed via that menu. Also, if a link was hidden due to an ALT

+attribute in an IMG element, it will be converted to a visible link

+whenever the IMAGE_TOGGLE ('*') command is used to create links

+for SRC attritute 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 browsers or

+other suitable software.

+HTML forms also can 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.

+Lynx respects this attribute as well, and neither displays the HIDDEN field,

+nor assigns it a number for the F_LINK_NUM ('0') command and

+Links and form fields are numbered keypad mode handling, nor

+includes an entry for it in the menu created for the LIST ('l')

+command. However, the HIDDEN name/value pairs are included in any displays

+of submitted form content in the Information about the current

+document that is invoked by the INFO ('=') command.

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/gopher_types_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/gopher_types_help.html
new file mode 100644
index 00000000000..629256e1347
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/gopher_types_help.html

@@ -0,0 +1,59 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Listing of Gopher types</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<h1>+++ Gopher Types +++</h1>

+<dl compact>

+<dt>(FILE)

+<dd>An ASCII file

+<dt>(DIR)

+<dd>A directory listing

+<dt>(CSO)

+<dd>The Computing Services Organizations

+nameserver interface

+<dt>(BIN)

+<dd>A binary file with one of the following meanings

+<ul>

+<li>A Binary file with PC extensions

+<li>A Binary file with UNIX extensions

+</ul>

+<dt>(HQX)

+<dd>A Macintosh file that has be BinHexed

+<dt>(?)

+<dd>A searchable database

+<dt>(IMG)

+<dd>An unknown image type

+You must have an <A HREF="xterm_help.html">X terminal</A> to

+view images

+<dt>(GIF)

+<dd>An image in Graphics Interchange Format

+You must have an <A HREF="xterm_help.html">X terminal</A> to

+view images

+<dt>(HTML)

+<dd>A World Wide Web hypertext file

+<dt>(TEL)

+<dd>The link will open a connection to another host using telnet

+<dt>(3270)

+<dd>The link will open a connection to another

+host using tn3270

+<dt>(UKN)

+<dd>An unknown or unsupported type

+</dl>

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/history_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/history_help.html
new file mode 100644
index 00000000000..c6e3010fdd4
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/history_help.html

@@ -0,0 +1,37 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Help on the History Page</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<h1>+++ History Page Help +++</h1>

+The 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

+left-arrow key, it will not be in the history stack.

+If you entered a document and left it by selecting another link within

+that document, it will be in the history stack.

+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 left-arrow key, if you wish to review previous

+documents without needing to remember and repeat the series of selections

+for reaching your currently displayed document.

+Upon using left-arrow in the document selected via the History

+Page, you will be returned to the document from which you initially went to

+the History Page.

+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 'd'ownloaded or passed to a helper

+application, and thus were not included in the history stack.

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/keystroke_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/keystroke_help.html
new file mode 100644
index 00000000000..f3a57bc35d9
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/keystroke_help.html

@@ -0,0 +1,104 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Help on Lynx Keystroke Commands</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<h1>+++ Keystroke Commands +++</h1>

+<PRE>

+ <A HREF="movement_help.html"

+ >MOVEMENT</A>: Down arrow - Highlight next topic

+ Up arrow - Highlight previous topic

+ Right arrow, - Jump to highlighted topic

+ Return, Enter

+ Left arrow - Return to previous topic

+ <A HREF="scrolling_help.html"

+ >SCROLLING</A>: + - 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 Toolbar or Banner in the current document

+ <A HREF="dired_help.html">DIRED</A>: c - Create a new file

+ d - Download selected file

+ e - Edit selected file

+ E - Edit the current link's URL (or ACTION) and

+ use that as a goto URL.

+ 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

+ <A HREF="other_help.html">OTHER</A>: ? (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

+ 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 a list of 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 'Q' 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

+ 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

+ [ - 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-V - Switch to alternative parsing of HTML documents

+ CTRL-W - Refresh the screen

+ CTRL-U - Erase input line

+ 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>

+ numbers - 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/gnu/usr.bin/lynx/lynx_help/keystrokes/movement_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/movement_help.html
new file mode 100644
index 00000000000..4655db31a76
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/movement_help.html

@@ -0,0 +1,49 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Help on Lynx Movement commands</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<H1>+++ MOVEMENT HELP +++</H1>

+<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.

+ *note: If 'VI Keys' are enabled from the options menu or

+ from the '.lynxrc' file, lowercase h,j,k,l will

+ move left, down, up, and right, respectively.

+ *note: If 'Emacs Keys' are enabled from the options menu or

+ from the '.lynxrc' file, Ctrl-B, Ctrl-N, Ctrl-P,

+ Ctrl-F will move left, down, up, and right, respectively.

+ *note: If the 'Num Lock' on your keyboard is on, Lynx will

+ translate the numbers of your keypad into movement

+ commands. The translation is as follows.

+ 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>

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/option_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/option_help.html
new file mode 100644
index 00000000000..2ef8151ce4d
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/option_help.html

@@ -0,0 +1,262 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Options Screen Help</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<h1>+++ Options Screen Help +++</h1>

+<PRE>

+ The Options Screen allows you to set and

+ modify many of Lynx's features. The following

+ options may be set.

+ Editor - If non-empty it defines the editor to spawn

+ when editing a local file or sending mail.

+ Any valid text editor may be entered here.

+ DISPLAY variable - If non-empty it specifies your <A HREF="xterm_help.html">X terminal</A>

+ display address.

+ Multi-bookmarks - When OFF, the default bookmark file is used

+ for the 'v'iew bookmarks and 'a'dd bookmark

+ link commands. If set to STANDARD, 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 in that menu. If set to

+ ADVANCED, you instead are prompted for the

+ letter of the desired bookmark file, but can

+ enter '=' to invoke the STANDARD selection

+ menu, or RETURN for the default bookmark file.

+ Bookmark file - If non-empty and multi-bookmarks is OFF, it

+ specifies your default '<A HREF="bookmark_help.html">Bookmark file</A>'.

+ If multi-bookmarks is STANDARD or ADVANCED,

+ entering 'B' will invoke a menu in which you

+ can specify the filepaths and descriptions

+ of up to 26 bookmark files. The filepaths

+ must be from your home directory, and begin

+ with dot-slash (./) if subdirectories are

+ included (e.g, ./BM/lynx_bookmarks.html).

+ Lynx will create bookmark files when you

+ first 'a'dd a link, but any subdirectories

+ in the filepath must already exist.

+ FTP sort criteria - This option allows you to specify how files

+ will be sorted within FTP listings. The

+ current options include "By Filename",

+ "By Size", "By Type", and "By Date".

+ Personal Mail - You may set your mail address here so that

+ Address 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 from: field.

+ Searching type - If set to 'case sensitive', user searches

+ invoked by the '/' command will be case

+ sensitive substring searches. The

+ default is 'Case Insensitive' substring

+ searches

+ Preferred Document - The language you prefer if multi-language files

+ Language are available from servers. Use RFC 1766 tags,

+ 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:

+ <kbd>da, en-gb;q=0.8, en;q=0.7</kbd>

+ Preferred Document - The character set you prefer if sets in addition

+ Charset 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:

+ <kbd>iso-8859-5, unicode-1-1;q=0.8</kbd>

+ Display Character - This option allows you to set up the default

+ set character set for your specific terminal.

+ The character set provides a mapping of 8-bit ISO

+ Latin character entities and/or Asian (CJK) or

+ Unicode characters into viewable characters and

+ should be set according to your terminal's

+ character set if you will be viewing such

+ characters with Lynx. You must have the selected

+ character set installed on your terminal.

+ Raw 8-bit or CJK - Toggles whether 8-bit characters are assumed to

+ mode correspond with the selected character set and

+ therefore are processed without translation via

+ the chartrans conversion tables. Should be ON

+ by default when the selected character set is one

+ of the Asian (CJK) sets and the 8-bit characters

+ are Kanji multibytes. Should be OFF for the other

+ 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 included in

+ a reply header from an HTTP server to indicate what

+ it is) but you know by some means that you have the

+ matching display character set selected. Should be

+ OFF when an Asian (CJK) set is selected but the

+ document is ISO-8859-1. The setting also can be

+ toggled via the RAW_TOGGLE command, normally mapped

+ to '@', and at startup via the -raw switch.

+ Show color - 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.

+ ALWAYS and NEVER are not offered in anonymous

+ accounts. If saved to a '.lynxrc' 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 -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.

+ A saved value of NEVER will cause Lynx to assume a

+ monochrome terminal at startup. 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 '.lynxrc' 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 -color switch or COLORTERM

+ variable. This default behavior always is used in

+ anonymous accounts, or if the 'option'_save

+ 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.

+ VI keys - If set to 'ON' then the lowercase h, j, k, and l,

+ keys will be mapped to left-arrow, down-arrow,

+ up-arrow, 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).

+ Emacs keys - 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).

+ Show dot files - If display/creation of hidden (dot)

+ files/directories is enabled, you can turn

+ the feature on or off via this setting.

+ Popups for select - Lynx normally uses a popup window for the

+ fields 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.

+ Show cursor for - Lynx normally hides the cursor by positioning it

+ current link or to the right and if possible the very bottom of

+ option 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.

+ Keypad mode - This option 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.

+ Line edit style - This option allows you to set alternate key

+ bindings for the built-in line editor, if your

+ system administrator has installed alternates.

+ Otherwise, Lynx uses the <A HREF="edit_help.html">Default Binding</A>.

+ List directory - Applies to Directory Editing. Files and

+ style directories can be presented in the following

+ ways:

+ Mixed style

+ Files and directories are listed together in

+ alphabetical order.

+ Directories first

+ Files and directories are separated into two

+ alphabetical lists. Directories are listed

+ first.

+ Files first

+ Files and directories are separated into two

+ alphabetical lists. Files are listed first.

+ User Mode - Beginner

+ Shows two extra lines of help at the bottom

+ of the screen

+ Intermediate (normal mode)

+ The "normal" statusline messages appear.

+ Advanced

+ The URL is shown on the statusline.

+ User Agent - 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 a string such as L_y_n_x/2.7.2 for

+ access to sites which discriminate against Lynx

+ based on checks for the presence of "Lynx" 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 the Options Menu. Changes

+ of the header are not saved in the RC file.

+ NOTE that Netscape Communications Corp. has

+ claimed that false transmissions of "Mozilla" as

+ the User-Agent are a copyright infringement, which

+ will be prosecuted. DO NOT misrepresent Lynx as

+ Mozilla. The Options Menu issues a warning about

+ possible copyright infringement whenever the header

+ is changed to one which does not include "Lynx" or

+ "lynx".

+ Local execution - If set to 'ALWAYS ON', Lynx will locally execute

+ links commands contained inside of any links. This

+ can be HIGHLY DANGEROUS so it is recommended

+ that they remain 'ALWAYS OFF' or 'FOR LOCAL

+ FILES ONLY' unless otherwise set by your system

+ administrator. This option may not be available

+ on most versions of Lynx.

+</PRE>

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/other_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/other_help.html
new file mode 100644
index 00000000000..511ddaac4b7
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/other_help.html

@@ -0,0 +1,171 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Help on Misc. Lynx Commands</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<h1>+++ Other Commands +++</h1>

+<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 transfered 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 goto URL.

+ g - Allows you to enter any <a href="http://www.ncsa.uiuc.edu/demoweb/url-primer.html">URL</a> or filename that

+ you wish to view, and then goto it.

+ G - Allows you to edit the current document's URL and use that

+ as a goto URL.

+ ? or H - Hypertext help to explain how to navigate in

+ Lynx and use its features.

+ i - Shows an index of files or subjects. This is

+ configurable by the System administrator, or

+ within documents that you may be viewing.

+ j - Allows you to enter a "short" name to execute a

+ jump command configured by your system administrator.

+ Press "?" and ENTER to see a 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 setable <A HREF="option_help.html">options</A>.

+ q - Quits Lynx. ('Q' quits without asking)

+ / - Search for a string of characters in the current

+ document case insensitive or case sensitive

+ depending on the options set. (see <A HREF="option_help.html">options)</A>.

+ 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>.

+ x - Force submission of form or link with no-cache.

+ z - Abort a network transfer in progress. If any partial

+ data has been transfered it will be displayed.

+ <backspace> - 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 Lynx

+ 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.

+ Should be on when the document's charset matches the

+ selected character set, and otherwise off so that 8-bit

+ characters will be reverse translated with respect to the

+ ISO-8859-1 conversion table for the character set (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 Lynx display.

+ When off, they will be treated as having ALT="" (i.e.,

+ they'll 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., 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.

+ " - 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.

+ 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 Lynx Trace Log for the current session.

+ CTRL-K - Invokes the Cookie Jar Page.

+ numbers - Lynx 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/gnu/usr.bin/lynx/lynx_help/keystrokes/print_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/print_help.html
new file mode 100644
index 00000000000..153caa74c31
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/print_help.html

@@ -0,0 +1,37 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Lynx Print Help</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<h1>+++ Printing Help +++</h1>

+After entering the 'p' 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. The following print options

+may be available:

+<dl>

+<dt>Print to a local file:

+<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 Lynx.

+<dt>Print to the screen:

+<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.

+<dt>Mail the file to yourself:

+<dd>This option allows you to mail the file, in ASCII form, to any

+ valid e-mail address.

+<dt>Custom print options:

+<dd>Any number of custom print options may be available, as defined

+ by your system administrator.

+</dl>

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/scrolling_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/scrolling_help.html
new file mode 100644
index 00000000000..d19313462bb
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/scrolling_help.html

@@ -0,0 +1,58 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Lynx Scrolling Help</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<H1>+++ SCROLLING HELP +++</H1>

+<PRE>

+ + (or SPACE, - If the bottom of the screen informs you

+ or CTRL-F) that there is 'more' 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).

+ If the 'Num Lock' on your keyboard is on, Lynx will translate

+ the numbers of your keypad into movement commands as follows:

+ 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

+ 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).

+ ) - Moves you forward half a page in the current

+ document (Down-Half).

+ ( - Moves you back half a page in the current

+ document (Up-Half).

+ # - 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>

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/visited_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/visited_help.html
new file mode 100644
index 00000000000..ebb03a709b8
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/visited_help.html

@@ -0,0 +1,31 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>Help on the Visited Links Page</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<h1>+++ Visited Links Page Help +++</h1>

+The Visited Links Page 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 'V'. The list of Visited Links is 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>.

+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#9">Download</A>

+them.

+In contrast to the History Page, the Visited Links Page includes any

+links which were retrieved for 'd'ownloading or were passed to

+helper applications, i.e, not just the links that were rendered and

+displayed by Lynx, itself.

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/keystrokes/xterm_help.html b/gnu/usr.bin/lynx/lynx_help/keystrokes/xterm_help.html
new file mode 100644
index 00000000000..d40ea45016f
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/keystrokes/xterm_help.html

@@ -0,0 +1,32 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>X Terminal Help</TITLE>

+<LINK rev="made" href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<h1>+++ X Terminal or X Server +++</h1>

+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.

+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.

+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.

+<dl>

+<dt>Note:

+<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."

+</dl>

+</BODY>

+</HTML>

diff --git a/gnu/usr.bin/lynx/lynx_help/lynx-dev.html b/gnu/usr.bin/lynx/lynx_help/lynx-dev.html
new file mode 100644
index 00000000000..f062f6748d9
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/lynx-dev.html

@@ -0,0 +1,70 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<html>

+<head>

+<title>Lynx-Dev Discussion List</title>

+<link rev="made" href="mailto:lynx-dev@sig.net">

+</head>

+<body>

+<banner>

+[ <a href="http://www.flora.org/lynx-dev/html/">Lynx-Dev Archives</a> |

+<a href="about_lynx.html">About Lynx</a> ]

+</banner>

+<h1>Lynx-Dev Discussion List</h1>

+Lynx-dev is a majordomo mailing list used by developers and interested

+users as a forum to discuss the further development of the Lynx World

+Wide Web browser. Topic issues include fixing known bugs, porting Lynx

+to various systems, and increasing the usability of Lynx.

+<h2>Subscribing to Lynx-Dev</h2>

+If you are interested in joining this mailing list,

+send email to <a href="mailto:majordomo@sig.net"

+>majordomo@sig.net</a> with only the following request

+in the body of your message: SUBSCRIBE LYNX-DEV address

+where inclusion of your email address is optional if it can be obtained,

+correctly, from the mail headers of your subscription request.

+NOTE: Subject headers are ignored by the majordomo.

+<h2>Unsubscribing from Lynx-Dev</h2>

+To unsubscribe, send an email message to

+<a href="mailto:majordomo@sig.net"

+>majordomo@sig.net</a> with only the following request

+in the body: UNSUBSCRIBE LYNX-DEV address

+where inclusion of your email address is optional if it can be obtained,

+correctly, from the mail headers of your request.

+<h2>Majordomo Commands</h2>

+To receive a brief description of majordomo commands, place

+the following request in a message to <a href="mailto:majordomo@sig.net"

+>majordomo@sig.net</a>: HELP

+<h2>Contacting Lynx-Dev</h2>

+If you have questions, problems, or comments about using Lynx or

+installing it on your system, send email to

+<a href="mailto:lynx-dev@sig.net"

+>lynx-dev@sig.net</a> (after you've subscribed).

+If you have problems with majordomo not responding to your requests,

+send email to the list owner: <a

+href="mailto:majordomo-owner@sig.net"

+>majordomo-owner@sig.net</a>. Please,

+DO NOT send them to lynx-dev@sig.net as they

+will be distributed to everyone on the list and will clutter

+up their mailboxes.

+<h2>Lynx-Dev Archives</h2>

+Archives of messages posted to lynx-dev are now in html format so that

+you can view them using Lynx.

+Go to the <a href="http://www.flora.org/lynx-dev/html/"

+>Lynx-Dev Archives</a>.

+</body>

+</html>

diff --git a/gnu/usr.bin/lynx/lynx_help/lynx_help_main.html b/gnu/usr.bin/lynx/lynx_help/lynx_help_main.html
new file mode 100644
index 00000000000..0871f1d9f24
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/lynx_help_main.html

@@ -0,0 +1,84 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<html>

+<head>

+<link rev="made" href="mailto:lynx-dev@sig.net">

+<title>Help! - Press the Left arrow key to exit help</title>

+</head>

+<body>

+<H1>Lynx Help Menu</h1>

+<ul plain>

+<lh>Choose a subject:</lh>

+<li><a href="Lynx_users_guide.html">Lynx Users Guide</a>

+<ul plain>

+<li><a href="keystrokes/keystroke_help.html">Key-stroke Commands</a>

+| <a href="keystrokes/edit_help.html">Line Editor</a>

+<li><a href="lynx_url_support.html">Supported URLs</a>

+| <a href="http://www.w3.org/Addressing/Addressing.html"

+>Help on URLs</a>

+<li><a href="http://leb.net/blinux/blynx/"

+>Speech-Friendly Lynx Help Files</a>

+<li><a href="http://lynx.browser.org/">Lynx Information</a>

+| <a href="http://www.crl.com/~subir/lynx.html"

+>Lynx links</a>

+| <a href="http://www.slcc.edu/lynx/faq.html"

+>Lynx FAQ</a>

+<li><a href="about_lynx.html">About Lynx</a>

+| <a href="lynx-dev.html">About Lynx-Dev</a>

+| <a href="http://www.access.digex.net/~asgilman/lynx/FAQ/"

+>Al's Picks (FAQ)</a>

+</ul>

+<li><a

+href="http://www.w3.org/MarkUp/html-spec/html-spec_toc.html"

+>HTML 2.0</a>

+| <a href="http://www.w3.org/MarkUp/html3/Contents.html"

+>HTML 3.0</a>

+| <a href="http://www.alis.com:8085/ietf/html/"

+>HTML i18n</a>

+| <a href="http://www.w3.org/MarkUp/"

+>HTML 3.2</a>

+| <a href="http://www.w3.org/TR/PR-html40/"

+>HTML 4.0</a>

+<ul plain>

+<li><a href="http://www.stonehand.com/doc/"

+>Spyglass/Stonehand Technical Reference</a>

+<ul plain>

+<li><a

+href="http://www.stonehand.com/doc/comments.html"

+>Keep Your Comments Legal</a>

+</ul>

+<li><a

+href="http://ugweb.cs.ualberta.ca/~gerald/validate/"

+>A Kinder, Gentler HTML Validator</a>

+<li><a href="http://www.webtechs.com/html-val-svc/"

+>WebTechs HTML Validation Service</a>

+<li><a href="http://www.ncsa.uiuc.edu/General/Internet/WWW/HTMLPrimer.html"

+>HTML Primer</a>

+| <a href="http://kuhttp.cc.ukans.edu/lynx_help/HTML_quick.html"

+>HTML Quick Reference Guide</a>

+</ul>

+<li><a

+href="http://ds.internic.net/rfc/rfc1945.txt"

+>HTTP 1.0</a>

+| <a href="http://www.w3.org/Protocols/"

+>HTTP 1.1</a>

+<li><a

+href="http://www.w3.org/TheProject.html"

+>The World Wide Web Consortium (W3C)</a>

+<li><a href="http://www.altavista.digital.com/">Alta Vista</a>

+| <a href="http://www.yahoo.com/">Yahoo!</a>

+| <a href="http://guaraldi.cs.colostate.edu:2000/">Savvy Search</a>

+| <a href="http://www.webcrawler.com/">WebCrawler</a>

+<li><a href="http://guide.Infoseek.com/">Infoseek Guide</a>

+| <a href="http://www.lycos.com/">Lycos</a>

+| <a href="http://www.excite.com/">Excite</a>

+| <a href="http://www.metacrawler.com/">MetaCrawler</a>

+</ul>

+</body>

+</html>

diff --git a/gnu/usr.bin/lynx/lynx_help/lynx_url_support.html b/gnu/usr.bin/lynx/lynx_help/lynx_url_support.html
new file mode 100644
index 00000000000..27f069ab41f
--- /dev/null
+++ b/gnu/usr.bin/lynx/lynx_help/lynx_url_support.html

@@ -0,0 +1,586 @@

+<!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN">

+<HTML>

+<HEAD>

+<TITLE>URL Schemes Supported in Lynx</TITLE>

+<LINK rev=made href="mailto:lynx-dev@sig.net">

+</HEAD>

+<BODY>

+<BANNER>

+[<a href="#http">http, https</a> |

+<a href="#telnet">telnet, tn3270, rlogin</a> |

+<a href="#gopher">gopher</a> |

+<a href="#file">file</a> |

+<a href="#ftp">ftp</a> |

+<a href="#wais">wais</a> |

+<a href="#news">news, nntp, snews</a> |

+<a href="#newspost">newspost, newsreply, snewspost, snewsreply</a> |

+<a href="#mailto">mailto</a> |

+<a href="#finger">finger</a> |

+<a href="#cso">cso</a> |

+<a href="#exec">lynxexec, lynxprog</a> |

+<a href="#cgi">lynxcgi</a>|

+<a href="#internal">internal</a>]

+</BANNER>

+<H1>URL Schemes Supported in Lynx</H1>

+Lynx handles a number of URL types, that are enumerated below. For

+more details about URLs (Uniform Resource Locators) see RFC1738:

+<ul plain>

+<li><a href="http://www.w3.org/Addressing/rfc1738.txt"

+>http://www.w3.org/Addressing/rfc1738.txt</a>

+<li><a href="ftp://ds.internic.net/rfc/rfc1738.txt"

+>ftp://ds.internic.net/rfc/rfc1738.txt</a>

+</ul>

+Lynx 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 RFC1808:

+<ul plain>

+<li><a href="http://www.w3.org/Addressing/rfc1808.txt"

+>http://www.w3.org/Addressing/rfc1808.txt</a>

+<li><a href="ftp://ds.internic.net/rfc/rfc1808.txt"

+>ftp://ds.internic.net/rfc/rfc1808.txt</a>

+</ul>

+and in subsequent drafts of the IETF:

+<ul plain>

+<li><a href="http://www.ics.uci.edu/pub/ietf/uri/"

+>Uniform Resource Identifiers (URI) Working Group</a>

+</ul>

+When entering a URL on the command line to be used as the

+startfile, or at the prompt for a 'g'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 Lynx configuration file. See the explanation of those definitions

+and their use in your lynx.cfg. For example, wfbr will

+be treated as http://www.wfbr.edu/, and wfbr/dir/lynx

+will be treated as http://www.wfbr.edu/dir/lynx, but

+gopher.wfbr.edu/11/_fileserv/_lynx will be treated as

+gopher://gopher.wfbr.edu/11/_fileserv/_lynx. For files or

+directories on the local host, a tilde (~) is expanded to

+the path of the account's login directory, e.g., ~/foo will

+be expanded to file://localhost/your/login/directory/foo.

+The tilde expansion is done homologously on Unix and VMS. On VMS,

+Lynx also will expand any file or directory spec recognizable to

+DCL into a valid URL, e.g., [] will be expanded to

+file://localhost/current/default/directory. These expansions

+are SOLELY for startfile or 'g'oto entries!

+Any partial or relative URLs within HTML documents are resolved

+according to the rules specified in RFC1808 and subsequent IETF drafts.

+<HR WIDTH="100%">

+<H2><a name="http">The http and https URLs:</a></H2>

+Lynx handles http URLs exactly as specified in RFC1738. The format

+is:

+<tab indent="12">http://host:port/path?searchpart#fragment

+where :port is optional and defaults to :80,

+/path if present is a slash-separated series of symbolic

+elements, and ?searchpart if present is the query for an ISINDEX

+search or the content of a FORM with METHOD="GET". The #fragment

+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. Lynx 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.

+The https URL has the same format, but the default port is :443.

+Patches for support of https URLs and the CONNECT procedure are available

+for qualified recipients via <a

+href="http://www.crl.com/~subir/lynx.html">Lynx links</a>. US Export laws

+and associated red tape pose severe impediments to inclusion of this support

+in the general distributions of freeware WWW clients such as Lynx. Sorry.

+<HR WIDTH="100%">

+<H2><a name="telnet"

+>The telnet, tn3270, and rlogin URLs:</a></H2>

+A telnet URL generally results in Lynx spawning a telnet

+session. Lynx implements the complete telnet URL scheme, i.e.:

+<tab indent="12">telnet://user:password@host:port

+The user and/or :password fields may be omitted, and

+the @ should be omitted if neither is present. The port defaults

+to :23 when omitted in the URL.

+A tn3270 or rlogin 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.

+It is unwise to include the :password 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.

+<HR WIDTH="100%">

+<H2><a name="gopher">The gopher URL:</a></H2>

+The gopher URL takes the form:

+<tab indent="12">gopher://host:port/gopher-path

+where :port is optional and defaults to :70, and the

+/gopher-path 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">gophertype</A>

+indicating the file or service type (e.g., 0 or I for

+plain text or an image, respectively, 7 for a search, or 1

+for a directory), followed by a platform-specific selector. Any

+reserved characters in the selector should be hex escaped (%hh),

+including slashes, although hex escaping of slashes is not required by Lynx

+in gopher URLs.

+Lynx does not overtly support the gopher+ protocol, and does not

+represent itself as gopher+ capable when communicating with gopher

+servers. Lynx 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 ? rather than hex-escaped tab

+(%09) as the separator for the searchpart in the

+selector, e.g.:

+gopher://gopher.wfbr.edu/77/_shell/search.shell%20/_shell/walker?lynx*

+Lynx will handle the %09 if you use that instead of ?,

+but other WWW clients may mishandle it.

+For the gophertype which signifies HTML (h), if the

+selector begins with GET%20/ Lynx will convert the gopher

+URL to an http URL, e.g.:

+<tab indent="12">gopher://www.wfbr.edu:80/hGET%20/

+will become:

+<tab indent="12">http://www.wfbr.edu/

+The port field will be retained if it is not :80, and will default

+to :70 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.

+<HR WIDTH="100%">

+<H2><a name="file">The file URL:</a></H2>

+The file URL is used to retrieve files or generate a directory listing

+on the local host. The host field can be localhost or a domain

+name for the local host:

+<tab indent="12">file://localhost/path

+If you do not use localhost or a domain name for the local host,

+Lynx will substitute ftp:// for file:// and treat it

+as an ftp URL.

+The /path is treated as originating at the root, unless

+you include a tilde (~), e.g.:

+<tab indent="12">file://localhost/~/foo

+<tab indent="60">will be converted to:

+<tab indent="12">file://localhost/your/login/directory/foo

+The latter feature is a Lynxism, is done homologously on Unix and VMS,

+and should be used ONLY in local documents intended for Lynx.

+On VMS, the first element of the path, if not a tilde, is assumed to

+be a device, e.g.:

+<tab indent="12"

+>file://localhost/www_root/directory/filename.suffix

+should be used for: www_root:[directory]filename.suffix

+If you are unsure how to specify a file URL in local documents on

+VMS, invoke Lynx with the desired file or directory as the

+startfile using any spec acceptable to DCL, and then

+use the showinfo command (=) to see the file

+URL which Lynx created for it.

+<HR WIDTH="100%">

+<H2><a name="ftp">The ftp URL:</a></H2>

+The ftp URL has the general format:

+<tab indent="12"

+>ftp://username:password@host:port/path;type=[D,I, or A]

+The default port is :21 and the default username

+is anonymous. If username is included but not

+:password, Lynx will prompt you for the password. This is

+recommended, as otherwise the URL will have it completely unencrypted.

+Do not include the @ if neither username nor

+:password is included. For anonymous ftp, Lynx uses your

+personal_mail_address (user@host) as the :password

+if it has been defined via the 'o'ptions menu. Otherwise,

+Lynx uses the dummy password WWWUser.

+The ;type= parameter can be used with value D,

+I, or A to force handling of the URL as, respectively,

+a directory listing, binary file, or ASCII file. The Lynx 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.

+The /path is treated according to RFC1738 for VMS

+and VM/CMS ftp servers. The lead slash (/) is treated purely

+as a separator, not as a designator for the root, and the path

+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 (%2f), e.g.:

+<tab indent="12">ftp://user@myhost/%2fsys$common/syshlp

+can be used for a listing of sys$common:[syshlp]

+Also, on VM/CMS ftp servers, if the path string begins

+with vmsysu%3a it receives special handling as an SFS

+path, e.g.:

+<tab indent="12">ftp://ubvm.cc.buffalo.edu/vmsysu%3alistserv.webshare

+For Unix and Unix-emulation ftp servers, RFC1738 is not respected

+and the lead slash is treated as the root, i.e., the /path 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 path

+string treated as a file or path under the login directory, include a

+tilde (~) as for <a href="#file">file</a> URLs, e.g.:

+<tab indent="12">ftp://user@myhost/~

+<HR WIDTH="100%">

+<H2><a name="wais">The wais URL:</a></H2>

+The wais URL is used to retrieve resources using the Wide Area Information

+System protocol. The format is:

+<tab indent="12">wais://host:port/database

+<tab indent="12">wais://host:port/database?wais_query

+<tab indent="12">wais://host:port/database/wais_type/wais_path

+where :port defaults to :210

+Direct wais support is built into Lynx for VMS, and can be compiled

+into Lynx on Unix.

+If only a database is indicated in the URL, Lynx returns

+an ISINDEX cover page for searching that database, and will

+submit your search with the wais_query appended. Lynx will

+convert the server's reply into a hit list with URLs that include the

+wais_type and wais_path for retrieving items from

+the hit list.

+<HR WIDTH="100%">

+<H2><a name="news"

+>The news, nntp, and snews URLs:</a></H2>

+The news and nntp URLs are handled by Lynx as specified in RFC1738, but

+for compatibility with other clients, Lynx allows inclusion of host and

+port fields in news URLs, which properly should be used only in

+nntp and snews URLs. If not included in news URLs, Lynx will use the nntp

+server pointed to by the NNTPSERVER environment variable or configuration

+symbol (see lynx.cfg), with default port :119. A host field must

+be included in nntp URLs, and the port field is optional with the same

+default. Patches for support of snews URLs are available to qualified

+recipients via <a href="http://www.crl.com/~subir/lynx.html">Lynx links</a>

+but cannot be included in the general distribution (sorry, see <a

+href="#http">http and https</a>).

+The formats are:

+<tab indent="12">news:newsgroup <tab

+id="ng">(retrieves list of messages in newsgroup)

+<tab indent="12">news:messageID <tab

+to="ng">(retrieves the message)

+<tab indent="12">news:* <tab

+to="ng">(retrieves list of all available newsgroups)

+<tab indent="12">nntp://host:port/newsgroup

+<tab indent="12">nntp://host:port/messageID

+<tab indent="12">nntp://host:port/*

+(snews same as nntp, but the default port is :563)

+The messageID is the message's unique identifier, consisting

+of an identification string and the host of origin for the message

+(ident_string@origin_host).

+Lynx also supports wildcarding via an asterisk for listings of news

+hierarchies or sub-hierarchies, e.g.:

+<tab indent="12">news:comp.infosystems.*

+<tab indent="12">nntp://host:port/comp.infosystems.*

+(snews same as nntp, but the default port is :563)

+This is not in RFC1738 and may not be supported by all other clients.

+Lynx allows you both to reply to the author of a news message

+via email, and, if news posting has been enabled, to send a followup

+message to the newsgroup (see <a href="#newspost">newspost, newsreply,

+snewspost, snewsreply</a>).

+Lynx converts any strings in news messages which appear to be a URL

+with a supported scheme into a link for accessing that URL.

+Lynx also supports the newsgroup and message number URL scheme:

+<tab indent="12">news:newsgroup/startNo-endNo <tab

+id="ngno">(lists message range in newsgroup)

+<tab indent="12">news:newsgroup/messageNo <tab

+to="ngno">(retrieves the message by number)

+<tab indent="12">nntp://host:port/newsgroup/startNo-endNo

+<tab indent="12">nntp://host:port/newsgroup/messageNo

+(snews same as nntp, but the default port is :563)

+Use of this scheme is not recommended, because the message numbers

+are specific to each nntp server, unlike the unique identifiers for

+news messages.

+<HR WIDTH="100%">

+<H2><a name="newspost"

+>The newspost, newsreply, snewspost, and

+snewsreply URLs:</a></H2>

+When Lynx receives group listings or articles via news,

+nntp or snews URLs, it also checks whether the

+nntp server supports posting from the Lynx 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 Lynx, do not include any schemes

+for posting to news groups. Lynx has long supported newspost and

+newreply URL schemes for posting new messages or sending followups,

+respectively, to standard nntp servers, with default port :119.

+Lynx now also supports homologous snewspost and snewsreply URLs for use

+with SSL capable nntp servers, but the latter requires patches for built

+in SSL support, or use of a daemon which handles the secure communications

+on behalf of Lynx.

+The formats are:

+<tab indent="12">newspost://host:port/newsgroup(s)  <tab

+id="ngp">(post a new message)

+<tab indent="12">newsreply://host:port/newsgroup(s) <tab

+to="ngp">(post a followup message)

+(snewspost and snewsreply have the same formats, but the default port is

+:563)

+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 newgroup names

+is not supported for these URLs. For newsreply and snewsreply URLs, if

+an external editor has been defined via the Options Menu, the

+user is offered an option to include the currently displayed document,

+which presumeably is a news article with a followup 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.

+These URLs can be used as command line startfiles (in which case, Lynx

+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">mailto</a> URLs, with the qualification that they presently

+are supported only by Lynx.

+<HR WIDTH="100%">

+<H2><a name="mailto">The mailto URL:</a></H2>

+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:

+<tab indent="12">mailto:user@host

+The description of the mailto URL in RFC1738 has been interpreted by

+some as allowing only a single recipient, but Lynx 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, Lynx also accepts

+a semi-colon-separated list.

+For compatibility with Netscape, Lynx parses any

+?subject=The%20Subject appended to the URL, trims the URL

+at the ?, 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.:

+<tab indent="12"><LINK <tab id="rev">REV="made"

+<tab to="rev">HREF="mailto:me@myhost,her@herhost" TITLE="The Subject">

+<tab indent="12"><A

+HREF="mailto:user@host" TITLE="The Subject">...</A>

+<tab indent="12"><FORM <tab id="met">METHOD="post"

+ENCTYPE="text/plain"

+<tab to="met">ACTION="mailto:WebMaster@host" TITLE="The Subject">

+<tab indent="14">...

+<tab indent="12"></FORM>

+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 Lynx recognizes that as a synonym for TITLE.

+Lynx also will process any to=address(es),

+cc=address(es), keywords=word_list and/or

+body=message fields in ?searchpart tack-ons to mailto

+URLs. The to and/or cc values can be single addresses,

+or comma- or semi-colon-separated lists of addresses. All addresses,

+and any body values, will be offered for approval by the user

+before proceeding with a mailing. Any other name=value pairs in the

+?searchpart will be ignored. Also, if the mailto URL is the

+ACTION for a FORM, any body in a ?searchpart tack-on

+will be ignored, because the body of the mailing must be constructed

+solely from the the FORM's content. Lynx expects multiple name=value

+pairs in a ?searchpart 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 (&amp;) 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., mail:, or

+smtp:), rather than breaking mailto: implementations.

+If ENCTYPE="text/plain" is specified for a FORM with a mailto

+ACTION, Lynx will not hex escape the name=value pairs of the FORM's content,

+and will use physical newlines instead of '&' or ';'

+to separate the pairs, so that the content will be readable directly.

+Otherwise, Lynx will mail the content with the default:

+<tab indent="12"

+>ENCTYPE="application/x-www-form-urlencoded" <tab id="enc">('<em

+>&' separates pairs)

+or:

+<tab indent="12"

+>ENCTYPE="application/sgml-form-urlencoded" <tab to="enc">('<em

+>;' separates pairs)

+if the latter was indicated.

+Note that when mailing FORM content Lynx 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 text/plain,

+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.

+If the mailto URL is not the ACTION for a FORM, and if an external

+editor has been defined via the Options Menu, 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.

+<HR WIDTH="100%">

+<H2><a name="finger">The finger URL:</a></H2>

+Lynx 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 Lynx

+therefore include every possibility not inconsistent with RFC1738,

+including:

+<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>

+Activating a finger URL will send a request to the finger server via

+port 79 on the host specified. You can include :79 in the URL,

+but no other value is allowed. The /w or /%2fw is used

+to request a full report for finger servers which support it, and is not

+case sensitive (i.e., can be /W or /%2fW). 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.

+An alternative way to access finger servers is via gopher URLs with

+port 79 and the plain text (0) gophertype specified:

+gopher://host:79/0

+Lynx will handle such URLs equivalently to overt finger URLs, including

+creation of links for any strings which appear to be supported URLs.

+<HR WIDTH="100%">

+<H2><a name="cso">The cso URL:</a></H2>

+The cso URL is intended to provide a gateway to CSO/PH (QI) servers.

+The requests are made on port 105 by default (:105), with the

+following overt cso URL format:

+<tab indent="12">cso://host

+You also can use a gopher URL format with port 105 and the CSO

+(2) gophertype specified:

+<tab indent="12">gopher://host:105/2

+Lynx 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.

+<HR WIDTH="100%">

+<H2><a name="chargen">The chargen URL:</a></H2>

+The chargen URL is intended to provide a gateway to the chargen service.

+The requests are made on port 19 (:19). You can omit the port,

+and no other value is allowed. The format is:

+<tab indent="12">chargen://host

+Lynx will accept approximately 55 lines of characters in the stream

+returned by the server, then close the connection and display the lines

+as PRE formatted text. Note that if port 19 is used for a URL with a

+scheme other than chargen, the URL will be rejected by Lynx.

+<HR WIDTH="100%">

+<H2><a name="exec">The lynxexec and lynxprog URLs:</a></H2>

+If execution of spawned commands has been enabled in your Lynx 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

+Lynx on Unix, or for DCL on VMS, e.g.:

+<tab indent="12">lynxexec:dir/date/size foo:[blah] <tab

+id="listing">(VMS)

+<tab indent="12">lynxexec:ls -l /foo/blah <tab

+to="listing">(Unix)

+<tab indent="12">lynxprog:news

+(Note, however, that restrictions on acceptable commands or utilities

+may be imposed by the system administrator.)

+You optionally can include //localhost/ 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 RETURN before Lynx 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.

+These are Lynxisms and should be used only in local documents intended

+solely for Lynx.

+<HR WIDTH="100%">

+<H2><a name="cgi">The lynxcgi URL:</a></H2>

+The lynxcgi URL is implemented only on Unix, can be used as the

+ACTION for a FORM, and if enabled in your Lynx image has the format:

+<tab indent="12">ly<tab id="lh">

+nxcgi://localhost/path_to_CGI_script

+<tab to="lh">where //localhost/ is optional and always implied.

+The output of the script should be text/html and is rendered and displayed

+by Lynx. (Note that restrictions on acceptable paths can be imposed

+by the system administrator.)

+This is a Lynxism and should be used only in local documents intended

+solely for Lynx, or for limited local testing of CGI scripts without an

+http server.

+On VMS, you are advised to use the threaded OSU http server, available

+from <a href="ftp://osu.edu"

+>ftp://osu.edu</a> as freeware, if your site does not already have an http

+server. It can be installed as a purely local script server, and is far

+more efficient and comprehensive than any code which might be incorporated

+within Lynx.

+<HR WIDTH="100%">

+<H2><a name="internal">The LYNXfoo internal URLs:</a></H2>

+Lynx uses a variety of internal URL schemes as structured stream

+objects for communication among its display modules. If you discover

+what they are, and are tempted to use them externally in documents,

+find the self-restraint to resist that temptation!!!

+For example, tempting though it might be, do not use these:

+<tab indent="12"

+>Return to your <A HREF="LYNXHIST:0">Startfile</A>

+<tab indent="12"

+>Review your <A HREF="LYNXKEYMAP:">Keymap</A>

+(Yes, they'll work. No, they won't do any harm. But...)

+If you must try one, the second is OK from the command line:

+<tab indent="12">lynx LYNXKEYMAP:

+But within Lynx, use the 'K' keystroke command.

+</BODY>

+</HTML>