From e087f6d44e87f489fcb3056e86319ebba4218156 Mon Sep 17 00:00:00 2001 From: "Thomas E. Dickey" Date: Mon, 2 Sep 1996 19:39:24 -0400 Subject: snapshot of project "lynx", label v2_6 --- lynx_help/Lynx_users_guide.html | 1814 ++++++++++++++++++++ lynx_help/keystroke_commands/bookmark_help.html | 20 + lynx_help/keystroke_commands/dired_help.html | 51 + lynx_help/keystroke_commands/edit_help.html | 38 + .../keystroke_commands/gopher_types_help.html | 59 + lynx_help/keystroke_commands/history_help.html | 28 + lynx_help/keystroke_commands/keystroke_help.html | 79 + lynx_help/keystroke_commands/movement_help.html | 49 + lynx_help/keystroke_commands/option_help.html | 164 ++ lynx_help/keystroke_commands/other_help.html | 137 ++ lynx_help/keystroke_commands/print_help.html | 37 + lynx_help/keystroke_commands/scrolling_help.html | 58 + lynx_help/keystroke_commands/xterm_help.html | 32 + lynx_help/lynx_help_main.html | 87 + lynx_help/lynx_url_support.html | 493 ++++++ 15 files changed, 3146 insertions(+) create mode 100644 lynx_help/Lynx_users_guide.html create mode 100644 lynx_help/keystroke_commands/bookmark_help.html create mode 100644 lynx_help/keystroke_commands/dired_help.html create mode 100644 lynx_help/keystroke_commands/edit_help.html create mode 100644 lynx_help/keystroke_commands/gopher_types_help.html create mode 100644 lynx_help/keystroke_commands/history_help.html create mode 100644 lynx_help/keystroke_commands/keystroke_help.html create mode 100644 lynx_help/keystroke_commands/movement_help.html create mode 100644 lynx_help/keystroke_commands/option_help.html create mode 100644 lynx_help/keystroke_commands/other_help.html create mode 100644 lynx_help/keystroke_commands/print_help.html create mode 100644 lynx_help/keystroke_commands/scrolling_help.html create mode 100644 lynx_help/keystroke_commands/xterm_help.html create mode 100644 lynx_help/lynx_help_main.html create mode 100644 lynx_help/lynx_url_support.html (limited to 'lynx_help') diff --git a/lynx_help/Lynx_users_guide.html b/lynx_help/Lynx_users_guide.html new file mode 100644 index 00000000..af4b7efc --- /dev/null +++ b/lynx_help/Lynx_users_guide.html @@ -0,0 +1,1814 @@ + + + +Lynx Users Guide v2.6 + + + + +

Lynx Users Guide Version 2.6

+ +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 +URL Schemes Supported by Lynx). +Current versions of Lynx run on Unix and VMS. + +

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

Table of Contents

+ + + +

Lynx online help

+ +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 Navigating hypertext documents with Lynx 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). +[ToC] + +

Viewing local files with Lynx

+ +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: + +
+
UNIX +
lynx filename +
lynx /home/my-dir/filename +
lynx ~/filename +
VMS +
lynx filename +
lynx dua5:[my-directory]filename +
lynx /dua5/my-directory/filename +
lynx ~/filename +
lynx sys$login:filename +
lynx /sys$login/filename +
+ +

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

Leaving Lynx

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

Starting Lynx with a Remote File

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

PROTOCOL :// HOST / PATH + +

where + +

+
PROTOCOL +
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. + +
HOST +
is the Internet address of the computer system on which the + server is running, and + +
PATH +
is a scheme-specific field which for some schemes may + correspond to a directory path and/or filename. +
+ +Here are some sample URLs. + +
+
HTTP (HyperText Transfer Protocol) +
http://www.nyu.edu/pages/wsn/subir/lynx.html + +
Gopher +
gopher://gopher.micro.umn.edu/11/ + +
FTP (File Transfer Protocol) +
ftp://ftp2.cc.ukans.edu/pub/lynx/README + +
WAIS (Wide Area Information Service protocol) +
wais://cnidr.org/directory-of-servers + +
A URL may be specified to Lynx on the command line, as in: +
lynx http://kufacts.cc.ukans.edu/cwis/kufacts_start.html +
+ +Lynx also will attempt to create a complete URL if you include adequate +portions of it in the startfile argument. For example:
+wfbr +will be expanded to:
+http://www.wfbr.edu/ +and:
+ftp.more.net/pub +will be expanded to:
+ftp://ftp.more.net/pub
+See URL Schemes Supported by Lynx for +more detailed information. [ToC] + +

Starting Lynx with the WWW_HOME environment variable.

+ +You may also specify a starting file for Lynx using the WWW_HOME +environment variable, +
+
UNIX +
+
+
ksh +
export WWW_HOME=http://www.w3.org/ +
csh +
setenv WWW_HOME http://www.w3.org/ +
+
VMS +
define "WWW_HOME" "http://www.w3.org/" +
+ +Note that on VMS the double-quoting must be included to preserve +casing. + +

Navigating hypertext documents with Lynx

+ +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. +
+                                       +-------+-------+-------+
+                                       | TOP   |  /|\  | Page  |
+              arrow keys               | of    |   |   | UP    |
+                                       | text 7|   |  8|      9|
+              +---------+              +-------+-------+-------+
+              | SELECT  |              |       |       |       |
+              | prev /|\|              | <---  |       |  ---> |
+              | link  | |              |      4|      5|      6|
+    +---------+---------+---------+    +-------+-------+-------+
+    |    BACK | SELECT  | DISPLAY |    | END   |   |   | Page  |
+    |<-- prev | next  | | sel. -->|    | of    |   |   | DOWN  |
+    |    doc. | link \|/| link    |    | text 1|  \|/ 2|      3|
+    +---------+---------+---------+    +-------+-------+-------+
+
+ +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 Scrolling and Other useful commands. Some +additional commands depend on the fact that Lynx keeps a list of each +file you visit called the History Page. The Backspace +or Delete key will show you the History Page of links +preceding your access to the current document. Any of the previous +documents shown in the list may be revisited by selecting them from the +history screen. The 'm' key command 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 activated 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 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. [ToC] + +

Printing, Mailing, and Saving rendered files to disk.

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

Viewing the HTML document source and editing documents

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

+
Command +
lynx file://localhost/FULL/PATH/FILENAME +
lynx path/filename.html +
+ +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. [ToC] + +

Downloading and Saving source files.

+ +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 display the source +('\') and then using Printing 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. +[ToC] + +

Reloading files and refreshing the display

+ +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 Lynx and HTML Forms). [ToC] + +

Lynx searching commands

+ +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 Options Menu. 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 Supported URLs). + +

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' command to repeated 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 HTML Forms 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:
+<ISINDEX PROMPT="Enter WAIS query:"
+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. [ToC] + +

Lynx Options Menu

+ +The Lynx Options Menu may be accessed by pressing the 'o' +key. The current Options Menu contains the following configurable +options. + +
+                      Options Menu
+
+     E)ditor                      : emacs
+     D)ISPLAY variable            : aixtest.cc.ukans.edu:0.0
+     B)ookmark file               : home_page
+     F)TP sort criteria           : By Filename
+     P)ersonal mail address       : montulli@ukanaix.cc.ukans.edu
+     S)earching type              : CASE INSENSITIVE
+     display (C)haracter set      : ISO Latin 1
+     raw 8-bit or CJK m(O)de      : ON
+     preferred document lan(G)uage: en
+     preferred document c(H)arset : NONE
+     V)I keys                     : OFF
+     e(M)acs keys                 : OFF
+     K)eypad mode                 : Numbers act as arrows
+     l(I)st directory style	  : Mixed style
+     sho(W) dot files             : OFF
+     U)ser mode                   : Advanced
+     user (A)gent                 : [User-Agent header]
+     L)ocal execution links       : Always off
+
+ +An option can be changed by entering the capital letter of the option +you want to change (i.e. 'E' for Editor). For fields where text +must be entered, simply enter the text by typing on the keyboard. The +Line Editor 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 from a list of choices, press any key +to toggle the choices and 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: + +

+
Editor +
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. + +
DISPLAY variable +
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. + +
Bookmark file +
This is the filename and location of your personal bookmark + file. The bookmark file allows frequently traveled links to + be stored in a personal easy to access file. Using the + 'a' command (see below) you may save any link into + your bookmark file. If the path specified does not begin with + a slash then the path will reference your home directory. + +
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 address +
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 all HTTP get requests if inclusion of that HTTP header + has not been disabled via the NO_FROM_HEADER definition in + lynx.cfg or via the -nofrom command line option. + +
Searching type +
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. + +
Display Character set +
This option allows you to set up the default character set for + your specific terminal. The character set provides a mapping + of 8-bit ISO Latin character entities and/or Asian (CJK) + characters into viewable characters and should be set in + relation 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 Mode +
Whether 8-bit characters are are assumed to correspond with + the selected character set and therefore are processed without + translation via the ISO Latin 1 conversion tables. Should be + ON by default when the selected character set is ISO Latin 1, + or 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 there's a match, e.g., the document's + charset is ISO-8859-2 and ISO Latin 2 has been selected. Should + be OFF when an Asian (CJK) set is selected but the document is + ISO-8850-1. The setting also can be toggled via the RAW_TOGGLE + command, normally mapped to '@', and at startup via the + -raw switch. + +
Preferred Document Language +
The language you prefer if multi-language files are available + from servers. Use MIME abbreviations, e.g., en for English, + fr for French, etc. Can be a comma-separated list in descending + order of preferences. + +
Preferred Document Charset +
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 in descending order of preferences. + +
VI keys +
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). + +
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). + +
Keypad as arrows or numbered links +
This option gives the choice between navigating with the arrow + keys or having every link numbered so that the links may be + selected by numbers as well as using the arrow keys. + +
List directory style +
Applies to Directory Editing. Files and 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. +
+ +
Show dot files +
If display/creation of hidden (dot) files/directories is + enabled, you can turn the feature on or off via this setting. + +
User Mode +
There are three possible choices: Novice, Intermediate, and + Advanced. +
+
Novice +
In Novice mode two lines of help are displayed at the + bottom of the screen. +
Intermediate +
Intermediate mode turns off the help lines. +
Advanced +
Advanced mode displays the URL of the currently selected + link at the bottom of the screen. +
+ +
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.6 + 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 scripts or links +
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. +
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: +
+
Always off +
Local execution scripts will never be executed +
For Local files only +
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 +
Always on +
All local execution scripts will be executed +
+ +
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. + [ToC] +
+ +

Comments and mailto: links

+ +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 +mailto: 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' then the message will be sent, if you +press 'n' the message will be deleted. [ToC] + +

USENET News posting

+ +While reading news articles with Lynx you should see a link that says +Reply to: user@host and a link that says +Followup to: newsgroup(s) + +
+
Reply to user@host +
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. + +
Followup to newsgroup(s) +
Selecting this link will allow you to post back to the + newsgroup that you are currently reading and any newsgroups + that the message may be cross-posted to. You will be given + the option of including the original message in your reply. + Once you have typed in your message the inews program + will be called to post your message to your news host. + [ToC] +
+ +

Lynx bookmarks

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

+
+
Save D)ocument or L)ink to bookmark + file or C)ancel? (d,l,c): +
+ +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. + +

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

Jump Command

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

Directory Editing

+ +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 + +
+
C)reate +
Type 'c' to create a new file. New file will be empty. + +
D)ownload +
Type 'd' to download selection using one of the options defined + by your system administrator. + +
E)dit +
Type 'e' to spawn the editor defined in Options Menu + and load a selected file for editing. + +
F)ull Menu +
Type 'f' to show full menu of options available for selection. + Menu may vary according to type of file selected and compression + facilities available. + + +
M)odify +
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. + +
R)emove +
Type 'r' to remove the selected file or directory. + +
T)ag +
Type 't' to tag highlighted file. Further operations will be + performed on tagged files instead of highlighted ones. + +
U)pload +
Type 'u' to upload a file to the present directory. Upload + methods are defined by your system administrator. +
+[ToC] + +

Scrolling and Other useful commands

+ +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. + +
+
^A +
Control-A jumps you to the beginning of the current + document. It is a synonym for the Keypad Home key, and + can be used 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. +
^E +
Control-E jumps you to the end of the current document. + It is a synonym for the Keypad End key, and can be used + 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. +
^B +
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 Lynx Options Menu). +
^F +
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. +
^N +
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. +
^P +
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. +
) +
The ) command jumps you forward half a page in the + current document. +
( +
The ( command jumps you back half a page in the + current document. +
# +
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. +
! +
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. +
g +
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 be accessed at + the prompt by pressing the up-arrow or + down-arrow keys. +
= +
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. +
^T +
Control-T toggles 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. +
* +
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. +
@ +
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. +
[ +
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. +
] +
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. +
z +
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. + [ToC] +
+ +

Lynx and HTML Forms

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

+

+
Buttons: +
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. + +
Checkboxes and Radio buttons +
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. + +
Selection Fields +
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 and down-arrow keys to move the cursor + between options and the right-arrow or Return + key to select an option. + +
Text Entry Fields +
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 Line Editor 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 submit the form if the text entry field is the + only non-hidden field in the form. +
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. +
+ +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 Line Editor as either text entries or editing commands. Select a +button or box when you want to use Lynx keystrokes. + +

To submit 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 form's source included a +META tag with a no-cache Pragma or Cache-Control directive:
+<META HTTP-EQUIV="Pragma" CONTENT="no-cache">
+<META HTTP-EQUIV="Cache-Control" CONTENT="no-cache">
+ +

Forms which have POST as the METHOD, or a mailto: 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 History Page. 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 image maps, 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, and will send that +instead of an artificial 0,0 coordinate pair if that button is named and +is used to submit the form. The script which analyzes the form content +thus can be made aware whether the submission was by a user with a graphic +client, or by a user who did not see the image nor 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 HTML 3.0 +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 tag. However, you can specify a mailto 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 does not yet support ENCTYPE="multipart/form-data" for +sending form content with name=value pairs encoded as multipart sections +with individual MIME headers and terminators. If the FORM tag indicates +that ENCTYPE, Lynx will render and display the form fields, but will treat +them as having the DISABLED attribute, so that they can't be +submitted with an inappropriate encoding. [ToC] + +

Lynx and HTML Tables

+ +HTML includes markup for creating tables structured as arrays of +cells aligned by columns and rows on the displayed page. + +

Lynx recognizes the TABLE tag and all of its associated tags as described +in ftp://ds.internic.net/rfc/rfc1942.txt +and will process any ID attributes in these tags for handling as NAME-ed +anchors, but does not create actual tables. Instead, it treats +the TR tag as a collapsible BR (line break), and inserts a collapsible +space before the content of each TH and TD 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 HTML Tabs. An example table using TAB +elements is included in the test subdirectory of the Lynx distribution. +[ToC] + +

Lynx and HTML Tabs

+ +Lynx implements the HTML 3.0 +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 Supported URLs page include TAB markup in +a manner which degrades gracefully for WWW browsers which do not +support it. Toggle to display of source and search for <tab to examine the use of TAB markup +in these documents. [ToC] + +

Lynx and HTML Frames

+ +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 tags, 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. +[ToC] + +

Lynx and HTML Banners

+ +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 HTML 3.0 +REL attribute tokens in LINK tags for creating a banner. The +LINK tokens are Home, ToC, Index, +Glossary, Copyright, Up, Next, +Previous, and Help. Any LINK tags with those tokens +will invoke creation of a banner at the top of the first page, +with the tag's HREF as the link, and the token as the link name. In +addition, a Bookmark token in conjunction with a TITLE attribute +will invoke a banner link with the value of the TITLE attribute +as the link name. 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. + +

Lynx also recognizes the HTML 3.0 +BANNER container tag, and will create a banner based on its content +if one has not already been created based on LINK tags. Lynx treats the +MicroSoft MARQUEE tag as a synonym for BANNER (i.e., presenting it's +markup as a static banner, without any horizontal scrolling of +its content). [ToC] + +

Lynx and HTML Footnotes

+ +Lynx implements the HTML 3.0 +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:
+See the <A +HREF="#fn1">footnote</A>.
+activating that link will take you to the labeled rendering of: + +

<FN ID="fn1"><p>Lynx +does not use popups for FN blocks.</p></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. +[ToC] + +

Lynx and HTML Notes

+ +Lynx implements the HTML 3.0 +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 HTML Footnotes, 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:
+<NOTE CLASS="warning" ID="too-bad">
+<p>The W3C vendors did not retain +NOTE in the HTML 3.2 draft.</p>
+</NOTE>
+It will degrade gracefully for WWW browsers which do not support +NOTE, except for recognition of the ID attribute as a named Anchor. +[ToC] + +

Lynx and HTML Lists

+ +Lynx implements the HTML 3.0 +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 HTML 2.0 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 +HTML 3.0 +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. +[ToC] + +

Lynx and HTML Quotes

+ +The HTML 3.0 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 tags within the quotation. The BLOCKQUOTE or BQ block +can include a CREDIT block, 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. [ToC] + +

Lynx and Client-Side-Image-Maps

+ +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 tag and its AREA tags, +and will create a menu of links for the HREF of each AREA tag when the +link created for the IMG tag with a USEMAP attribute is activated. The +menu uses the ALT attributes of the AREA tags 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 tag, 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 tag. 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 tags. 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 tag also indicates a server-side-image-map via +an ISMAP attribute, Lynx will create a link for that as well, rather +than ignoring it, and will submit a 0,0 coordinate pair if that link is +activated. However, the client-side-image-map is much 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 also recognizes the HTML 3.0 +FIG and OVERLAY tags, 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 tag encompasses much of the +functionality of the FIG tag for client-side-image-maps. Lynx +will render and display the content of OBJECT tags which have the SHAPES +attribute equivalently to its handling of FIG. Lynx also handles +OBJECT tags with the USEMAP and/or ISMAP attributes equivalently to +its handling of IMG tags with client-side-image-maps and/or +server-side-image-maps. [ToC] + +

Lynx and Client-Side-Pull

+ +HTML includes provision for passing instructions to clients via directives +in META tags, 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 a tag is:
+<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 tags, +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. +[ToC] + +

The Lynx command line

+ +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. The basic syntax of the Lynx command line can +be represented as one of the following: + +
+
Command +
lynx [options] +
lynx [options] startfile +
+ +where + +
+
startfile +
is the file or URL that Lynx will load at start-up. +
    +
  • If startfile is not specified, Lynx will use a default + starting file and base directory determined during + installation. +
  • 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. +
  • If a URL is specified, the file will be retrieved, + and only the server base directory will be relevant + to further accesses. +
+
options +
can be selected from the following list, where items in + all-caps indicate that a substitution must be made. +
+
- +
If the only argument is '-' (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 '$'. +
-anonymous +
used to specify the anonymous account. +
-auth=ID:PW +
id and password for protected pages. +
-book +
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. +
-buried_news +
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. +
-cache=NUMBER +
set the NUMBER of documents cached in memory. + The default is 10. +
-case +
enable case-sensitive string searching. +
-cfg=FILENAME +
specifies a Lynx configuration file other than the default + lynx.cfg. +
-child +
exit on left-arrow in startfile, and disable save to disk. +
-crawl +
with -traversal, output each page to a file.
+ with -dump, format output as with + -traversal, but to stdout. +
-display=DISPLAY +
set the display variable for X rexe-ced programs. +
-dump +
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/ +
-editor=EDITOR +
enable edit mode using the specified + EDITOR. (vi, ed, emacs, etc.) +
-emacskeys +
enable emacs-like key movement. +
-enable_scrollback +
toggles behavior compatible with the scrollback keys in + some communications software (may be incompatible with + some curses packages). +
-error_file=FILENAME +
the status code from the HTTP request is placed in this + file. +
-locexec +
enable local program execution from local files only + (if lynx was compiled with local execution enabled). +
-fileversions +
include all versions of files in local VMS directory + listings. +
-force_html +
forces the first document to be interpreted as HTML. +
-ftp +
disable ftp access. +
-get_data +
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 '---'. +
-head +
send a HEAD request for the mime headers. +
-help +
print this Lynx command syntax usage message. +
-historical +
toggles use of '>' or '-->' as a terminator for + comments. +
-homepage=URL +
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 + URL for the 'm'ain menu command. +
-image_links +
toggles inclusion of links for all images. +
-index=URL +
set the default index file to the specified URL +
-link=NUMBER +
starting count for lnk#.dat files produced by + -crawl. +
-localhost +
disable URLs that point to remote hosts. +
-mime_header +
include mime headers and force source dump. +
-minimal +
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. +
-newschunksize=NUMBER +
number of articles in chunked news listings. +
-newsmaxchunk=NUMBER +
maximum news articles in listings before chunking. +
-nobrowse +
disable directory browsing. +
-noexec +
disable local program execution. (DEFAULT) +
-nofilereferer +
disable transmissions of Referer headers for file URLs. +
-nofrom +
disable transmissions of From headers. +
-nolist +
disable the link list feature in dumps. +
-nolog +
disable mailing of error messages to document owners. +
-noprint +
disable print functions. +
-noredir +
don't follow URL redirections +
-noreferer +
disable transmissions of Referer headers. +
-nosocks +
disable SOCKS proxy usage by a SOCKSified Lynx. +
-nostatus +
disable the retrieval status messages. +
-number_links +
force numbering of links. +
-post_data +
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 '---'. +
-print +
enable print functions. (default) +
-pseudo_inlines +
toggles pseudo-ALTs for inlines with no ALT string. +
-raw +
toggles default setting of 8-bit character translations + or CJK mode for the startup character set. +
-realm +
restricts access to URLs in the starting realm. +
-reload +
flushes the cache on a proxy server + (only the first document affected). +
-restrictions +
allows a list of services to be disabled + selectively and takes the following form: +
lynx -restrictions=[option][,option][,option]... +
This list is printed if no options are specified. +
+
all +
restricts all options. +
bookmark +
disallow changing the location of the bookmark + file. +
bookmark_exec +
disallow execution links via the bookmark file. +
change_exec_perms +
disallow changing the eXecute permission on + files (but still allow it for directories) when + local file management is enabled. +
default +
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. +
dired_support +
disallow local file management. +
disk_save +
disallow saving binary files to disk in the + download menu. +
download +
disallow downloaders in the download menu. +
editor +
disallow editing. +
exec +
disable execution scripts. +
exec_frozen +
disallow the user from changing the local + execution option. +
file_url +
disallow using G)oto, served links or bookmarks + for file: URLs. +
goto +
disable the 'g' (goto) command. +
inside_ftp +
disallow ftps for people coming from inside your + domain. +
inside_news +
disallow USENET news posting for people coming + from inside you domain. +
inside_rlogin +
disallow rlogins for people coming from inside + your domain. +
inside_telnet +
disallow telnets for people coming from inside + your domain. +
jump +
disable the 'j' (jump) command. +
mail +
disable mailing feature. +
news_post +
disable USENET News posting. +
options_save +
disallow saving options in .lynxrc. +
outside_ftp +
disallow ftps for people coming from outside your + domain. +
outside_news +
disallow USENET news posting for people coming + from outside you domain. +
outside_rlogin +
disallow rlogins for people coming from outside + your domain. +
outside_telnet +
disallow telnets for people coming from + outside your domain. +
print +
disallow most print options. +
shell +
disallow shell escapes. +
suspend +
disallow Control-Z suspends with escape + to shell on Unix. +
telnet_port +
disallow specifying a port in telnet G)oto's. +
useragent +
disallow modifications of the User-Agent header. +
+ +
-resubmit_posts +
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. +
-rlogin +
disable recognition of rlogin commands. +
-selective +
require .www_browsable files to browse directories. +
-show_cursor +
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, and the default + configuration can be changed in userdefs.h. +
-soft_dquotes +
toggles emulation of the old Netscape and Mosaic bug which + treated '>' as a co-terminator for + double-quotes and tags. +
-source +
works the same as dump but outputs HTML source instead of + formatted text. +
-startfile_ok +
allow non-http startfile and homepage with + -validate. +
-telnet +
disable recognition of telnet commands. +
-term=TERM +
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.) +
-trace +
turns on WWW trace mode. +
-traversal +
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. +
-underscore +
toggles use of _underline_ format in dumps. +
-validate +
accept only http URLs (for validation). Complete + security restrictions also are implemented. +
-version +
print version information +
-vikeys +
enable vi-like key movement. +
+
+ +

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

Lynx development history

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

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

Information on obtaining the most current version of Lynx is +available via the +Lynx Enhanced Pages. + +

[ToC] + + diff --git a/lynx_help/keystroke_commands/bookmark_help.html b/lynx_help/keystroke_commands/bookmark_help.html new file mode 100644 index 00000000..4030be6b --- /dev/null +++ b/lynx_help/keystroke_commands/bookmark_help.html @@ -0,0 +1,20 @@ + + + +Lynx Bookmark Help + + + +

+++ Bookmark Help +++

+ +The Bookmark file is a document 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 current +Bookmark file. The remove feature, invoked by pressing an +'r' when your Bookmark file is being displayed, will +remove the currently highlighted link. You may set and modify the path +and name of your current Bookmark file in the options screen. + + diff --git a/lynx_help/keystroke_commands/dired_help.html b/lynx_help/keystroke_commands/dired_help.html new file mode 100644 index 00000000..eb1d1ae6 --- /dev/null +++ b/lynx_help/keystroke_commands/dired_help.html @@ -0,0 +1,51 @@ + + + +Lynx Dired Help + + + +

+++DIRED HELP+++

+ +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: +
+	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 options screen
+			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.
+
+ +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. + + diff --git a/lynx_help/keystroke_commands/edit_help.html b/lynx_help/keystroke_commands/edit_help.html new file mode 100644 index 00000000..4baa7232 --- /dev/null +++ b/lynx_help/keystroke_commands/edit_help.html @@ -0,0 +1,38 @@ + + + +Lynx Line Editor Default Key Binding + + + +

+++DEFAULT BINDING+++

+ +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: +
+     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
+
+ + diff --git a/lynx_help/keystroke_commands/gopher_types_help.html b/lynx_help/keystroke_commands/gopher_types_help.html new file mode 100644 index 00000000..aa134daa --- /dev/null +++ b/lynx_help/keystroke_commands/gopher_types_help.html @@ -0,0 +1,59 @@ + + + +Listing of Gopher types + + + +

+++ Gopher Types +++

+ +
+
(FILE) +
An ASCII file + +
(DIR) +
A directory listing + +
(CSO) +
The Computing Services Organizations +nameserver interface + +
(BIN) +
A binary file with one of the following meanings +
    +
  • A Binary file with PC extensions +
  • A Binary file with UNIX extensions +
+ +
(HQX) +
A Macintosh file that has be BinHexed + +
(?) +
A searchable database + + +
(IMG) +
An unknown image type +You must have an X terminal to +view images + +
(GIF) +
An image in Graphics Interchange Format +You must have an X terminal to +view images + +
(HTML) +
A World Wide Web hypertext file + +
(TEL) +
The link will open a connection to another host using telnet + +
(3270) +
The link will open a connection to another +host using tn3270 + +
(UKN) +
An unknown or unsupported type +
+ + diff --git a/lynx_help/keystroke_commands/history_help.html b/lynx_help/keystroke_commands/history_help.html new file mode 100644 index 00000000..eaf8949e --- /dev/null +++ b/lynx_help/keystroke_commands/history_help.html @@ -0,0 +1,28 @@ + + + +Help on the History page + + + +

+++ History Page Help +++

+ +The History Page displays all of the links that you have traveled through +to reach your current point. 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 it will +be in the history stack. + +

You may select 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. + + diff --git a/lynx_help/keystroke_commands/keystroke_help.html b/lynx_help/keystroke_commands/keystroke_help.html new file mode 100644 index 00000000..a11cfb3c --- /dev/null +++ b/lynx_help/keystroke_commands/keystroke_help.html @@ -0,0 +1,79 @@ + + + +HELP! -- Press the left arrow key to exit help + + + +

+++ Keystroke Commands +++

+
+  MOVEMENT:    Down arrow     - Highlight next topic
+               Up arrow       - Highlight previous topic
+               Right arrow,   - Jump to highlighted topic
+               Return, Enter
+               Left arrow     - Return to previous topic
+
+  SCROLLING:   +              - 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
+
+  DIRED:       c	      -	Create a new file
+	       d	      -	Download selected file
+	       e	      - Edit selected file
+               f              - Show a full menu of options for current file
+	       m	      - Modify the name or location of selected file
+	       r              - Remove selected file
+	       t              - Tag highlighted file
+	       u	      - Upload a file into the current directory
+	       
+  OTHER:       ? (or h)       - Help (this screen)
+               a              - Add the current link to your 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 URL or file
+	       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 options
+               p              - Print 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 your bookmark file
+               x              - Force submission of form or link with no-cache
+               z              - Cancel transfer in progress
+               [backspace]    - Go to the history page
+               =              - Show file and link info
+               \              - Toggle document source/rendered view
+	       !	      - Spawn your default shell
+	       '	      -	Toggle "historical" vs minimal or valid comment
+	       			parsing
+	       `	      -	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-W         - Refresh the screen
+               CTRL-U         - Erase input line
+               CTRL-G         - Cancel input or transfer
+               CTRL-T         - Toggle trace mode on and off
+
+ + diff --git a/lynx_help/keystroke_commands/movement_help.html b/lynx_help/keystroke_commands/movement_help.html new file mode 100644 index 00000000..4655db31 --- /dev/null +++ b/lynx_help/keystroke_commands/movement_help.html @@ -0,0 +1,49 @@ + + + +Help on Lynx Movement commands + + + +

+++ MOVEMENT HELP +++

+
+        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
+
+ + diff --git a/lynx_help/keystroke_commands/option_help.html b/lynx_help/keystroke_commands/option_help.html new file mode 100644 index 00000000..0cbc8297 --- /dev/null +++ b/lynx_help/keystroke_commands/option_help.html @@ -0,0 +1,164 @@ + + + +Options Screen Help + + + +

+++ Options Screen Help +++

+
+        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 X terminal
+                           display address.
+
+     Bookmark file      -  If non-empty it specifies the name of your
+                           'Bookmark file'.  If the filename is not
+                           absolute, then the path begins from your
+		           home directory.
+
+     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.  You 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
+
+     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)
+                           characters into viewable characters and should
+                           be set in relation 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 ISO Latin 1 conversion tables.  Should be
+	                   ON by default when the selected character set is
+                           ISO Latin 1, or 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 there's a match, e.g., the
+                           document's charset is ISO-8859-2 and ISO Latin 2
+                           has been selected.  Should be OFF when an Asian
+                           (CJK) set is selected but the document is
+                           ISO-8850-1.  The setting also can be toggled via
+                           the RAW_TOGGLE command, normally mapped to '@',
+                           and at startup via the -raw switch.
+
+     Preferred Document -  The language you prefer if multi-language files are
+     Language              available from servers.  Use MIME abbreviations,
+                           e.g., en for English, fr for French, etc.  Can be
+                           a comma-separated list in descending order of
+                           preferences.
+	
+     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 in descending order of
+                           preferences.
+	
+     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).
+
+     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 Default Binding.
+
+     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.
+
+     Show dot files    -   If display/creation of hidden (dot)
+                           files/directories is enabled, you can turn
+                           the feature on or off via this setting.
+
+     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.6 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 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 'ON', Lynx will locally execute
+     links                 commands contained inside of links.  This
+                           can be HIGHLY DANGEROUS so it is recommended
+                           that they remain 'ALWAYS OFF' unless
+                           otherwise set by your system administrator.
+                           This option may not be available on most
+                           versions of Lynx.
+
+
+ + diff --git a/lynx_help/keystroke_commands/other_help.html b/lynx_help/keystroke_commands/other_help.html new file mode 100644 index 00000000..4d248257 --- /dev/null +++ b/lynx_help/keystroke_commands/other_help.html @@ -0,0 +1,137 @@ + + + +Help on Misc. Lynx Commands + + + +

+++ Other Commands +++

+
+       a      -	Places the link that you are currently positioned
+		on in your personal bookmark file.
+
+       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.
+
+       g      -	Allows you to enter any URL or filename that
+		you wish to view.
+                        
+     ? 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 print commands.
+
+       o      -	Brings up a list of setable options.
+
+       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 options).
+
+       s      -	Search through an external searchable indexed document.
+
+       n      -	Move to the next instance of a search string if you 
+		have searched previously.
+
+       v      -	Views your current Bookmark file.
+
+       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 history page.
+
+       =      -	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.
+
+       `      -	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
+		options).
+
+       [      -	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-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.
+
+ + diff --git a/lynx_help/keystroke_commands/print_help.html b/lynx_help/keystroke_commands/print_help.html new file mode 100644 index 00000000..153caa74 --- /dev/null +++ b/lynx_help/keystroke_commands/print_help.html @@ -0,0 +1,37 @@ + + + +Lynx Print Help + + + +

+++ Printing Help +++

+ +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: + +
+
Print to a local file: +
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. + +
Print to the screen: +
This option simply scrolls the entire document up the screen and + is intended for those who wish to capture the document with their + terminal. + +
Mail the file to yourself: +
This option allows you to mail the file, in ASCII form, to any + valid e-mail address. + +
Custom print options: +
Any number of custom print options may be available, as defined + by your system administrator. +
+ + diff --git a/lynx_help/keystroke_commands/scrolling_help.html b/lynx_help/keystroke_commands/scrolling_help.html new file mode 100644 index 00000000..d1931346 --- /dev/null +++ b/lynx_help/keystroke_commands/scrolling_help.html @@ -0,0 +1,58 @@ + + + +Lynx Scrolling Help + + + +

+++ SCROLLING HELP +++

+
+        + (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.
+
+ + diff --git a/lynx_help/keystroke_commands/xterm_help.html b/lynx_help/keystroke_commands/xterm_help.html new file mode 100644 index 00000000..d40ea450 --- /dev/null +++ b/lynx_help/keystroke_commands/xterm_help.html @@ -0,0 +1,32 @@ + + + +X Terminal Help + + + +

+++ X Terminal or X Server +++

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

+
Note: +
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." +
+ + diff --git a/lynx_help/lynx_help_main.html b/lynx_help/lynx_help_main.html new file mode 100644 index 00000000..42fc5275 --- /dev/null +++ b/lynx_help/lynx_help_main.html @@ -0,0 +1,87 @@ + + + + +Help! - Press the Left arrow key to exit help + + + +

Lynx Help Menu

+ + + + + diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html new file mode 100644 index 00000000..8c0ed4f6 --- /dev/null +++ b/lynx_help/lynx_url_support.html @@ -0,0 +1,493 @@ + + + +URL Schemes Supported in Lynx + + + + + +[http, https | +telnet, tn3270, rlogin | +gopher | +file | +ftp | +wais | +news, nntp, snews | +mailto | +finger | +cso | +lynxexec, lynxprog | +lynxcgi| +internal] + + +

URL Schemes Supported in Lynx

+ +Lynx handles a number of URL types, that are enumerated below. For +more details about URLs (Uniform Resource Locators) see RFC1738: + + +

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

+ +

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

+ +

The http and https URLs:

+ +Lynx handles http URLs exactly as specified in RFC1738. The format +is:
+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 links in the +Lynx Enhanced +Pages. 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. +

+ +

The telnet, tn3270, and rlogin URLs:

+ +A telnet URL generally results in Lynx spawning a telnet +session. Lynx implements the complete telnet URL scheme, i.e.:
+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. +

+ +

The gopher URL:

+ +The gopher URL takes the form:
+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 gophertype +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.:
+gopher://www.wfbr.edu:80/hGET%20/
+will become:
+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. +

+ +

The file URL:

+ +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:
+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.:
+file://localhost/~/foo +will be converted to:
+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.:
+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. +

+ +

The ftp URL:

+ +The ftp URL has the general format:
+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.:
+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.:
+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 file URLs, e.g.:
+ftp://user@myhost/~ +

+ +

The wais URL:

+ +The wais URL is used to retrieve resources using the Wide Area Information +System protocol. The format is:
+wais://host:port/database
+wais://host:port/database?wais_query
+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 direct wais support is not available, Lynx uses +the W3C wais gateway. + +

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

+ +

The news, nntp, and snews URLs:

+ +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 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 +links in the Lynx Enhanced Pages but cannot be included in the general +distribution (sorry, see http and https). +The formats are:
+news:newsgroup (retrieves list of messages in newsgroup)
+news:messageID (retrieves the message)
+news:* (retrieves list of all available newsgroups)
+nntp://host:port/newsgroup
+nntp://host:port/messageID
+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.:
+news:comp.infosystems.*
+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. + +

For news URLs, Lynx allows you both to reply to the author +of a message via email, and, if news posting has been enabled, to send +a followup message to the newsgroup. Only email replies to the +author are permitted via nntp URLs. + +

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:
+news:newsgroup/startNo-endNo (lists message range in newsgroup)
+news:newsgroup/messageNo (retrieves the message by number)
+nntp://host:port/newsgroup/startNo-endNo
+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. +

+ +

The mailto URL:

+ +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:
+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.:
+<LINK REV="made"
+HREF="mailto:me@myhost,her@herhost" TITLE="The Subject"> + +

<A +HREF="mailto:user@host" TITLE="The Subject">...</A> + +

<FORM METHOD="post" +ENCTYPE="text/plain"
+ACTION="mailto:WebMaster@host" TITLE="The Subject">
+...
+</FORM> + +

Note that a TITLE attribute for FORM has been proposed but not included +in any HTML specifications or drafts, and should be considered a Lynxism +until/unless it is. Some clients use a SUBJECT attribute for this purpose +in FORM tags, and Lynx recognizes that as a synonym for TITLE. + +

If ENCTYPE="text/plain" is specified for a FORM with a mailto +ACTION, Lynx will not hex escape the name=value pairs, 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:
+ENCTYPE="application/x-www-form-urlencoded" ('&' separates pairs)
+or:
+ENCTYPE="application/sgml-form-urlencoded" (';' 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. +

+ +

The finger URL:

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

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

+ +

The cso URL:

+ +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:
+cso://host
+ +

You also can use a gopher URL format with port 105 and the CSO +(2) gophertype specified:
+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. +

+ +

The lynxexec and lynxprog URLs:

+ +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.:
+lynxexec:dir/date/size foo:[blah] (VMS)
+lynxexec:ls -l /foo/blah (Unix)
+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. +

+ +

The lynxcgi URL:

+ +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:
+ly +nxcgi://localhost/path_to_CGI_script
+where //localhost/ is optional and always implied. +The output of the script must 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. + +

On VMS, you are advised to use the threaded OSU http server, available +from ftp://osu.edu 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. +

+ +

The LYNXfoo internal URLs:

+ +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:
+Return to your <A HREF="LYNXHIST:0">Startfile</A>
+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:
+lynx LYNXKEYMAP:
+But within Lynx, use the 'K' keystroke command. + + -- cgit 1.4.1-2-gfad0