diff options
Diffstat (limited to 'lynx_help')
25 files changed, 8038 insertions, 0 deletions
diff --git a/lynx_help/Lynx_users_guide.html b/lynx_help/Lynx_users_guide.html new file mode 100644 index 00000000..b7fba2dc --- /dev/null +++ b/lynx_help/Lynx_users_guide.html @@ -0,0 +1,4365 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!-- $LynxId: Lynx_users_guide.html,v 1.116 2012/01/31 23:55:11 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Users Guide v2.8.7</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Lynx Users Guide v2.8.7</h1> + + <p>Lynx is a fully-featured <em>World Wide Web</em> + (<em>WWW</em>) client for users running cursor-addressable, + character-cell display devices (e.g., vt100 terminals, vt100 + emulators running on PCs or Macs, or any other character-cell + display). It will display <em>Hypertext Markup Language</em> + (<em>HTML</em>) documents containing links to files on the local + system, as well as files on remote systems running <em>http</em>, + <em>gopher</em>, <em>ftp</em>, <em>wais</em>, <em>nntp</em>, + <em>finger</em>, or <em>cso</em>/<em>ph</em>/<em>qi</em> servers, + and services accessible via logins to <em>telnet</em>, + <em>tn3270</em> or <em>rlogin</em> accounts (see <a href= + "lynx_url_support.html">URL Schemes Supported by Lynx</a>). + <a href="#Hist">Current</a> versions of Lynx run on Unix, VMS, + Windows3.x/9x/NT, 386DOS and OS/2 EMX.</p> + + <p>Lynx can be used to access information on the <em>WWW</em>, or + to build information systems intended primarily for local access. + For example, Lynx has been used to build several <em>Campus Wide + Information Systems</em> (<em>CWIS</em>). In addition, Lynx can + be used to build systems isolated within a single LAN.</p> + + <h2 id="TOC"><a name="Contents" id="Contents"><em>Table of + Contents</em></a></h2> + + <ul> + <li><a href="#Help" name="ToC-Help" id="ToC-Help">Lynx online + help</a></li> + + <li><a href="#Local" name="ToC-Local" id="ToC-Local">Viewing + local files with Lynx</a></li> + + <li><a href="#Leaving" name="ToC-Leaving" id= + "ToC-Leaving">Leaving Lynx</a></li> + + <li><a href="#Remote" name="ToC-Remote" id= + "ToC-Remote">Starting Lynx with a Remote File</a></li> + + <li><a href="#EnVar" name="ToC-EnVar" id="ToC-EnVar">Starting + Lynx with the WWW_HOME environment variable.</a></li> + + <li><a href="#IntraDocNav" name="ToC-IntraDocNav" id= + "ToC-IntraDocNav">Navigating hypertext documents with + Lynx</a></li> + + <li><a href="#Disposing" name="ToC-Disposing" id= + "ToC-Disposing">Printing, Mailing, and Saving rendered files to + disk.</a></li> + + <li><a href="#LocalSource" name="ToC-LocalSource" id= + "ToC-LocalSource">Viewing the HTML document source and editing + documents</a></li> + + <li><a href="#RemoteSource" name="ToC-RemoteSource" id= + "ToC-RemoteSource">Downloading and Saving source + files.</a></li> + + <li><a href="#ReDo" name="ToC-ReDo" id="ToC-ReDo">Reloading + files and refreshing the display</a></li> + + <li><a href="#Search" name="ToC-Search" id="ToC-Search">Lynx + searching commands</a></li> + + <li><a href="#InteractiveOptions" name="ToC-InteractiveOptions" + id="ToC-InteractiveOptions">Lynx Options Menu</a></li> + + <li><a href="#Mail" name="ToC-Mail" id="ToC-Mail">Comments and + mailto: links</a></li> + + <li><a href="#News" name="ToC-News" id="ToC-News">USENET News + posting</a></li> + + <li><a href="#Bookmarks" name="ToC-Bookmarks" id= + "ToC-Bookmarks">Lynx bookmarks</a></li> + + <li><a href="#Jumps" name="ToC-Jumps" id="ToC-Jumps">Jump + command</a></li> + + <li><a href="#DirEd" name="ToC-DirEd" id="ToC-DirEd">Directory + Editing</a></li> + + <li><a href="#ColorMouse" name="ToC-ColorMouse" id= + "ToC-ColorMouse">Using Color & the Mouse</a></li> + + <li><a href="#MiscKeys" name="ToC-MiscKeys" id= + "ToC-MiscKeys">Scrolling and Other useful commands</a></li> + + <li><a href="#Forms" name="ToC-Forms" id="ToC-Forms">Lynx and + HTML Forms</a> | <a href="#Images" name="ToC-Images" id= + "ToC-Images">Lynx and HTML Images</a></li> + + <li><a href="#Tables" name="ToC-Tables" id="ToC-Tables">Lynx + and HTML Tables</a> | <a href="#Tabs" name="ToC-Tabs" id= + "ToC-Tabs">Lynx and HTML Tabs</a></li> + + <li><a href="#Frames" name="ToC-Frames" id="ToC-Frames">Lynx + and HTML Frames</a> | <a href="#Banners" name="ToC-Banners" id= + "ToC-Banners">Lynx and HTML Banners</a></li> + + <li><a href="#Footnotes" name="ToC-Footnotes" id= + "ToC-Footnotes">Lynx and HTML Footnotes</a> | <a href="#Notes" + name="ToC-Notes" id="ToC-Notes">Lynx and HTML Notes</a></li> + + <li><a href="#Lists" name="ToC-Lists" id="ToC-Lists">Lynx and + HTML Lists</a></li> + + <li><a href="#Quotes" name="ToC-Quotes" id="ToC-Quotes">Lynx + and HTML Quotes</a></li> + + <li><a href="#Eightbit" name="ToC-Eightbit" id= + "ToC-Eightbit">Lynx and HTML Internationalization: 8bit, + UNICODE, etc.</a></li> + + <li><a href="#USEMAP" name="ToC-USEMAP" id="ToC-USEMAP">Lynx + and Client-Side-Image-Maps</a></li> + + <li><a href="#Refresh" name="ToC-Refresh" id="ToC-Refresh">Lynx + and Client-Side-Pull</a></li> + + <li><a href="#Cookies" name="ToC-Cookies" id="ToC-Cookies">Lynx + and State Management</a> (Me want <em>cookie</em>!)</li> + + <li><a href="#Cache" name="ToC-Cache" id="ToC-Cache">Lynx and + Cached Documents</a></li> + + <li><a href="#Sessions" name="ToC-Sessions" id= + "ToC-Sessions">Lynx and Sessions</a></li> + + <li><a href="#Invoking" name="ToC-Invoking" id= + "ToC-Invoking">The Lynx command line</a></li> + + <li><a href="#Environment" name="ToC-Environment" id= + "ToC-Environment">Environment variables used by Lynx</a></li> + + <li><a href="#lynx.cfg" name="ToC-lynx.cfg" id= + "ToC-lynx.cfg">Main configuration file lynx.cfg</a></li> + + <li><a href="#Hist" name="ToC-Hist" id="ToC-Hist">Lynx + development history</a></li> + </ul> + + <h2 id="id-Help"><a name="Help" id="Help"><em>Lynx online + help</em></a></h2> + + <p>Online help is available while viewing any document. Press the + '<em>?</em>' or '<em>H</em>' key (or the '<em>h</em>' key if + vi-like key movement is not on) to see a list of help topics. See + the section titled <a href="#IntraDocNav">Navigating hypertext + documents with Lynx</a> for information on navigating through the + help files.</p> + + <p>In addition, a summary description of all the Lynx keystroke + commands and their key bindings is available by pressing the + '<em>K</em>' key (or the '<em>k</em>' key if vi-like key movement + is not on).</p> + + <p>If you want to recall recent status-line messages, you can do + so by entering the `g' command, followed by `LYNXMESSAGES:'.</p> + + <p>[<a href="#ToC-Help">ToC</a>]</p> + + <h2 id="id-Local"><a name="Local" id="Local"><em>Viewing local + files with Lynx</em></a></h2> + + <p>Lynx can be started by entering the Lynx command along with + the name of a file to display. For example these commands could + all be used to display an arbitrary ASCII text or HTML file:</p> + + <dl> + <dt>UNIX</dt> + + <dd><code>lynx filename</code></dd> + + <dd><code>lynx /home/my-dir/filename</code></dd> + + <dd><code>lynx ~/filename</code></dd> + + <dt>VMS</dt> + + <dd><code>lynx filename</code></dd> + + <dd><code>lynx dua5:[my-directory]filename</code></dd> + + <dd><code>lynx /dua5/my-directory/filename</code></dd> + + <dd><code>lynx ~/filename</code></dd> + + <dd><code>lynx sys$login:filename</code></dd> + + <dd><code>lynx /sys$login/filename</code></dd> + + <dt>Win32/DOS</dt> + + <dd><code>lynx file:///filename</code></dd> + + <dd><code>lynx filename</code></dd> + + <dd><code>lynx c:/dir/filename</code></dd> + + <dd><code>lynx //n/dir/filename</code></dd> + </dl> + + <p>When executed, Lynx will clear the screen and display as much + of the specified file as will fit on the screen. Pressing a + <em>down-arrow</em> will bring up the next screen, and pressing + an <em>up-arrow</em> will bring up the previous screen. If no + file is specified at startup, a default file will be displayed, + depending on settings e.g., in <em>lynx.cfg</em>.</p> + + <p>Lynx will display local files written in the <em>HyperText + Markup Language</em> (<em>HTML</em>), if the file's name ends + with the characters <em>.html</em>, <em>.htm</em>, + <em>.shtml</em>, <em>.htmlx</em>, <em>.html3</em>, or + <em>.ht3</em>. HTML is a file format that allows users to create + a file that contains (among other things) hypertext links to + other files. Several files linked together may be described as a + <em>hypertext document</em>. If the filename does not have one of + the suffixes mapped by Lynx to HTML, the <em>-force_html</em> + command line option can be included to force treatment of the + file as hypertext.</p> + + <p>When Lynx displays an HTML file, it shows links as "bold face" + text, except for one link, which is shown as "highlighted" text. + Whether "boldface" or "highlighted" text shows up as reverse + video, boldface type, or a color change, etc. depends on the + display device being used (and the way in which that device has + been configured). Lynx has no control over the exact presentation + of links.</p> + + <p>The one link displayed as "highlighted" text is the currently + "selected" link. Lynx will display the file associated with the + selected link when a <em>right-arrow</em> or a <em>Return</em> + key is pressed. To select a particular link, press the + <em>up-arrow</em> or <em>down-arrow</em> keys until the desired + link becomes "highlighted," and then press the + <em>right-arrow</em> or <em>Return</em> key to view the linked + information. Information included in the HTML file tells Lynx + where to find the linked file and what kind of server will + provide it (i.e., HTTP, Gopher, etc.).</p> + + <p>Lynx renders HTML files and saves the rendition (and the + source, if so configured in the <a href="#lynx.cfg">lynx.cfg</a> + file) for initial display and should you select the link again. + If you do select a link again and have reason to desire a new + fetch and rendering of the file, use the NOCACHE command, + normally mapped to '<em>x</em>' and '<em>X</em>', instead of the + <em>right-arrow</em> or <em>Return</em> key when positioned on + the link. You also can force a new fetch and rendering of the + currently displayed document via the RELOAD command, normally + mapped to <em>Control-R</em>.</p> + + <p>When a binary file is encountered Lynx will ask the user if + he/she wishes to download the file or cancel. If the user selects + '<em>D'</em> for download, Lynx will transfer the file into a + temporary location and present the user with a list of options. + The only default option is <em>Save to disk</em>, which is + disabled if Lynx is running in anonymous mode. Additional + download methods may be defined in the <a href= + "#lynx.cfg">lynx.cfg</a> file. Programs like kermit, zmodem and + FTP are some possible options.</p> + + <p>[<a href="#ToC-Local">ToC</a>]</p> + + <h2 id="id-Leaving"><a name="Leaving" id="Leaving"><em>Leaving + Lynx</em></a></h2> + + <p>To exit Lynx use the '<em>q</em>' command. You will be asked + whether you really want to quit. Answering '<em>y</em>' will exit + and '<em>n</em>' will return you to the current document. Use + '<em>Q</em>' or <em>Control-D</em> to quit without + verification.</p> + + <p>[<a href="#ToC-Leaving">ToC</a>]</p> + + <h2 id="id-Remote"><a name="Remote" id="Remote"><em>Starting Lynx + with a Remote File</em></a></h2> + + <p>If you wish to view a remote file (that is, a file residing on + some computer system other than the one upon which you are + running Lynx) without first viewing a local file, you must + identify that file by using a Uniform Resource Locator (URL). + URLs take the general form:</p> + + <p><code>PROTOCOL :// HOST / PATH</code></p> + + <p>where</p> + + <dl> + <dt><code>PROTOCOL</code></dt> + + <dd>identifies the communications protocol (<em>scheme</em>) + used by the server that will provide the file. As mentioned + earlier, Lynx (and any WWW client) can interact with a variety + of servers, each with its own protocol.</dd> + + <dt><code>HOST</code></dt> + + <dd>is the Internet address of the computer system on which the + server is running, and</dd> + + <dt><code>PATH</code></dt> + + <dd>is a scheme-specific field which for some schemes may + correspond to a directory path and/or filename.</dd> + </dl>Here are some sample URLs. + + <dl> + <dt>HTTP (HyperText Transfer Protocol)</dt> + + <dd><code>http://www.subir.com/lynx.html</code></dd> + + <dt>Gopher</dt> + + <dd><code>gopher://gopher.micro.umn.edu/11/</code></dd> + + <dt>FTP (File Transfer Protocol)</dt> + + <dd><code>ftp://ftp2.cc.ukans.edu/pub/lynx/README</code></dd> + + <dt>WAIS (Wide Area Information Service protocol)</dt> + + <dd><code>wais://cnidr.org/directory-of-servers</code></dd> + + <dt>A URL may be specified to Lynx on the command line, as + in:</dt> + + <dd><code>lynx + http://kufacts.cc.ukans.edu/cwis/kufacts_start.html</code></dd> + </dl>Lynx also will attempt to create a complete URL if you + include adequate portions of it in the startfile argument. For + example:<br> + <pre> +1234.6789.1234.6789.1234.6789.1234.6789.1234.6789.1234.6789.1234.6789.1234.6789 + <em>wfbr</em> will be expanded to: + <em>http://www.wfbr.edu/</em> and: + <em>ftp.more.net/pub</em> will be expanded to: + <em>ftp://ftp.more.net/pub</em> +</pre>See <a href="lynx_url_support.html">URL Schemes Supported by +Lynx</a> for more detailed information. + + <p>[<a href="#ToC-Remote">ToC</a>]</p> + + <h2 id="id-EnVar"><a name="EnVar" id="EnVar"><em>Starting Lynx + with the WWW_HOME environment variable.</em></a></h2> + + <p>You may also specify a starting file for Lynx using the + WWW_HOME environment variable,</p> + + <dl> + <dt>UNIX</dt> + + <dd> + <dl> + <dt>ksh</dt> + + <dd><code>export WWW_HOME=http://www.w3.org/</code></dd> + + <dt>csh</dt> + + <dd><code>setenv WWW_HOME http://www.w3.org/</code></dd> + </dl> + </dd> + + <dt>VMS</dt> + + <dd><code>define "WWW_HOME" "http://www.w3.org/"</code></dd> + + <dt>win32</dt> + + <dd><code>WWW_HOME=http://www.w3.org/ [or in + registry]</code></dd> + </dl>Note that on VMS the double-quoting <em>must</em> be + included to preserve casing. + + <p>[<a href="#ToC-EnVar">ToC</a>]</p> + + <h2 id="id-IntraDocNav"><a name="IntraDocNav" id= + "IntraDocNav"><em>Navigating hypertext documents with + Lynx</em></a></h2> + + <p>The process of moving within a hypertext web, selecting and + displaying links is known as "navigation." With Lynx almost all + navigation can be accomplished with the arrow keys and the + numeric keypad.</p> + <pre> + +-------+-------+-------+ + | TOP | /|\ | Page | + arrow keys | of | | | UP | + | text 7| | 8| 9| + +---------+ +-------+-------+-------+ + | SELECT | | | | | + | prev /|\| | <--- | | ---> | + | link | | | 4| 5| 6| + +---------+---------+---------+ +-------+-------+-------+ + | BACK | SELECT | DISPLAY | | END | | | Page | + |<-- prev | next | | sel. -->| | of | | | DOWN | + | doc. | link \|/| link | | text 1| \|/ 2| 3| + +---------+---------+---------+ +-------+-------+-------+ +</pre>There are also a few other keyboard commands to aid in +navigation. The Control and Function keys used for navigation +within the current document are described in <a href= +"#MiscKeys"><em>Scrolling and Other useful commands</em></a>. Some +additional commands depend on the fact that Lynx keeps a list of +each link you visited to reach the current document, called the +<a href="keystrokes/history_help.html">History Page</a>, and a list +of all links visited during the current Lynx session, called the +<a href="keystrokes/visited_help.html">Visited Links Page</a>. The +HISTORY keystroke command, normally mapped to <em>Backspace</em> or +<em>Delete</em>, will show you the <em>History Page</em> of links +leading to your access of the current document. Any of the previous +documents shown in the list may be revisited by selecting them from +the history screen. The VLINKS keystroke command, normally mapped +to uppercase '<em>V</em>', will show the <em>Visited Links +Page</em>, and you similarly can select links in that list. The +MAIN_MENU keystroke command, normally mapped to '<em>m</em>' and +'<em>M</em>', will take you back to the starting document unless +you specified the <em>-homepage=URL</em> option at the command +line. Also, the LIST and ADDRLIST keystroke commands, normally +mapped to '<em>l</em>' and <em>A</em>' respectively, will create a +compact lists of all the links in the current document, and they +can be selected via those lists. + + <p>The '<em>i</em>' key presents an index of documents. The + default index offered contains many useful links, but can be + changed in <em>lynx.cfg</em> or on the command line using the + <em>-index=URL</em> switch.</p> + + <p>If you choose a link to a server with active access + authorization, Lynx will automatically prompt for a username and + a password. If you give the correct information, you will then be + served the requested information. Lynx will automatically send + your username and password to the same server if it is needed + again.</p> + + <p>[<a href="#ToC-IntraDocNav">ToC</a>]</p> + + <h2 id="id-Disposing"><a name="Disposing" id= + "Disposing"><em>Printing, Mailing, and Saving rendered files to + disk.</em></a></h2> + + <p>Rendered HTML documents, and plain text files, may be printed + using the '<em>p</em>' command while viewing the document. After + pressing the '<em>p</em>' key a menu of <em>Print Options</em> + will be displayed. The menu will vary according to several + factors. First, some sites set up special accounts to let users + run Lynx to access local information systems. Typically these + accounts require no passwords and do not require users to + identify themselves. As a result such accounts are called + "anonymous" accounts, and their users are considered "anonymous" + users. In most configurations, all Lynx users (including + anonymous users) are able to mail files to themselves and print + the entire file to the screen.</p> + + <p>Additional print options are available for users who are using + Lynx from their own accounts (that is, so-called "non-anonymous + users"). In particular, the <em>Save to a local file</em> option + allows you to save the document into a file on your disk space. + Additional print options may also be available as configured in + the <a href="#lynx.cfg">lynx.cfg</a> file.</p> + + <p>Some options, such as <em>Save to a local file</em>, involve + prompting for an output filename. All output filename entries are + saved in a circular buffer, and any previous entries can be + retrieved for re-use by pressing the <em>up-arrow</em> or + <em>down-arrow</em> keys at the prompt.</p> + + <p>Note that if you want exact copies of text files without any + expansions of TAB characters to spaces you should use the + <a href="#RemoteSource">Download</a> options.</p> + + <p>[<a href="#ToC-Disposing">ToC</a>]</p> + + <h2 id="id-LocalSource"><a name="LocalSource" id= + "LocalSource"><em>Viewing the HTML document source and editing + documents</em></a></h2> + + <p>When viewing HTML documents it is possible to retrieve and + display the unrendered (i.e., the original HTML) source of the + document by pressing the '<em>\</em>' (backslash) key. Lynx + usually caches only the rendering of the document and doesn't + keep the source (unless it is configured to do so in the <a href= + "#lynx.cfg">lynx.cfg</a> file), so to display the source + unrendered, Lynx must reload it from the server or disk. When + viewing unrendered documents you may print them as any normal + document.</p> + + <p>Selecting the <em>Print to a local file</em> option from the + Print Menu, makes it possible to save the source of the document + to disk so that you may have a local copy of the document source, + but it is better to <a href="#RemoteSource">Download</a> the + source.</p> + + <p>NOTE: When saving an HTML document it is important to name the + document with a <em>.html</em> or <em>.htm</em> extension, if you + want to read it with Lynx again later.</p> + + <p id="FileEdit">Lynx can allow users to edit documents that + reside on the local system. To enable editing, documents must be + referenced using a "file:" URL or by specifying a plain filename + on the command line as in the following two examples:</p> + + <dl> + <dt>Command</dt> + + <dd><code>lynx file://localhost/FULL/PATH/FILENAME</code></dd> + + <dd><code>lynx path/filename.html</code></dd> + </dl>In addition, the user must also specify an editor in the + <em>Options Menu</em> so that Lynx knows which editor to use. If + the file is specified correctly and an editor is defined, then + you may edit documents by using the '<em>e</em>' command. When + the '<em>e</em>' command is entered your specified editor is + spawned to edit the file. After changes are completed, exit your + editor and you will return to Lynx. Lynx will reload and render + the file so that changes can be immediately examined. + + <p>[<a href="#ToC-LocalSource">ToC</a>]</p> + + <h2 id="id-RemoteSource"><a name="RemoteSource" id= + "RemoteSource"><em>Downloading and Saving source + files.</em></a></h2> + + <p>If the DOWNLOAD keystroke command ('<em>d</em>' or <em>D</em>) + is used when positioned on a link for an HTML, plain text, or + binary file, Lynx will transfer the file, without rendering, into + a temporary location and present the user with a list of options, + just as it does when a link for a binary file of a type for which + no viewer has been mapped is activated.</p> + + <p>There is a default <em>Download option</em> of <em>Save to + disk</em>. This is disabled if Lynx is running in anonymous mode. + Any number of download methods such as kermit and zmodem may be + defined in addition to this default in the <em>lynx.cfg</em> + file. Using the <em>Save to disk</em> option under the PRINT + command after viewing the source of an HTML with the VIEW SOURCE + (<em>\</em>) command will result in a file which differs from the + original source in various ways such as tab characters expanded + to spaces. Lynx formats the source presentation in this mode. On + the other hand, if the DOWNLOAD command is used, the only change + will be that Lynx optionally puts</p> + + <blockquote> + <!--X-URL: http://www.site.foo/path/to/file.html --><br> + <BASE href="http://www.site.foo/path/to/file.html"> + </blockquote>at the start of the file so that relative URLs in + the document will still work. Even this modification can be + prevented by setting PREPEND_BASE_TO_SOURCE:FALSE in lynx.cfg. + + <p>Some options, such as <em>Save to disk</em>, involve prompting + for an output filename. All output filename entries are saved in + a circular buffer, and any previous entries can be retrieved for + re-use by pressing the <em>up-arrow</em> or <em>down-arrow</em> + keys at the prompt.</p> + + <p>[<a href="#ToC-RemoteSource">ToC</a>]</p> + + <h2 id="id-ReDo"><a name="ReDo" id="ReDo"><em>Reloading files and + refreshing the display</em></a></h2> + + <p>The RELOAD (<em>Control-R</em>) command will reload and + re-render the file that you are currently viewing. The REFRESH + (<em>Control-L</em> or <em>Control-W</em>) command will refresh + or wipe the screen to remove or correct any errors that may be + caused by operating system or other messages.</p> + + <p>The NOCACHE ('<em>x</em>' or '<em>X</em>') command can be used + in lieu of ACTIVATE (<em>Return</em> or <em>right-arrow</em>) to + request an uncached copy and new rendition for the current link, + or resubmission of a FORM, if a cache from a previous request or + submission exits. The request or submission will include + <em>Pragma: no-cache</em> and <em>Cache-Control: no-cache</em> in + its headers. Note that FORMs with POST content will be + resubmitted regardless of whether the NOCACHE or ACTIVATE command + is used (see <a href="#Forms"><em>Lynx and HTML + Forms</em></a>).</p> + + <p>[<a href="#ToC-ReDo">ToC</a>]</p> + + <h2 id="id-Search"><a name="Search" id="Search"><em>Lynx + searching commands</em></a></h2> + + <p>Two commands activate searching in Lynx: '<em>/</em>' and + '<em>s</em>'.</p> + + <p>While viewing a normal document use the '<em>/</em>' command + to find a word or phrase within the current document. The search + type will depend on the search option setting in the <a href= + "#InteractiveOptions">Options Menu</a>. The search options are + case sensitive and case insensitive. These searches are entirely + local to Lynx.</p> + + <p>Some documents are designated <em>index documents</em> by + virtue of an ISINDEX element in their HEAD section. These + documents can be used to retrieve additional information based on + searches using words or phrases submitted to an index server. The + Lynx statusline will indicate that you are viewing such a + document, and if so, the '<em>s</em>' key will invoke a + statusline prompt to enter a query string. The prompt can be + specified via a PROMPT attribute in the ISINDEX element. + Otherwise, Lynx will use an internally configured prompt. The + address for submitting the search can be specified via an HREF or + ACTION attribute. Otherwise, Lynx will use the current document's + URL and append your query string as a <em>?searchpart</em> (see + <a href="lynx_url_support.html">Supported URLs</a>).</p> + + <p>All search words or strings which you have entered during a + Lynx session are saved in a circular buffer, and can be retrieved + for re-use by pressing the <em>up-arrow</em> or + <em>down-arrow</em> keys at the prompt for a search word or + string. Also, you can use the '<em>n</em>'ext command to repeat a + search with the last-entered search word or phrase, starting from + the current position in the document. The word or phrase matches + will be highlighted throughout the document, but such + highlighting will not persist for new documents, or if the + current document is reloaded. The search cycles to the top of the + document if the word or phrase is not located below your current + position.</p> + + <p>Although <a href="#Forms">HTML Forms</a> have largely replaced + index documents for searches via http servers, they are still + useful for performing searches directly via WAIS or Gopher + servers in conjunction with the internal gateways for such + servers. For example, an HTML index document can act as a + <em>cover page</em> describing a WAIS database and how to + formulate query strings for searching it, and include an element + such as:<br></p> + <pre> + <em><ISINDEX PROMPT="Enter WAIS query:" + HREF="wais://net.bio.net/biologists-addresses"></em> +</pre>for submitting a search of the Biologist's Addresses database +directly to the net.bio.net WAIS server. + + <p>[<a href="#ToC-Search">ToC</a>]</p> + + <h2 id="id-InteractiveOptions"><a name="InteractiveOptions" id= + "InteractiveOptions"><em>Lynx Options Menu</em></a></h2> + + <p>The Lynx <em>Options Menu</em> may be accessed by pressing the + '<em>o</em>' key. It allows you to change options at runtime, if + you need to. Most changes are read from & saved to your + .lynxrc file; those which are not are marked (!) in the + form-based menu (as below). Many other options are stored in the + <a href="#lynx.cfg">lynx.cfg</a> file.</p> + + <p>Lynx supports two styles of Options Menu, key-based & + form-based. The form-based menu shown below is an HTML file + generated at runtime, in which the user fills in choices as in + any ordinary HTML form.</p> + <pre> + + Options Menu (Lynx Version 2.8.7rel.1) + + Accept Changes - Reset Changes Left Arrow cancels changes <a href="keystrokes/option_help.html">HELP!</a> + + Save options to disk: [_] + (options marked with (!) will not be saved) + + General Preferences + User mode : [Advanced....] + Editor : __________________________________________ + Type of Search : [Case insensitive] + + Security and Privacy + Cookies (!) : [ask user..] + Invalid-Cookie Prompting (!) : [prompt normally___] + SSL Prompting (!) : [prompt normally___] + + Keyboard Input + Keypad mode : [Links are numbered................] + Emacs keys : [OFF] + VI keys : [OFF] + Line edit style : [Bash-like Bindings] + Keyboard layout : [YAWERTY Cyrillic, for DEC LK201 kbd] + + Display and Character Sets + Use locale-based character set(!): [OFF] + Use HTML5 charset replacements(!): [OFF] + Display character set : [Cyrillic (ISO-8859-5)..........] + Assumed document character set(!): [iso-8859-1......] + Raw 8-bit (!) : [OFF] + X Display (!) : __________________________________________ + + Document Appearance + Show color : [ON....] + Show cursor : [OFF] + Underline links (!) : [OFF] + Show scrollbar : [OFF] + Popups for select fields : [ON.] + HTML error recovery (!) : [strict (SortaSGML mode)] + Bad HTML messages (!) : [Warn, point to trace-file] + Show images (!) : [as labels] + Verbose images : [OFF..........] + + Headers Transferred to Remote Servers + Personal mail address : __________________________________________ + Personal mail name : __________________________________________ + Password for anonymous ftp : __________________________________________ + Preferred media type (!) : [Accept lynx's internal types] + Preferred encoding (!) : [All_____] + Preferred document character set : _________________________________ + Preferred document language : _________________________________ + Send User-Agent header (!) : [ ] + User-Agent header (!) : __________________________________________ + + Listing and Accessing Files + Use Passive FTP (!) : [ON_] + FTP sort criteria : [By Name] + Local directory sort criteria : [Mixed style......] + Local directory sort order : [By name..........] + Show dot files : [ON.] + Execution links : [FOR LOCAL FILES ONLY] + Pause when showing message (!) : [ON_] + Show transfer rate : [Show progressbar___] + + Special Files and Screens + Multi-bookmarks : [ADVANCED] + Review/edit Bookmarks files : Goto multi-bookmark menu + Auto Session (!) : [OFF] + Session file (!) : ___________________________________________ + Visited Pages : [As Visit Tree..........] + + View the file lynx.cfg + + Accept Changes - Reset Changes Left Arrow cancels changes + +</pre> + + <p>The key-based menu depends on key-strokes to identify options + which the user wants to change. It is compiled into Lynx and is + accessed by setting FORMS_OPTIONS to TRUE in <a href= + "#lynx.cfg">lynx.cfg</a>.</p> + <pre> + + Options Menu (Lynx Version 2.8.7rel.1) + + (E)ditor : emacs + (D)ISPLAY variable : aixtest.cc.ukans.edu:0.0 + mu(L)ti-bookmarks: OFF B)ookmark file: lynx_bookmarks.html + (F)TP sort criteria : By Filename + (P)ersonal mail address : montulli@netscape.com + (S)earching type : CASE INSENSITIVE + preferred document lan(G)uage: en + preferred document c(H)arset : NONE + display (C)haracter set : Western (ISO-8859-1) + raw 8-bit or CJK m(O)de : ON show color (&) : OFF + (V)I keys: OFF e(M)acs keys: OFF sho(W) dot files: OFF + popups for selec(T) fields : ON show cursor (@) : OFF + (K)eypad mode : Numbers act as arrows + li(N)e edit style : Default Binding + l(I)st directory style : Mixed style + (U)ser mode : Advanced verbose images (!) : ON + user (A)gent : [User-Agent header] + local e(X)ecution links : FOR LOCAL FILES ONLY +</pre>An option can be changed by entering the capital letter or +character in parentheses for the option you wish to change (e.g., +'<em>E</em>' for Editor or '<em>@</em>' for show cursor). For +fields where text must be entered, simply enter the text by typing +on the keyboard. The <a href="keystrokes/edit_help.html">Line +Editor</a> can be used to correct mistakes, and <em>Control-U</em> +can be used to erase the line. When you are done entering a change +press the <em>Return</em> key to get back to the <em>Command?</em> +prompt. + + <p>For fields where you must choose one of two choices, press any + key to toggle the choices and press the <em>Return</em> key to + finish the change.</p> + + <p>For fields where you potentially have more than two choices, + popup windows may be evoked which function homologously to those + for select fields in <a href="#Forms">HTML Forms</a>. The popup + windows will be invoked only if you have popups for select fields + set to ON (see below). Otherwise, your cursor will be positioned + at the current choice, and you can press any key to cycle through + the choices, then press the <em>Return</em> key to finish the + change.</p> + + <p>When you are done changing options use the '<em>r</em>' + command to return to Lynx or the '<em>></em>' command to save + the options to a <em>.lynxrc</em> file and return to Lynx.</p> + + <p>The following table describes the options available on the + <em>Options Menu</em>:</p> + + <dl> + <dt>Assumed document character set</dt> + + <dd>This option changes the handling of documents which do not + explicitly specify a charset. Normally Lynx assumes that 8-bit + characters in those documents are encoded according to + iso-8859-1 (the official default for the HTTP protocol). + Unfortunately, many non-English web pages "forget" to include + proper charset info; this option helps you to browse those + broken pages if you know by some means what the charset is. + When the value given here or by an -assume_charset command line + flag is in effect, Lynx will treat documents as if they were + encoded accordingly. This option active when 'Raw 8-bit or CJK + Mode' is OFF.</dd> + + <dt>Auto Session</dt> + + <dt>Lynx can save and restore useful information about your + browsing history. Use this setting to enable or disable the + feature.</dt> + + <dt>Bad HTML messages</dt> + + <dd> + Suppress or redirect Lynx's messages about "Bad HTML": + + <dl> + <dt>Ignore</dt> + + <dd>do not warn; no details are written to the + trace-file.</dd> + + <dt>Add to trace-file</dt> + + <dd>add the detailed warning message to the + trace-file.</dd> + + <dt>Add to LYNXMESSAGES</dt> + + <dd>add the detailed warning message to the message page at + "LYNXMESSAGES:".</dd> + + <dt>Warn, point to trace-file</dt> + + <dd>show a warning message on the status line; the complete + message is written to the trace-file.</dd> + </dl> + </dd> + + <dt>Bookmark file</dt> + + <dd> + When multi-bookmarks is OFF, this is the filename and + location of your default personal bookmark file. Enter + '<em>B</em>' to modify the filename and/or location via the + <a href="keystrokes/edit_help.html">Line Editor</a>. Bookmark + files allow frequently traveled links to be stored in + personal easy to access files. + + <p>Using the '<em>a</em>'dd bookmark link command (see + <a href="#Bookmarks">Lynx bookmarks</a>) you may save any + link that does not have associated POST content into a + bookmark file. All bookmark files must be in or under your + account's home directory. If the location specified does not + begin with a dot-slash (./), its presence will still be + assumed, and referenced to the home directory.</p> + + <p>When multi-bookmarks is STANDARD or ADVANCED, entering + '<em>B</em>' will invoke a menu of up to 26 bookmark files + (associated with the letters of the English alphabet), for + editing their filenames and locations (<em>filepath</em>), + and descriptions.</p> + + <p>Lynx will create bookmark files, if they don't already + exist, when you first '<em>a</em>'dd a bookmark link to them. + However, if you've specified a subdirectory (e.g., + ./BM/lynx_bookmarks.html), that subdirectory must already + exist. Note that on VMS you should use the URL syntax for the + filepath (e.g., <em>not</em> [.BM]lynx_bookmarks.html).</p> + </dd> + + <dt>Cookies</dt> + + <dd>This option allows you to tell how to handle cookies: + <em>ignore</em>, prompt (<em>ask user</em>) or <em>accept + all</em>.</dd> + + <dt>Display Character set</dt> + + <dd>This option allows you to set up the default character set + for your specific terminal. The display character set provides + a mapping from the character encodings of viewed documents and + from HTML entities into viewable characters. It should be set + according to your terminal's character set so that characters + other than 7-bit ASCII can be displayed correctly, using + approximations if necessary. You must have the selected + character set installed on your terminal. (Since Lynx now + supports a wide range of platforms it may be useful to note + that cpXXX codepages used within IBM PC computers, and + windows-xxxx within native MS-Windows apps.)</dd> + + <dt>Editor</dt> + + <dd>The editor to be invoked when editing browsable files, when + sending mail or comments, when preparing a news article for + posting, and for external TEXTAREA editing. The full pathname + of the editor command should be specified when possible.</dd> + + <dt>Emacs keys</dt> + + <dd> + If set to ON then the CTRL-P, CTRL-N, CTRL-F, and CTRL-B keys + will be mapped to up-arrow, down-arrow, right-arrow, and + left-arrow, respectively. Otherwise, they remain mapped to + their configured bindings (normally UP_TWO lines, DOWN_TWO + lines, NEXT_PAGE, and PREV_PAGE, respectively). + + <p>Note: this has no direct effect on the line-editor's key + bindings.</p> + </dd> + + <dt>Execution links<br> + This deals with execution of local scripts or links:</dt> + + <dd>Local execution is activated when Lynx is first set up. If + it has not been activated you will not see this option in the + <em>Options Menu</em>.</dd> + + <dd> + When a local execution script is encountered Lynx checks the + users options to see whether the script can be executed. + Users have the following options: + + <dl> + <dt>Always off</dt> + + <dd>Local execution scripts will never be executed</dd> + + <dt>For Local files only</dt> + + <dd>Local execution scripts will only be executed if the + script to be executed resides on the local machine, and is + referenced by a URL that begins with + <em>file://localhost</em></dd> + + <dt>Always on</dt> + + <dd>All local execution scripts will be executed</dd> + </dl> + </dd> + + <dd>If the users options permit the script to be executed Lynx + will spawn a shell and run the script. If the script cannot be + executed Lynx will show the script within the Lynx window and + inform the user that the script is not allowed to be executed + and will ask the user to check his/her options.</dd> + + <dt>FTP sort criteria</dt> + + <dd>This option allows you to specify how files will be sorted + within FTP listings. The current options include "<code>By + Filename</code>", "<code>By Size</code>", "<code>By + Type</code>", and "<code>By Date</code>".</dd> + + <dt>HTML error recovery</dt> + + <dd>Select the <a href= + "keystrokes/option_help.html#tagsoup">recovery mode</a> used by + Lynx.</dd> + + <dt>Invalid-Cookie Prompting</dt> + + <dd>This allows you to tell how to handle invalid cookies: + <em>prompt normally</em> to prompt for each cookie, <em>force + yes-response</em> to reply "yes" to each prompt, <em>force + no-response</em> to reply "no" to each prompt.</dd> + + <dt>Keypad mode</dt> + + <dd>This option gives the choice among navigating with the + arrow keys, or having every link numbered so that the links may + be selected or made current by numbers as well as using the + arrow keys, or having every link as well as every form field + numbered so that they can be selected or sought by numbers. See + the<br> + <a href="keystrokes/follow_help.html">Follow link + (or page) number:</a> and<br> + <a href= + "keystrokes/follow_help.html#select-option">Select option (or + page) number:</a><br> + help for more information.</dd> + + <dt>Line edit style</dt> + + <dd>This option allows you to set alternative key bindings for + the built-in line editor, if alternative line-edit bindings + have been compiled in. Otherwise, Lynx uses the <a href= + "keystrokes/edit_help.html">Default Binding</a>.</dd> + + <dt>Local directory sort criteria</dt> + + <dd> + This applies to directory editing. Files and directories can + be presented in the following ways: + + <dl> + <dt>Mixed style</dt> + + <dd>Files and directories are listed together in + alphabetical order.</dd> + + <dt>Directories first</dt> + + <dd>Files and directories are separated into two + alphabetical lists. Directories are listed first.</dd> + + <dt>Files first</dt> + + <dd>Files and directories are separated into two + alphabetical lists. Files are listed first.</dd> + </dl> + </dd> + + <dt>Local directory sort order</dt> + + <dd> + The Options Form also allows you to sort by the file + attributes. + + <dl> + <dt>By name</dt> + + <dd>by filename (the default)</dd> + + <dt>By size</dt> + + <dd>by file size, in descending order</dd> + + <dt>By date</dt> + + <dd>by file modification time, in descending order</dd> + + <dt>By mode</dt> + + <dd>by file protection</dd> + + <dt>By type</dt> + + <dd>by filename suffix, e.g., the text beginning with + '.'</dd> + + <dt>By user</dt> + + <dd>by file owner's user-id</dd> + + <dt>By group</dt> + + <dd>by file owner's group-id</dd> + </dl> + </dd> + + <dt>Multi-bookmarks</dt> + + <dd>Lynx supports a default bookmark file, and up to 26 total + bookmark files (see below). When multi-bookmarks is OFF, the + default bookmark file is used for the '<em>v</em>'iew bookmarks + and '<em>a</em>'dd bookmark link commands. If multi-bookmark + support is available in your account, the setting can be + changed to STANDARD or ADVANCED. In STANDARD mode, a menu of + available bookmarks always is invoked when you seek to view a + bookmark file or add a link, and you select the bookmark file + by its letter token (see <em>Bookmark file</em>, below) in that + menu. In ADVANCED mode, you instead are prompted for the letter + of the desired bookmark file, but can enter '<em>=</em>' to + invoke the STANDARD selection menu, or <em>RETURN</em> for the + default bookmark file.</dd> + + <dt>Password for anonymous ftp</dt> + + <dd>If this is blank, Lynx will use your personal mail address + as the anonymous ftp password. Though that is the convention, + some users prefer to use some other string which provides less + information. If the given value lacks a "@", Lynx also will use + your computer's hostname as part of the password. If both this + field and the personal mail address are blank, Lynx will use + your $USER environment variable, or "WWWuser" if even the + environment variable is unset.</dd> + + <dt>Pause when showing message</dt> + + <dd>If set to "off", this overrides the INFOSECS setting in + lynx.cfg, to eliminate pauses when displaying informational + messages, like the "-nopause" command line option.</dd> + + <dt>Personal mail address</dt> + + <dd>This mail address will be used to help you send files to + yourself and will be included as the From: address in any mail + or comments that you send. It will also be sent as the From: + field in HTTP or HTTPS requests if inclusion of that header has + been enabled via the NO_FROM_HEADER definition in <a href= + "#lynx.cfg">lynx.cfg</a> (the compilation default is not to + send the header), or via the <em>-from</em> command line + toggle.</dd> + + <dt>Personal mail name</dt> + + <dd>This mail name will be included as the "X-Personal_Name" + field in any mail or comments that you send if that header has + not been disabled via the NO_ANONYMOUS_EMAIL definition in + <a href="#lynx.cfg">lynx.cfg</a>.</dd> + + <dt>Popups for select fields</dt> + + <dd>Lynx normally uses a popup window for the OPTIONs in form + SELECT fields when the field does not have the MULTIPLE + attribute specified, and thus only one OPTION can be selected. + The use of popup windows can be disabled by changing this + setting to OFF, in which case the OPTIONs will be rendered as a + list of radio buttons. Note that if the SELECT field does have + the MULTIPLE attribute specified, the OPTIONs always are + rendered as a list of checkboxes.</dd> + + <dt>Preferred document language</dt> + + <dd>The language you prefer if multi-language files are + available from servers. Use RFC 1766 abbreviations, e.g., en + for English, fr for French, etc. Can be a comma-separated list, + which may be interpreted by servers as descending order of + preferences. You can also make your order of preference + explicit by using q factors as defined by the HTTP protocol, + for servers which understand it, for example: + da, en-gb;q=0.8, en;q=0.7</dd> + + <dt>Preferred document charset</dt> + + <dd>The character set you prefer if sets in addition to + ISO-8859-1 and US-ASCII are available from servers. Use MIME + notation (e.g., ISO-8859-2) and do not include ISO-8859-1 or + US-ASCII, since those values are always assumed by default. Can + be a comma-separated list, which may be interpreted by servers + as descending order of preferences. You can also make your + order of preference explicit by using q factors as defined by + the HTTP protocol, for servers which understand it, for + example: iso-8859-5, utf-8;q=0.8</dd> + + <dt>Preferred encoding</dt> + + <dd>When doing a GET, lynx tells what types of compressed data + it can decompress (the "Accept-Encoding:" string). This is + determined by compiled-in support for decompression or external + decompression programs. Use this option to select none, one or + all of the supported decompression types.</dd> + + <dt>Preferred media type</dt> + + <dd> + When doing a GET, lynx lists the MIME types which it knows + how to present (the "Accept:" string). Depending on your + system configuration, the mime.types or other data given by + the GLOBAL_EXTENSION_MAP may include many entries that lynx + really does not handle. Use this option to select one of the + built-in subsets of the MIME types that lynx could list in + the Accept. + + <dl> + <dt>Accept lynx's internal types</dt> + + <dd>list only the types that are compiled into lynx.</dd> + + <dt>Also accept lynx.cfg's types</dt> + + <dd>lists types defined in lynx.cfg, e.g., the VIEWER and + Cern RULE or RULESFILE settings.</dd> + + <dt>Also accept user's types</dt> + + <dd>lists types from the PERSONAL_EXTENSION_MAP setting in + lynx.cfg</dd> + + <dt>Also accept system's types</dt> + + <dd>lists types from the GLOBAL_EXTENSION_MAP setting in + lynx.cfg</dd> + + <dt>Accept all types</dt> + + <dd>adds the types that are in lynx's built-in tables for + external programs that may be used to present a + document.</dd> + </dl> + </dd> + + <dt>Raw 8-bit or CJK Mode</dt> + + <dd>Whether 8-bit characters are assumed to correspond with the + display character set and therefore are processed without + translation via the chartrans conversion tables. Should be ON + by default when the display character set is one of the Asian + (CJK) sets and the 8-bit characters are Kanji multibytes. + Should be OFF for the other display character sets, but can be + turned ON when the document's charset is unknown (e.g., is not + ISO-8859-1 and no charset parameter was specified in a reply + header from an HTTP server to indicate what it is) but you know + by some means that you have the matching display character set + selected. Should be OFF when an Asian (CJK) set is selected but + the document is ISO-8859-1 or another 'assumed document + character set'. The setting also can be toggled via the + RAW_TOGGLE command, normally mapped to '<em>@</em>', and at + startup via the <em>-raw</em> switch.</dd> + + <dt>Send User-Agent header Controls whether the user-agent + string will be sent.</dt> + + <dt>Session file</dt> + + <dd>Define the file name where lynx will store user sessions. + This setting is used only when <em>Auto Session</em> is + enabled.</dd> + + <dt>Show color</dt> + + <dd>This option will be present if color support is available. + If set to ON or ALWAYS, color mode will be forced on if + possible. If (n)curses color support is available but cannot be + used for the current terminal type, selecting ON is rejected + with a message. If set to OFF or NEVER, color mode will be + turned off.<br> + ALWAYS and NEVER are not offered in anonymous accounts. If + saved to a <em>.lynxrc</em> file in non-anonymous accounts, + ALWAYS will cause Lynx to set color mode on at startup if + supported. If Lynx is built with the slang library, this is + equivalent to having included the <em>-color</em> command line + switch or having the <em>COLORTERM</em> environment variable + set. If color support is provided by curses or ncurses, this is + equivalent to the default behavior of using color when the + terminal type supports it. If (n)curses color support is + available but cannot be used for the current terminal type, the + preference can still be saved but will have no effect.<br> + A saved value of NEVER will cause Lynx to assume a monochrome + terminal at startup. It is similar to the <em>-nocolor</em> + switch, but (when the slang library is used) can be overridden + with the <em>-color</em> switch.<br> + If the setting is OFF or ON when the current options are saved + to a <em>.lynxrc</em> file, the default startup behavior is + retained, such that color mode will be turned on at startup + only if the terminal info indicates that you have a + color-capable terminal, or (when the slang library is used) if + forced on via the <em>-color</em> switch or <em>COLORTERM</em> + variable. This default behavior always is used in anonymous + accounts, or if the <em>option_save</em> restriction is set + explicitly. If for any reason the startup color mode is + incorrect for your terminal, set it appropriately on or off via + this option.</dd> + + <dt>Show cursor</dt> + + <dd>Lynx normally hides the cursor by positioning it to the + right and if possible the very bottom of the screen, so that + the current link or OPTION is indicated solely by its + highlighting or color. If show cursor is set to ON, the cursor + will be positioned at the left of the current link or OPTION. + This is helpful when Lynx is being used with a speech or + braille interface. It also is useful for sighted users when the + terminal cannot distinguish the character attributes used to + distinguish the current link or OPTION from the others in the + screen display.</dd> + + <dt>Show dot files</dt> + + <dd>If display/creation of hidden (dot) files/directories is + enabled, you can turn the feature on or off via this + setting.</dd> + + <dt>Show images</dt> + + <dd> + This allows you to select the way in which Lynx shows image + links. These are the available selections: + + <ul> + <li><em>ignore</em> to suppress the links altogether,</li> + + <li><em>as labels</em> to show the descriptive text for the + link</li> + + <li><em>as links</em>, which allows you to use an external + viewer</li> + </ul> + </dd> + + <dt>Show scrollbar</dt> + + <dd>This allows you to enable (show) or disable (hide) the + scrollbar on the right-margin of the display. This feature is + available with ncurses or slang libraries.</dd> + + <dt>Show transfer rate</dt> + + <dd> + This allows you to select the way in which Lynx shows its + progress in downloading large pages. It displays its progress + in the status line. These are the available selections: + + <ul> + <li>Do not show rate</li> + + <li>Local directory sort order</li> + + <li>Show dot files</li> + + <li>Execution links</li> + + <li>Pause when showing message</li> + + <li>Show transfer rate</li> + </ul> + </dd> + + <dt>SSL Prompting</dt> + + <dd>This allows you to tell how to handle errors detected in + SSL connections <em>prompt normally</em> to prompt for each + cookie, <em>force yes-response</em> to reply "yes" to each + prompt, <em>force no-response</em> to reply "no" to each + prompt.</dd> + + <dt>Type of Search</dt> + + <dd>Searching type has two possible values: CASE INSENSITIVE + (default) and CASE SENSITIVE. The searching type effects + inter-document searches only, and determines whether searches + for words within documents will be done in a case-sensitive or + case-insensitive manner.</dd> + + <dt>Use HTML5 charset replacements</dt> + + <dd>This option allows lynx to treat pages with ISO-8859-1 + (Latin1) or ASCII encoding as if they were Windows 1252. That + allows a few punctuation characters to be shown.</dd> + + <dt>Use locale-based character set</dt> + + <dd>This option allows you to request lynx to obtain a MIME + name from the operating system which corresponds to your locale + setting. If successful, it overrides the normal setting of the + display character set.</dd> + + <dt>Underline links</dt> + + <dd>Use underline-attribute rather than bold for links.</dd> + + <dt>Use Passive FTP</dt> + + <dd>This allows you to change whether Lynx uses passive ftp + connections.</dd> + + <dt>User Agent header</dt> + + <dd>The header string which Lynx sends to HTTP servers to + indicate the User-Agent is displayed here. Changes may be + disallowed via the <em>-restrictions</em> switch. Otherwise, + the header can be changed temporarily to a string such as + <em>L_y_n_x/2.8.7</em> for access to sites which discriminate + against Lynx based on checks for the presence of "Lynx" in the + header. If the User-Agent header has been changed, it can be + restored to the built-in default value by deleting the modified + string in the Options Menu. Whenever the User-Agent header is + changed, the current document is reloaded, with the no-cache + flags set, on exit from the Options Menu. Changes of the header + are not saved in the RC file.</dd> + + <dd><em id="noteUA">NOTE:</em> Some sites may regard + misrepresenting the browser as fraudulent deception, or as + gaining unauthorized access, if it is used to circumvent + blocking that was intentionally put in place. Some browser + manufacturers may find the transmission of their product's name + objectionable. If you change the User-Agent string, it is your + responsibility. The Options Menu issues a reminder whenever the + header is changed to one which does not include "Lynx" or + "L_y_n_x".</dd> + + <dt>User Mode</dt> + + <dd> + There are three possible choices: Novice, Intermediate, and + Advanced. + + <dl> + <dt>Novice</dt> + + <dd>In Novice mode two lines of help are displayed at the + bottom of the screen.</dd> + + <dt>Intermediate</dt> + + <dd>Intermediate mode turns off the help lines.</dd> + + <dt>Advanced</dt> + + <dd>Advanced mode displays the URL of the currently + selected link at the bottom of the screen.</dd> + </dl> + </dd> + + <dt>Verbose Images</dt> + + <dd>Controls whether or not Lynx replaces the [LINK], [INLINE] + and [IMAGE] comments (for images without ALT) with filenames of + these images. This is extremely useful because now we can + determine immediately what images are just decorations + (button.gif, line.gif) and what images are important. This + setting can also be toggled on startup via the + <em>-verbose</em> switch.</dd> + + <dt>VI keys</dt> + + <dd> + If set to ON then the lowercase h, j, k, and l keys will be + mapped to left, down, up, and right arrow, respectively. The + uppercase H, J, K, and L keys remain mapped to their + configured bindings (normally HELP, JUMP, KEYMAP, and LIST, + respectively). + + <p>Note: this has no effect on the line-editor's key + bindings.</p> + </dd> + + <dt>Visited Pages</dt> + + <dd> + Enable several different views of the visited links: + + <dl> + <dt>By First Visit</dt> + + <dt>By First Visit Reversed</dt> + + <dt>As Visit Tree</dt> + + <dt>By Last Visit</dt> + + <dt>By Last Visit Reversed</dt> + </dl> + </dd> + + <dt>X Display</dt> + + <dd>This option is only relevant to X Window users. The DISPLAY + (Unix) or DECW$DISPLAY (VMS) variable is picked up + automatically from the environment if it has been previously + set.</dd> + </dl> + + <p>[<a href="#ToC-InteractiveOptions">ToC</a>]</p> + + <h2 id="id-Mail"><a name="Mail" id="Mail"><em>Comments and + mailto: links</em></a></h2> + + <p>At any time while viewing documents within Lynx, you may use + the '<em>c</em>' command to send a mail message to the owner of + the current document if the author of the document has specified + ownership. (Note to authors: if you want to assign the ownership + to your document, you need to add into HEAD section a LINK + element with appropriate value for REV attribute. Two values are + recognized: <em>owner</em> and <em>made</em> (these are case + insensitive). For example,</p> + <pre> +<HEAD> + … + <LINK REV="made" HREF="mailto:user@somedomain.com"> + … +</HEAD> +</pre>You may also add a TITLE attribute with, for example, the +name of your page) If no ownership is specified then comments are +disabled. Certain links called <a href= +"lynx_url_support.html#mailto_url">mailto:</a> links will also +allow you to send mail to other people. Using the mail features +within Lynx is straightforward. + + <p>Once you have decided to send a comment or have selected a + <em>mailto:</em> link a new screen will appear showing you to + whom you are sending the message. Lynx will ask for your name, + your e-mail address, and the subject of the message. If you have + filled in the "personal mail address" field in the <em>Options + Menu</em>, your e-mail address will be filled in automatically. + After entering the above information, if you have an editor + defined in the <em>Options Menu</em> and you are not an anonymous + user then your specified editor will be spawned for you so that + you can enter your message. If you do not have an editor defined + or you are an anonymous user, a simple line mode input scheme + will allow you to enter your message.</p> + + <p>To finish sending the message, exit your spawned editor or, if + you are using the simple line mode input scheme, type a + '<em>.</em>' (period) on a line by itself. You will be asked a + final time whether to send the message. If you press + '<em>y</em>', you will be prompted whether to append your + signature file if one was defined in <a href= + "#lynx.cfg">lynx.cfg</a> and is accessible, and then the message + will be sent, whereas if you press '<em>n</em>' the message will + be deleted. Entering Control-G in response to any prompts also + will cancel the mailing.</p> + + <p>[<a href="#ToC-Mail">ToC</a>]</p> + + <h2 id="id-News"><a name="News" id="News"><em>USENET News + posting</em></a></h2> + + <p>While reading <a href= + "http://www.w3.org/LineMode/User/AboutNewsServers.html">news</a> + articles with Lynx you should see a link that says <em>Reply to: + user@host</em> and, if the nntp server from which you received + the article supports posting from your site, a link that says + <em>Followup to: newsgroup(s)</em></p> + + <dl> + <dt>Reply to user@host</dt> + + <dd>user@host will correspond to the mail address of the person + who posted the news article. Selecting the link will allow you + to send a message to the person who wrote the message you are + currently viewing. You will be given the option of including + the original message in your reply.</dd> + + <dt>Followup to newsgroup(s)</dt> + + <dd>Selecting this link will allow you to post back to the + newsgroup that you are currently reading and any newsgroups to + which the message was cross-posted. You will be given the + option of including the original message in your reply. Once + you have typed in your message, you will be asked for + confirmation of whether to proceed with the posting, and + whether to append your signature file if one was defined in + <a href="#lynx.cfg">lynx.cfg</a> and is accessible. See + <a href="lynx_url_support.html">Supported URLs</a> for more + information about the URL schemes for posting or sending + followups (replies) to nntp servers with Lynx. [<a href= + "#ToC-News">ToC</a>]</dd> + </dl>See also <a href= + "http://www.w3.org/Protocols/rfc977/rfc977">RFC 977</a>. + + <h2 id="id-Bookmarks"><a name="Bookmarks" id="Bookmarks"><em>Lynx + bookmarks</em></a></h2> + + <p>Bookmarks are entries in your <em>bookmark file</em>, which + record the URL of a document you may want to return to easily, + with a name of your choice to identify the document. To use + bookmarks you must first have specified a name for your bookmark + file in <a href="#lynx.cfg">lynx.cfg</a> or via the <em>Options + Menu</em>.</p> + + <p>To save a bookmark to the document you wish to place in the + bookmark file press the '<em>a</em>' key and you will be + asked:</p> + + <blockquote> + Save D)ocument or L)ink to bookmark file or C)ancel? (d,l,c): + </blockquote>Answer '<em>d</em>' to save a link to the document + you are currently viewing or '<em>l</em>' to save the link that + is currently selected on the page. Selecting '<em>c</em>' will + cancel without saving anything to your bookmark file. + + <p>A bookmark file will be created in conjunction with acting on + the '<em>a</em>'dd command if it does not already exist. + Otherwise, the link will be added to the bottom of the + pre-existing bookmark file. You must have created a bookmark file + via the '<em>a</em>'dd command before you can view it.</p> + + <p>Use the '<em>v</em>' command to view the list of bookmarks you + have saved. While viewing the bookmark list you may select a + bookmark as you would any other link.</p> + + <p>You can remove a link from the bookmark list by pressing the + '<em>r</em>' key when positioned on that link. You also can use a + standard text editor (e.g., via the '<em>e</em>'dit command while + viewing a bookmark file, if an external editor has been defined + via the <em>Options menu</em>) to delete or re-order links in the + bookmark file, or to modify a link name by editing the content of + the <em>A</em>nchor element for the link, but you should not + change the format within the line for the link, consisting of an + <em>LI</em> element followed by the <em>A</em>nchor element, nor + cause the line to become wrapped to a second line. You similarly + can change the link destination by editing the double-quoted + value for the <em>HREF</em> attribute in the <em>A</em>nchor + start tag, but you should not otherwise change the spacing within + the start tag, nor add other attributes. You can add a new link + while editing by copying an existing line for a link, to ensure + the proper format, and then modifying its <em>HREF</em> value and + <em>A</em>nchor content, but you should not add any other HTML + markup to the bookmark file. If the format and spacing (other + than the <em>A</em>nchor content or <em>HREF</em> value) within + lines is changed or other HTML markup is added, the + '<em>a</em>'dd and '<em>r</em>'emove commands may not work + properly.</p> + + <p>When multi-bookmarks (see <a href= + "#InteractiveOptions">Options Menu</a>) is OFF, you will always + view or add links to the default bookmark file. When it is + STANDARD, a menu of up to 26 bookmark files will be invoked, and + you select the bookmark file by entering its letter token. When + it is ADVANCED, you will be prompted for the letter token, but + can enter '<em>=</em>' to invoke the STANDARD selection menu, or + <em>RETURN</em> for the default bookmark file. [<a href= + "#ToC-Bookmarks">ToC</a>]</p> + + <h2 id="id-Jumps"><a name="Jumps" id="Jumps"><em>Jump + Command</em></a></h2> + + <p>Similar to the bookmarks file is the jumps file: for an + example, look in the <em>samples</em> subdirectory in the + distribution package. To use the jumps command, create a + <em>jumps file</em> with the same format as the sample file, but + containing your own URLs & short-cut names. Once you have + done that, typing '<em>j</em>' prompts you to enter a short-cut + name, which will take you straight to the URL associated with the + short-cut in the jumps file, much like using '<em>g</em>'. If you + want to check which short-cuts are available, type '<em>?</em>' + at the jump prompt for the full list.</p> + + <p>You can set up a jumps file which makes Lynx prompt for + parameters, e.g., as part of a search. Do this by putting a "%s" + marker in the URL at each point where you want Lynx to fill in + text. When you activate the corresponding jump, Lynx will prompt + you for the parameters, one by one.</p> + + <p>All jump short-cuts you have entered are saved in a circular + buffer in the same way as with '<em>g</em>' and '<em>/</em>' + (search):<br> + previous entries can be retrieved with <em>up-arrow</em> or + <em>down-arrow</em>.</p> + + <p>The jumps feature is especially useful for system + administrators who have unsophisticated users to care for, but + ordinary Lynx users who have a number of URLs they regularly + visit while browsing may find using the jumps command speeds + their movements.</p> + + <p>For more advice how to set up the jumps command on your system + and how to define short-cut names, read <a href= + "#lynx.cfg">lynx.cfg</a> .</p> + + <p>[<a href="#ToC-Jumps">ToC</a>]</p> + + <h2 id="id-DirEd"><a name="DirEd" id="DirEd"><em>Directory + Editing</em></a></h2> + + <p>Lynx offers extended DIRED support on Unix (on VMS the more + powerful CSwing program is recommended for character cell + terminals, and can be offered via Lynx as a jump shortcut or + execution link). When a local directory is accessed using a URL + of the form <em>file://localhost/path/</em>, a new set of + commands is available. With DIRED support you can create, edit, + delete, copy, and move files on your local system. The commands + available in DIRED mode are</p> + + <dl> + <dt><code>C)reate</code></dt> + + <dd>Type '<em>c</em>' to create a new file. New file will be + empty.</dd> + + <dt><code>D)ownload</code></dt> + + <dd>Type '<em>d</em>' to download using one of the pre-defined + options.</dd> + + <dt><code>E)dit</code></dt> + + <dd>Type '<em>e</em>' to spawn the editor defined in + <em>Options Menu</em> and load a selected file for + editing.</dd> + + <dt><code>F)ull Menu</code></dt> + + <dd>Type '<em>f</em>' to show full menu of options available + for selection. Menu may vary according to type of file selected + and compression facilities available. + <!-- List of full menu options --></dd> + + <dt><code>M)odify</code></dt> + + <dd>Type '<em>m</em>' to modify the name or location of file. + Then type '<em>n</em>' to rename the file or '<em>l</em>' to + move the file to a different location.</dd> + + <dt><code>R)emove</code></dt> + + <dd>Type '<em>r</em>' to remove the selected file or + directory.</dd> + + <dt><code>T)ag</code></dt> + + <dd>Type '<em>t</em>' to tag highlighted file. Further + operations will be performed on tagged files instead of + highlighted ones.</dd> + + <dt><code>U)pload</code></dt> + + <dd>Type '<em>u</em>' to upload a file to the present + directory. An uploading method must have been pre-defined in + <a href="#lynx.cfg">lynx.cfg</a> .</dd> + </dl> + + <p>[<a href="#ToC-DirEd">ToC</a>]</p> + + <h2 id="id-ColorMouse"><a name="ColorMouse" id= + "ColorMouse"><em>Using Color & the Mouse</em></a></h2> + + <p>A limited range of colors & mouse commands are available, + if the user chooses: see <em>lynx.cfg</em> for details. [<a href= + "#ToC-ColorMouse">ToC</a>]</p> + + <h2 id="id-MiscKeys"><a name="MiscKeys" id= + "MiscKeys"><em>Scrolling and Other useful commands</em></a></h2> + + <p>A summary of all the keystroke commands and their key bindings + can be invoked via the KEYMAP command, normally mapped to + '<em>k</em>' and '<em>K</em>'. The following describes some of + the most commonly used commands.</p> + + <dl> + <dt><em>^A</em></dt> + + <dd><em>Control-A</em> jumps you to the beginning of the + current document. It is a synonym for the Keypad <em>Home</em> + key, and can be used also when <em>Links are numbered</em> mode + is on. The <em>Find</em> Function key also is a synonym, and + ideally the latter has been mapped to the Function key labeled + <em>Home</em> if you are using an IBM Enhanced Keyboard.</dd> + + <dt><em>^E</em></dt> + + <dd><em>Control-E</em> jumps you to the end of the current + document. It is a synonym for the Keypad <em>End</em> key, and + can be used also when <em>Links are numbered</em> mode is on. + The <em>Select</em> Function key also is a synonym, and ideally + the latter has been mapped to the Function key labeled + <em>End</em> if you are using an IBM Enhanced Keyboard.</dd> + + <dt><em>^B</em></dt> + + <dd><em>Control-B</em> normally jumps you to the previous page + of the current document, and thus is a synonym for the Keypad + and Function <em>Page-Up</em> keys. However, <em>Control-B</em> + acts as <em>right-arrow</em> when emacs-like key movement is + enabled (see <a href="#InteractiveOptions">Lynx Options + Menu</a>).</dd> + + <dt><em>^F</em></dt> + + <dd><em>Control-F</em> normally jumps you to the next page of + the current document, and thus is a synonym for the Keypad and + Function <em>Page-Down</em> keys. However, <em>Control-F</em> + becomes <em>right-arrow</em> when emacs-like key movement is + enabled.</dd> + + <dt><em>^N</em></dt> + + <dd><em>Control-N</em> normally jumps you forward two lines in + the current document. The <em>Remove</em> Function key (labeled + <em>Delete</em> on IBM Enhanced keyboards, and distinct from + their <em>Backspace</em> key) is a synonym. <em>Control-N</em> + becomes <em>down-arrow</em> when emacs-like key movement is + enabled.</dd> + + <dt><em>^P</em></dt> + + <dd><em>Control-P</em> normally jumps you back two lines in the + current document. The <em>Insert</em> Function key is a + synonym. <em>Control-P</em> becomes <em>up-arrow</em> when + emacs-like key movement is enabled.</dd> + + <dt><em>)</em></dt> + + <dd>The <em>)</em> command jumps you forward half a page in the + current document.</dd> + + <dt><em>(</em></dt> + + <dd>The <em>(</em> command jumps you back half a page in the + current document.</dd> + + <dt><em>#</em></dt> + + <dd>The '<em>#</em>' command jumps you to the pseudo Toolbar or + Banner if present in the current document. Use + <em>left-arrow</em> to return from there to your previous + position in the document.</dd> + + <dt><em>!</em></dt> + + <dd>When '<em>!</em>' is pressed your default shell will be + spawned. When you quit or exit the shell you will return to + Lynx (usually <em>exit</em> under Unix and <em>logout</em> + under VMS). This command is usually disabled for anonymous + users. On VMS, '<em>$</em>' normally is a synonym. On Win32, + this has no effect [???].</dd> + + <dt><em>g</em></dt> + + <dd>The '<em>g</em>' command allows any URL to be viewed. + Pressing the '<em>g</em>' command will bring up a prompt asking + for a URL. Type in the URL that you wish to view. All + previously entered goto URLs are saved in a circular buffer, + and can be accessed at the prompt by pressing the + <em>up-arrow</em> or <em>down-arrow</em> keys.</dd> + + <dt><em>G</em></dt> + + <dd>The '<em>G</em>' command allows you to edit the URL of the + current document and then use that as a goto URL. Pressing the + '<em>G</em>' command will bring up a prompt asking you to edit + the current document's URL. If you do not modify it, or + completely delete it, or enter Control-G, the command will be + cancelled. If the current document has POST content associated + with it, an Alert will be issued. If you do edit that URL, and + it does not simply involve a fragment change (for seeking a + position in the current document), the modified URL will be + submitted with method GET and no POST content. If a + modification of the current document's URL results in a + submission, that modified URL will be entered into the circular + buffer for goto URLs, and can be accessed for further + modification via the '<em>g</em>' command.</dd> + + <dt><em>E</em></dt> + + <dd>The '<em>E</em>' command allows you to edit the URL (or + ACTION) of the current link and then use that as a goto URL. + Pressing the '<em>E</em>' command will bring up a prompt asking + you to edit the current link's URL. If you do not modify it, or + completely delete it, or enter Control-G, the command will be + cancelled. Otherwise, the request for the 'E'dited URL will be + sent with method GET, and will be entered into the circular + buffer for goto URLs so that it can be accessed for further + modification via the '<em>g</em>' command. Note that lower case + 'e' invokes the external editor for the current document.</dd> + + <dt><em>=</em></dt> + + <dd>The '<em>=</em>' command shows information about the + current document and the currently selected link if there is + one. The number of lines in the file, URL, title, owner, and + type are shown.</dd> + + <dt><em>^T</em></dt> + + <dd><em>Control-T</em> toggles Lynx trace mode on and off. This + is useful for diagnosing bad html. If you get a <em>Bad + HTML</em> statusline message when loading a document, enter + <em>Control-T</em> and then <em>Control-R</em> to reload the + document in trace mode. You may then examine the <em>Lynx Trace + Log</em> file with the <em>;</em> command if enabled (see + below), watch out especially for lines marked with a number of + asterisks '<code>*****</code>'. You also can submit the + document for validation via links in the online help menu. If + you are able to diagnose the problem, send a message about it + to the document's author.</dd> + + <dt><em>;</em></dt> + + <dd>The <em>;</em> command shows the <em>Lynx Trace Log</em> + (<em>Lynx.trace</em> in the home directory) if one has been + started for the current session. If a log has not been started, + any trace messages will be sent to the screen (and will disturb + the normal display) unless the system supports piping and that + was used to redirect stderr messages to a file. The log is + started when Lynx trace mode is turned on via the + <em>-trace</em> command line switch, or via the + <em>Control-T</em> toggle, if Lynx has been compiled to log the + trace and other stderr messages by default. If not, ability to + create a log can be toggled on with the <em>-tlog</em> switch. + Note that this ability is probably disabled in anonymous or + validation accounts.</dd> + + <dt><a name="asterisk-key" id= + "asterisk-key"><em>*</em></a></dt> + + <dd>The '<em>*</em>' command toggles image_links mode on and + off. When on, links will be created for all images, including + inline images. If you have an image viewer mapped to the + image's MIME type, you can activate such links to view an + inline image. You should normally have this mode toggled + off.</dd> + + <dt><em>@</em></dt> + + <dd>The '<em>@</em>' command toggles raw 8-bit or CJK mode on + and off. When on, the charset is assumed to match the selected + character set and 8-bit characters are not reverse translated + with respect to the ISO-8859-1 conversion tables.</dd> + + <dt><a name="lbracket-key" id= + "lbracket-key"><em>[</em></a></dt> + + <dd>The '<em>[</em>' command toggles pseudo_inlines mode on and + off. When on, inline images which have no ALT string specified + will have an <em>[INLINE]</em> pseudo-ALT string inserted in + the Lynx display. When off, they will be treated as having + ALT="" (i.e., they'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.</dd> + + <dt><em>]</em></dt> + + <dd>The '<em>]</em>' command is used to send HEAD requests for + the current document or link. It applies only to documents or + links (or form submit buttons) of http servers. A statusline + message will notify you if the context for this command was + inappropriate. The HEAD requests always are sent to the http + server, i.e., Lynx does not retrieve any previous server + replies from its cache. Note that for form submissions, http + servers vary in whether they'll treat HEAD requests as valid + and return the CGI script's headers, or treat it as invalid and + return an error message.</dd> + + <dt><em>^K</em></dt> + + <dd><em>Control-K</em> invokes the <a href= + "keystrokes/cookie_help.html">Cookie Jar Page</a> if it + contains cookies.</dd> + + <dt><em>^X</em></dt> + + <dd><em>Control-X</em> invokes the <a href="#Cache">Cache Jar + Page</a> if it contains cached documents.</dd> + + <dt><em>z</em></dt> + + <dd>Lynx supports completely interruptible I/O processes. Press + the '<em>z</em>' key at any time during a connect or transfer + process and the process will be halted. If any data was + transferred before the interrupt, it will be displayed.</dd> + + <dt><em>numbers</em></dt> + + <dd>Lynx offers other, advanced navigation features when + numbers are used to invoke the <a href= + "keystrokes/follow_help.html">Follow Link (or goto link or + page) number:</a> or <a href= + "keystrokes/follow_help.html#select-option">Select Pop-up + Option Number:</a> prompts.</dd> + </dl> + + <p>[<a href="#ToC-MiscKeys">ToC</a>]</p> + + <h2 id="id-Forms"><a name="Forms" id="Forms"><em>Lynx and HTML + Forms</em></a></h2> + + <p>This section describes the Lynx Forms Interface. HTML gives + document providers the ability to create on-line forms which may + be filled out when the document is viewed. When a form is + submitted the information on the form can be used to search a + database or complete a survey.</p> + + <p>An HTML Form provides for the use of buttons to perform an + action (such as <em>submit</em>), checkboxes, radio buttons or + popups to select options from a list, and fields for entering + text.</p> + + <dl> + <dt>Buttons:</dt> + + <dd>Buttons are displayed in the same way that Lynx displays + links in a document. To "push" the button press the + <em>right-arrow</em> or <em>Return</em> key. If it is a form + submission button, you also can use the NOCACHE ('<em>x</em>') + or DOWNLOAD ('<em>d</em>') keystroke commands to "push" the + button (see below).</dd> + + <dt>Checkboxes and Radio buttons</dt> + + <dd>Checkboxes are displayed as square brackets: <em>[ ]</em> + and radio buttons are displayed as parenthesis: <em>( )</em>. + When a box is checked or a button selected, an <em>x</em> + appears in the brackets: <em>[x]</em> or an asterisk appears + within the parenthesis: <em>(*)</em>. To check a box or select + a radio button press the <em>right-arrow</em> or + <em>Return</em> key.</dd> + + <dt>Selection Fields</dt> + + <dd>Selection fields are displayed as brackets with the default + option displayed between them: <em>[default__]</em>. To select + an option press the <em>right-arrow</em> or <em>Return</em> + key. A box with a border of asterisks (or line-drawing + characters) will pop up with the list of possible options + listed within the box. Use the <em>up-arrow</em>, + <em>down-arrow</em>, <em>page-up</em>, <em>page-down</em>, and + other navigation keys to move the cursor among options, and the + <em>right-arrow</em> or <em>Return</em> key to select an + option. You also can use the '<em>/</em>' and '<em>n</em>'ext + <a href="#Search">searching</a> commands for navigating to + options which contain particular strings. <em>NOTE</em> that + the popup menu feature can be disabled via compilation and/or + configuration options, or via the <a href= + "#InteractiveOptions">Options Menu</a>, in which case the + selection field options will be converted to a list of radio + buttons. The default setting for use of popups or radio button + lists can be toggled via the <em>-popup</em> command line + switch.</dd> + + <dt>Text Entry Fields</dt> + + <dd> + Text entry (INPUT) fields are displayed as a row of + underscores the length of the entry field: <em>_______</em>. + You may enter text directly by typing at the keyboard. Use + the <a href="keystrokes/edit_help.html">Line Editor</a> keys + to correct errors. If you try to input more text than the + field can hold, the line editor will not accept the + additional characters. If you fill a text field the cursor + will not move off the field but remain at the last field + position. Use the <em>up-arrow</em>, and <em>down-arrow</em>, + <em>TAB</em> or <em>Return</em> keys to move up, or down from + the text entry field. NOTE, however, that <em>Return</em> + also will <a href="#submit">submit</a> the form if the text + entry field is the only non-hidden field in the form. If + <a name="tna" id="tna">"Textfields Need Activation"</a> mode + is turned on (with the <kbd>-tna</kbd> command-line option or + in <a href="#lynx.cfg">lynx.cfg</a>), then text entry fields + do not become active immediately upon being selected, as + normally. Keystrokes have their normal command meaning unless + the Line Editor gets activated with <em>Return</em> or + <em>Right Arrow</em>. This mode can be used to avoid "getting + stuck" in input fields, especially by users who rarely fill + out forms. + + <p><a name="CtrlVNote" id="CtrlVNote">NOTE:</a> If you have a + text input field selected you will not have access to most of + the Lynx keystroke commands, because they are interpreted by + the <a href="keystrokes/edit_help.html">Line Editor</a> as + either text entries or editing commands. Select a button or + box when you want to use Lynx keystrokes; or prefix your + keystroke with <em>^V</em> to temporarily escape from line + editing.</p> + + <p>Some flavors of UNIX, shells & terminal settings + require that you enter <em>^V^Ve</em> in order to start the + external editor, as they also use <em>^V</em> as default + command-line quote key (called `lnext' in stty man pages and + `stty -a' output); to avoid this, you can put `stty lnext + undef' in your .cshrc file (or .profile or .bashrc, depending + on what shell you use), or invoke Lynx with a wrapper script, + e.g.</p> + + <p><code> #!/bin/sh<br> + stty lnext undef<br> + $HOME/bin/lynx "$@"<br> + stty lnext ^V<br> + exit</code></p> + + <p>NB when NOT in the Line Editor, <em>^V</em> is by default + bound to the command to switch between SortaSGML and TagSoup + HTML parsing (i.e., SWITCH_DTD). To avoid confusion, either + of these separate functions could be changed (mapped away) + with a KEYMAP directive in <em>lynx.cfg</em>. For + example,</p> + + <p> KEYMAP:^V:DO_NOTHING<br> + KEYMAP:#:SWITCH_DTD</p> + + <p>would map SWITCH_DTD away from <em>^V</em> to <em>#</em>, + while leaving its default Line Editor function as a command + escape in place. On the other hand,</p> + + <p> KEYMAP:^V::NOP:1<br> + KEYMAP:^_::LKCMD:1</p> + + <p>would move <em>^V</em>'s Line Editor binding as command + escape to <em>^_</em> for the first Line Edit style, letting + <em>^V</em> still act as SWITCH_DTD outside of text input + fields.</p> + </dd> + + <dt>TEXTAREA Fields</dt> + + <dd>TEXTAREA fields are for most purposes handled as if they + were a series of text entry (INPUT) fields for which successive + lines imply a newline at the end of the preceding line. You + enter text on each line to construct the overall message. Any + blank lines at the bottom of the TEXTAREA field will be + eliminated from the submission. The <em>up-arrow</em>, and + <em>down-arrow</em> or <em>Return</em> keys move you to the + preceding, or next line of the overall message, as for INPUT + fields. The <em>TAB</em> key will move you down beyond the + bottom of the TEXTAREA field, and <em>Back Tab</em> (if + available, e.g., as Shift-Tab, and correctly mapped in the + terminal description) will move backward to a link or field + before the TEXTAREA.</dd> + + <dt>Editing TEXTAREA Fields and Special TEXTAREA Functions</dt> + + <dd> + TEXTAREA fields can be edited using an external editor. The + statusline should tell you when this is possible and what key + to use, it might for example say + <pre> + <strong>(Textarea) Enter text. </strong>[ ..... ]<strong> (^Xe for editor).</strong> +</pre>An external editor has to be defined, for example in the +<a href="#InteractiveOptions">Options Menu</a>, before you can +start using this function. + + <p>A key to invoke external TEXTAREA editing is normally + provided by the <a href= + "keystrokes/edit_help.html">Line-Editor Key</a> Bindings. A + KEYMAP directive in <em>lynx.cfg</em> can also be used to + make a different key invoke external editing; it will then + normally be necessary to prefix that key with <em>^V</em> to + "escape" from line-editing. Two variants exist,<br> + KEYMAP:e:EDITTEXTAREA<br> + or<br> + KEYMAP:e:DWIMEDIT<br> + (the first is only functional for TEXTAREA editing, while the + second allows to use the same key for normal <a href= + "#FileEdit">file editing</a> <em>as long as both functions + don't conflict</em>).</p> + + <p>Please see the <a href="#CtrlVNote">note above</a> for + details about <em>^V</em> behavior.</p>You can also use two + other special TEXTAREA functions. Again, these are already + bound to key sequences in the <a href= + "keystrokes/edit_help.html#TASpecial">Line-Editor + Bindings</a>, by default <em>^Xg</em> and <em>^Xi</em>. You + can use different keys by adding KEYMAP bindings to your + <em>lynx.cfg</em> file, e.g. + + <p> KEYMAP:$:GROWTEXTAREA<br> + KEYMAP:#:INSERTFILE</p> + + <p>With these bindings, (in a TEXTAREA only) <em>^V$</em> + would add 5 lines to the TEXTAREA and <em>^V#</em> would + prompt for the name of an existing file to be inserted into + the TEXTAREA (above the cursorline). An automatic variation + of GROWTEXTAREA is normally compiled in, so that hitting + <em>Enter</em> with the cursor on the last line adds a new + line to the TEXTAREA, with the cursor on it.</p> + + <p>If you have some single keys (or control keys) to spare + that you do not need for their normal purposes, you can + dedicate those keys to invoke the special functions (without + requiring a prefix key). For example, to use the <em>^E</em> + key for the DWIMEDIT action, and the <em>Insert</em> key for + the INSERTFILE action, use<br> + KEYMAP:^E:DWIMEDIT:PASS<br> + KEYMAP:0x10C:INSERTFILE:PASS<br> + (see lynx.cfg for other keystroke codes to use).</p> + + <p>Note that the default bindings that use <em>^X</em> as a + prefix key <em>may</em> also work by substituting the + <kbd>Escape</kbd> key for ^X. If your keyboard has a modifier + (Meta) key that gets transmitted as an ESC prefix, for + example <kbd>Alt</kbd>, you can then even use <em>Alt-e</em> + instead of <em>^Xe</em>, <em>Alt-g</em> instead of + <em>^Xg</em>, and so on. But this does not work reliably + everywhere (it depends on the way Lynx is compiled, including + which libraries are used, and behavior of the connection and + terminal type).</p> + </dd> + </dl>In general, you can move around the form using the standard + Lynx navigation keys. The <em>up-arrow</em> and + <em>down-arrow</em> keys, respectively, select the previous or + next field, box, or button. The <em>TAB</em> key selects the next + field, box, or button. + + <p>To <a name="submit" id="submit"><em>submit</em></a> the form + press <em>right-arrow</em> or <em>Return</em> when positioned on + the form's submit button. If you've submitted the form previously + during the Lynx session, have not changed any of the form + content, and the METHOD was <em>GET</em>, Lynx will retrieve from + its cache what was returned from the previous submission. If you + wish to resubmit that form to the server with the same content as + previously, use the NOCACHE command ('<em>x</em>') when + positioned on the submit button. The <em>right-arrow</em> and + <em>Return</em> keys also will invoke a no-cache resubmission if + the reply from a form submission included a META element with a + no-cache Pragma or Cache-Control directive:<br></p> + <pre> + <em><META HTTP-EQUIV="Pragma" CONTENT="no-cache"></em> + <em><META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"></em> +</pre>or the server sent a "Pragma" or "Cache-Control" MIME header +with a no-cache directive. + + <p>You also can use the DOWNLOAD ('<em>d</em>') keystroke command + when positioned on a form submit button if you wish to download + the server's reply to the submission instead of having Lynx + render and display it.</p> + + <p>Forms which have <em>POST</em> as the METHOD, or a <a href= + "lynx_url_support.html#mailto_url">mailto:</a> URL as the ACTION, + are always resubmitted, even if the content has not changed, when + you activate the <em>submit</em> button. Lynx normally will not + resubmit a form which has <em>POST</em> as the METHOD if the + document returned by the form has links which you activated, and + then you go back via the PREV_DOC (<em>left-arrow</em>) command + or via the <a href="keystrokes/history_help.html">History + Page</a>. Lynx can be compiled so that it resubmits the form in + those cases as well, and the default can be changed via <a href= + "#lynx.cfg">lynx.cfg</a>, and toggled via the + <em>-resubmit_posts</em> command line switch.</p> + + <p>If the form has one <em>text entry</em> field and no other + fields except, possibly, hidden INPUT fields not included in the + display, then that field also serves as a <em>submit</em> button, + and pressing <em>right-arrow</em> or <em>Return</em> on that + field will invoke submission of the form. Be sure to use + <em>up-arrow</em>, <em>down-arrow</em> or <em>TAB</em> to move + off the text entry field, in such cases, if it is not your + intention to submit the form (or to retrieve what was returned + from an earlier submission if the content was not changed and the + METHOD was <em>GET</em>).</p> + + <p>Forms can have multiple <em>submit</em> buttons, if they have + been assigned NAMEs in the markup. In such cases, information + about which one of the buttons was used to submit the form is + included in the form content.</p> + + <p>Inlined images can be used as submit buttons in forms. If such + buttons are assigned NAMEs in the markup, for graphic clients + they can also serve as <a href="#USEMAP">image maps</a>, and the + x,y coordinates of the graphic client's cursor position in the + image when it was <em>clicked</em> are included in the form + content. Since Lynx cannot inline the image, and the user could + not have moved a cursor from the origin for the image, if no + alternatives are made available in the markup Lynx sends a 0,0 + coordinate pair in the form content. Document authors who use + images as submit buttons, but have at least some concern for text + clients and sight-challenged Webizens, should include VALUEs for + the buttons in such markup. Lynx will then display the string + assigned to the VALUE, as it would for a normal submit button. + Some document authors incorrectly use an ALT instead of VALUE + attribute for this purpose. Lynx "cooperates" by treating ALT as + a synonym for VALUE when present in an INPUT tag with + TYPE="image". If neither a VALUE nor an ALT attribute is present, + Lynx displays "[IMAGE]-Submit" as the string for such buttons. If + clickable images is set, the "[IMAGE]" portion of the string is a + link for the image, and the "Submit" portion is the button for + submitting the form. Otherwise, the entire string is treated as a + submit button. If a VALUE or ALT attribute is present and + clickable images is set, Lynx prepends "[IMAGE]" as a link for + the image, followed by '-' and then the attribute's value as the + displayed string for the submit button. Note that earlier + versions of Lynx would send a name=value pair instead of a 0,0 + coordinate pair if a TYPE="image" submit button was NAME-ed, had + a VALUE attribute in the INPUT tag, and was used to submit the + form. The script which analyzes the form content thus could be + made aware whether the submission was by a user with a graphic + client and had image loading turned on, or by a user who did not + see the image nor make a conscious choice within it. However, + requests that this be included in HTML specifications + consistently have fallen on deaf ears, and thus Lynx now "fakes" + a 0,0 coordinate pair whether or not a VALUE or ALT attribute is + present in the INPUT tag. Ideally, the script which analyzes the + submitted content will treat the 0,0 coordinate pair as an + indicator that the user did not see the image and make a + conscious choice within it.</p> + + <p>Forms can have <em>hidden</em> INPUT fields, which are not + displayed, but have NAMEs and VALUEs included in the content. + These often are used to keep track of information across a series + of related form submissions, but have the potential for including + information about the user that might be considered to represent + an invasion of privacy. NOTE, in this regard, that Lynx has + implemented the <a href="http://www.w3.org/Markup/html3/">HTML + 3.0</a> <em>DISABLED</em> attribute for <em>all</em> of its form + fields. These can be used to keep track of information across + submissions, and to cast it unmodifiable in the current form, but + keep the user aware that it will be included in the + submission.</p> + + <p>Forms most commonly are submitted to http servers with the + content encoded as + <em>ENCTYPE="application/x-www-form-urlencoded"</em> for analysis + by a script, and Lynx treats that as the default if no ENCTYPE is + specified in the FORM start tag. However, you can specify a + <a href="lynx_url_support.html#mailto_url">mailto</a> URL as the + form's ACTION to have the form content sent, instead, to an email + address. In such cases, you may wish to specify + <em>ENCTYPE="text/plain"</em> in the form markup, so that the + content will not be encoded, but remain readable as plain + text.</p> + + <p>Lynx also supports + <em>ENCTYPE="application/sgml-form-urlencoded"</em> for which all + reserved characters in the content will be hex escaped, as with + <em>application/x-www-form-urlencoded</em>, but semicolons + ('<em>;</em>') instead of ampersands ('<em>&</em>') will be + used as the separator for name=value pairs in the form content. + The use of semicolons is preferred for forms with the + <em>GET</em> METHOD, because the <em>GET</em> METHOD causes the + encoded form content to be appended as a <em>?searchpart</em> for + the form's ACTION, and if such URLs are used in + <em>text/html</em> documents or bookmark files without conversion + of the ampersands to SGML character references + (<em>&amp;</em> or <em>&#38;</em>), their being followed + by form field NAMEs which might correspond to SGML entities could + lead to corruption of the intended URL.</p> + + <p>NOTE, in this regard, that Lynx converts ampersands to + <em>&amp;</em> when creating bookmarks, and thus the bookmark + links will not be vulnerable to such corruptions. Also NOTE that + Lynx allows you to save links in your bookmark file for documents + returned by forms with the <em>GET</em> METHOD, and which thus + have the content appended as a <em>?searchpart</em>, but not if + the METHOD was <em>POST</em>, because the content would be lost + and the link thus would be invalid.</p> + + <p>Lynx supports <em>ENCTYPE="multipart/form-data"</em> for + sending form content with name=value pairs encoded as multipart + sections with individual MIME headers and boundaries. However, + Lynx does not yet support INPUTs with <em>TYPE="file"</em> or + <em>TYPE="range"</em> and will set the <em>DISABLED</em> + attribute for all of the form's fields if any INPUTs with either + of those two TYPEs are present, so that the form can't be + submitted. Otherwise, Lynx will submit the form with the + multipart ENCTYPE.</p> + + <p>A + <em>Content-Disposition: file; filename=name.suffix</em> + header can be used by CGI scripts to set the suggested filename + offered by Lynx for '<em>d</em>'ownload and '<em>p</em>'rint menu + options to save or mail the body returned by the script following + submission of a FORM. Otherwise, Lynx uses the last symbolic + element in the path for the FORM's ACTION, which is normally the + script, itself, or a PATH_INFO field, and thus might be + misleading. This also can be done via a META element in any + document:</p> + <pre> + <em><META HTTP-EQUIV="Content-Disposition" + CONTENT="file; filename=name.suffix"></em> +</pre> + + <p>[<a href="#ToC-Forms">ToC</a>]</p> + + <h2 id="id-Images"><a name="Images" id="Images"><em>Lynx and HTML + Images</em></a></h2> + + <p>As a text browser, Lynx does not display images as such -- you + need to define a viewer in <em>lynx.cfg</em>: see there -- , but + users can choose a number of ways of showing their presence.</p> + + <p>There are 3 choices in <em>lynx.cfg</em>, with 2 corresponding + keys:</p> + <pre> + MAKE_LINKS_FOR_ALL_IMAGES * IMAGE_TOGGLE + MAKE_PSEUDO_ALTS_FOR_INLINES [ INLINE_TOGGLE + VERBOSE_IMAGES no corresponding key +</pre> + + <p>You can also use the <em>Options Menu</em>, as outlined + below:</p> + <pre> + key lynx.cfg FM KM .lynxrc variable in source + + * MAKE_LINKS_ Y N N clickable_images + [ MAKE_PSEUDO_ Y N N pseudo_inline_alts + VERBOSE_ Y Y Y verbose_img + +FM = Form-based Menu ; KM = Key-based Menu ; +in .lynxrc , VERBOSE_IMAGES is called `verbose_images': +the other two cannot be saved between sessions. +</pre> + + <p>In the Form-based Menu, the 3-way `Show images' selection + combines the effects of the `*' & `[' keys, as follows:</p> + <pre> + Ignore clickable_images = FALSE, pseudo_inline_alts = FALSE + As labels clickable_images = FALSE, pseudo_inline_alts = TRUE + As links clickable_images = TRUE, pseudo_inline_alts = unchanged +</pre> + + <h2 id="id-Tables"><a name="Tables" id="Tables"><em>Lynx and HTML + Tables</em></a></h2> + + <p>HTML includes markup for creating <em>tables</em> structured + as arrays of cells aligned by columns and rows on the displayed + page.</p> + + <p>Lynx recognizes the TABLE element and all of its associated + elements as described in <a href= + "http://www.faqs.org/rfcs/rfc1942.html">RFC 1942</a> and will + process any ID attributes in the start tags for handling as + NAME-ed anchors, but does not create actual <em>tables</em>. + Instead, it treats the TR start tag as a collapsible BR (line + break), and inserts a collapsible space before the content of + each TH and TD start tag. This generally makes all of the content + of the <em>table</em> readable, preserves most of the intra-cell + organization, and makes all of the links in the <em>table</em> + accessible, but any information critically dependent on the + column and row alignments intended for the <em>table</em> will be + missed.</p> + + <p>If inherently tabular data must be presented with Lynx, one + can use PRE formatted content, or, if the <em>table</em> includes + markup not allowed for PRE content, construct the <em>table</em> + using <a href="#Tabs">HTML Tabs</a>. An example <em>table</em> + using <em>TAB</em> elements is included in the test subdirectory + of the Lynx distribution.</p> + + <div id="TRST"> + <p>Starting with version 2.8.3, Lynx renders some tables in + tabular form. This tabular representation for <em>simple</em> + tables (<dfn>TRST</dfn>) does not attempt to implement full + support for any table model. Limitations are:</p> + + <ul> + <li>All data constituting a table row generally has to fit + within the display width without inserting line breaks.</li> + + <li>Cell contents have to be simple. In general, only inline + markup is acceptable, no <code><P></code>, + <code><BR></code> etc. (although + <code><BR></code> may be ignored at the beginning of + the first cell or at the end of the last cell of a row).</li> + + <li>When tables are nested, only the innermost level is a + candidate for tabular representation.</li> + + <li>Most attributes are ignored, including borders, + <code>WIDTH</code>, vertical alignment.</li> + </ul>Horizontal alignments (<code>LEFT</code>, + <code>CENTER</code>, <code>RIGHT</code>), <code>COLSPAN</code>, + and <code>ROWSPAN</code> are interpreted according to HTML + 4.01. (<code>ROWSPAN</code> can only reserve empty space in + subsequent rows, because of the limitations above.) When TRST + fails because a table is not "simple" enough, the + representation falls back to the minimal handling described + earlier. Many (but, unfortunately, by no means all) tables that + represent inherently tabular material will thus be shown with + correct tabular formatting. Where table markup is used only for + layout purposes (containing whole blocks of text and list + within table cells) and not essential for understanding the + textual contents, it remains basically ignored. Some more + information on details is available in the file + <kbd>README.TRST</kbd> of the source distribution. + </div> + + <p>For tabular display of more complex tables, Lynx users can + make use of external scripts or programs. The normal Lynx + distribution currently does not provide such scripts, but they + can be written locally or downloaded from several sources. It is + suggested to use one of Lynx's facilities for invoking external + programs (see <kbd>DOWNLOADER</kbd>, <kbd>PRINTER</kbd>, + <kbd>EXTERNAL</kbd>, <kbd>TRUSTED_LYNXCGI</kbd> in <a href= + "#lynx.cfg">lynx.cfg</a> and <a href= + "lynx_url_support.html#cgi_url"><code>lynxcgi:</code></a> in + <em>Supported URLs</em> for information on various ways for + setting this up).</p> + + <p>[<a href="#ToC-Tables">ToC</a>]</p> + + <h2 id="id-Tabs"><a name="Tabs" id="Tabs"><em>Lynx and HTML + Tabs</em></a></h2> + + <p>Lynx implements the <a href= + "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> TAB + element only when LEFT alignment is in effect. If the alignment + is CENTER or RIGHT (JUSTIFY is not yet implemented in Lynx, and + is treated as a synonym for LEFT), or if the TAB element + indicates a position to the left of the current position on the + screen, it is treated as a collapsible space. For purposes of + implementing TAB, Lynx treats <em>en</em> units as half a + character cell width when specified by the INDENT attribute, and + rounds up for odd values (e.g., a value of either 5 or 6 will be + treated as three spaces, each the width of a character cell). See + the example <em>table</em> using TAB elements in the test + subdirectory of the Lynx distribution as a model for using this + functionality.</p> + + <p>Note that this <em>Users Guide</em> and the <a href= + "lynx_url_support.html">Supported URLs</a> page include TAB + markup in a manner which <em>degrades gracefully</em> for WWW + browsers which do not support it. Toggle to display of <a href= + "#LocalSource">source</a> and <a href="#Search">search</a> for + <em><tab</em> to examine the use of TAB markup in these + documents.</p> + + <p>[<a href="#ToC-Tabs">ToC</a>]</p> + + <h2 id="id-Frames"><a name="Frames" id="Frames"><em>Lynx and HTML + Frames</em></a></h2> + + <p>Some implementations of HTML include markup, primarily + designed for graphic clients, that is intended to create an array + of simultaneously displayed, independently scrolling windows. + Such windows have been termed <em>frames</em>.</p> + + <p>Lynx recognizes the Netscape and Microsoft Explorer FRAME, + FRAMESET, and NOFRAMES elements, but is not capable of windowing + to create the intended positioning of <em>frames</em>. Instead, + Lynx creates labeled links to the <em>frame</em> sources, + typically positioned in the upper left corner of the display, and + renders the NOFRAMES section. If the document provider has + disregard for text clients and sight-challenged Webizens, and + thus does not include substantive content in the NOFRAMES section + or a link in it to a document suitable for text clients, you can + usually guess from the labeling of the <em>frame</em> links which + one has the substantive material (if there is any), or you can + try each of those links to see if anything worthwhile is + returned.</p> + + <p>[<a href="#ToC-Frames">ToC</a>]</p> + + <p>Some sites -- in ignorance of Lynx capabilities -- may tell + you (for example) "to view this page you need Netscape + Navigator". You can simply ignore such warnings and access the + frames via the Lynx-generated links as above.</p> + + <h2 id="id-Banners"><a name="Banners" id="Banners"><em>Lynx and + HTML Banners</em></a></h2> + + <p>Some implementations of HTML markup include provisions for + creating a non-scrolling window to be positioned at the top of + each page, containing links with brief, descriptive link names, + analogous to a Windows toolbar. Such windows have been termed + <em>banners</em>.</p> + + <p>Lynx recognizes and processes all of the <a href= + "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> REL + attribute tokens in LINK elements for creating a <em>banner</em>, + and a number of others which have subsequently been proposed. + These <em>banner</em> tokens are <em>Home</em>, <em>ToC</em>, + <em>Contents</em>, <em>Index</em>, <em>Glossary</em>, + <em>Copyright</em>, <em>Up</em>, <em>Next</em>, + <em>Previous</em>, <em>Prev</em>, <em>Help</em>, <em>Search</em>, + <em>Top</em>, <em>Origin</em>, <em>Navigator</em>, + <em>Child</em>, <em>Disclaimer</em>, <em>Sibling</em>, + <em>Parent</em>, <em>Author</em>, <em>Editor</em>, + <em>Publisher</em>, <em>Trademark</em>, <em>Meta</em>, + <em>URC</em>, <em>Hotlist</em>, <em>Begin</em>, <em>First</em>, + <em>End</em>, <em>Last</em>, <em>Pointer</em>, + <em>Translation</em>, <em>Definition</em>, <em>Chapter</em>, + <em>Section</em>, <em>Subsection</em>, <em>Alternate</em>, + <em>Documentation</em>, <em>Biblioentry</em>, + <em>Bibliography</em>, <em>Start</em>, <em>Appendix</em>, + <em>Bookmark</em> and <em>Banner</em>. Any LINK elements with + those tokens as the REL attribute value, and an HREF attribute + value in the LINK, will invoke creation of a <em>banner</em> at + the top of the first page, with the element's HREF as the link, + and the token as the default link name. If a TITLE attribute is + included in the LINK, it's value will be used as the link name + instead of the default. <em>Bookmark</em> and <em>Banner</em> are + intended to be accompanied by a TITLE attribute, which in effect + makes the namespace for REL <em>banner</em> tokens infinite.</p> + + <p>If the special token <em>Help</em> is used as the REL value + and no HREF is included in the LINK, Lynx will use it own + <em>HELPFILE</em> URL for that link. For the special token + <em>Home</em> without an HREF, Lynx will use the default + <em>STARTFILE</em> (i.e., derived from the configuration files or + the WWW_HOME environment variable, <em>not</em> the command line + <em>startfile</em> if one was used). However, if a + <em>-homepage=URL</em> was specified on the command line, it's + URL will be used as the HREF. For the special token + <em>Index</em> without an HREF, Lynx will use the + <em>DEFAULT_INDEX_FILE</em> derived from the configuration files, + or if an <em>-index=URL</em> was specified on the command line, + it's URL will be used as the HREF.</p> + + <p>Lynx does not waste screen real estate maintaining the + <em>banner</em> at the top of every page, but the Lynx TOOLBAR + keystroke command ('<em>#</em>') will, any time it is pressed, + position you on the <em>banner</em> so that any of its links can + be activated, and pressing the <em>left-arrow</em> when in the + <em>banner</em> will return you to where you were in the current + document. The toolbar is indicated by a '<em>#</em>" preceding + its first link when present on the screen, that is, when the + first page of the document is being displayed. The availability + of a toolbar is indicated by a '<em>#</em>' at the top, left-hand + corner of the screen when the second or subsequent pages of the + document are being displayed.</p> + + <p>Lynx also recognizes the <a href= + "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> + BANNER container element, and will create a <em>banner</em> based + on its content if one has not already been created based on LINK + elements. Lynx treats the Microsoft MARQUEE element as a synonym + for BANNER (i.e., presenting it's markup as a static + <em>banner</em>, without any horizontal scrolling of its + content). Lynx does not prefix the BANNER or MARQUEE content with + a '<em>#</em>' because the content need not be only a series of + links with brief, descriptive links names, but does add a + '<em>#</em>' at the top, left-hand corner of the screen when the + content is not being displayed, to indicate it's accessibility + via the TOOLBAR keystroke command.</p> + + <p>[<a href="#ToC-Banners">ToC</a>]</p> + + <h2 id="id-Footnotes"><a name="Footnotes" id="Footnotes"><em>Lynx + and HTML Footnotes</em></a></h2> + + <p>Lynx implements the <a href= + "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> FN + element similarly to a named <em>A</em>nchor within the current + document, and assumes that the footnotes will be positioned at + the bottom of the document. However, in contrast to named + <em>A</em>nchors, the FN container element is treated as a block + (i.e., as if a new paragraph were indicated whether or not that + is indicated in its content) with greater than normal left and + right margins, and the block will begin with a <em>FOOTNOTE:</em> + label. For example, if the document contains:</p> + <pre> + See the <em><A HREF="#fn1"></em><a href= +"#an1">footnote</a><em></A></em>. +</pre>activating that link will take you to the labeled rendering +of: + <pre> + <em><FN ID="fn1"></em><p><a name="an1" id= +"an1">Lynx does not use popups for FN blocks.</a></p><em></FN></em> +</pre> + + <p>i.e., position it at the top of the page. Then, upon reading + the footnote, you can return to your previous position in the + document by pressing the <em>left-arrow</em> key. The content of + an FN element can be any HTML markup that is valid in the BODY of + the document.</p> + + <p>[<a href="#ToC-Footnotes">ToC</a>]</p> + + <h2 id="id-Notes"><a name="Notes" id="Notes"><em>Lynx and HTML + Notes</em></a></h2> + + <p>Lynx implements the <a href= + "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> NOTE + element (<em>Admonishment</em>) as a labeled block, i.e., as if a + new paragraph were indicated whether or not paragraphing markup + is included in its content, with greater than normal left and + right margins, and with the type of note indicated by an + emphasized label based on the value of its CLASS or ROLE + attribute. If no CLASS or ROLE attribute is included, the default + label <em>NOTE:</em> will be used. Lynx recognizes the values + <em>caution</em> and <em>warning</em>, for which, respectively, + the labels <em>CAUTION:</em> or <em>WARNING:</em> will be used. + The NOTE element can have an ID attribute, which will be treated + as a named <em>A</em>nchor, as for <a href="#Footnotes">HTML + Footnotes</a>, but the NOTE block need not be placed at the + bottom of the document. The content of a NOTE block can be any + HTML markup that is valid in the BODY of the document. This is an + example:<br></p> + <pre> + <em><NOTE CLASS="warning" ID="too-bad"> + <p>The W3C vendors did not retain NOTE in the HTML 3.2 draft.</p> + </NOTE></em> +</pre>It will <em>degrade gracefully</em> for WWW browsers which do +not support NOTE, except for recognition of the ID attribute as a +named <em>A</em>nchor. + + <p>[<a href="#ToC-Notes">ToC</a>]</p> + + <h2 id="id-Lists"><a name="Lists" id="Lists"><em>Lynx and HTML + Lists</em></a></h2> + + <p>Lynx implements the <a href= + "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> list + elements UL (<em>Unordered List</em>), OL (<em>Ordered + List</em>), and DL (<em>Definition List</em>), and their + associated attributes, and elements (LH, LI, DT, and DD) for the + most part as described in that specification. The lists can be + nested, yielding progressively greater indentation, up to six + levels. The <a href= + "http://www.w3.org/MarkUp/html-spec/html-spec_toc.html">HTML + 2.0</a> MENU and DIR elements <em>both</em> are treated as + synonyms for UL with the PLAIN attribute (no <em>bullets</em>, + see below). Note, thus, that neither DIR nor MENU yields a series + of columns with 24-character spacing. A single nesting index is + maintained, so that different types of List elements can be used + for different levels within the nest. Also, the <a href= + "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> FIG, + CAPTION and CREDIT elements are treated as valid within list + blocks. They will be rendered with indentation appropriate for + the current nesting depth, and the CAPTION or CREDIT elements + will have a <em>CAPTION:</em> or <em>CREDIT:</em> label beginning + the first line of their content. The content of any APPLET or + OBJECT elements in the lists also will be indented appropriately + for the current nesting depth, but those will not invoke line + breaks unless indicated by their content, and it should not + include markup which is inappropriate within the list.</p> + + <p>Lynx also supports the TYPE attribute for OL elements, which + can have values of <em>1</em> for Arabic numbers, <em>I</em> or + <em>i</em> for uppercase or lowercase Roman numerals, or + <em>A</em> or <em>a</em> for uppercase or lowercase letters, that + increment for successive LI elements in the list block. The + CONTINUE attribute can be used to continue the ordering from the + preceding list block when the nesting depth is changed.</p> + + <p>Lynx treats the OL attributes START and SEQNUM as synonyms for + specifying the ordering value for the first LI element in the + block. The values should be specified as Arabic numbers, but will + be displayed as Arabic, Roman, or alphabetical depending on the + TYPE for the block. The values can range from <em>-29997</em> to + the system's maximum positive integer for Arabic numbers. For + Roman numerals, they can range from <em>1</em> (<em>I</em> or + <em>i</em>) to <em>3000</em> (<em>MMM</em> or <em>mmm.</em>). For + alphabetical orders, the values can range from <em>1</em> + (<em>A</em> or <em>a</em>) to <em>18278</em> (<em>ZZZ</em> or + <em>zzz</em>). If the CONTINUE attribute is used, you do not need + to specify a START or SEQNUM attribute to extend the ordering + from a previous block, and you can include a TYPE attribute to + change among Arabic, Roman, or alphabetical ordering styles, or + their casing, without disrupting the sequence. If you do not + include a START, SEQNUM or CONTINUE attribute, the first LI + element of each OL block will default to <em>1</em>, and if you + do not include a TYPE attribute, Lynx defaults to Arabic + numbers.</p> + + <p>For UL blocks without the PLAIN attribute, Lynx uses + <em>*</em>, <em>+</em>, <em>o</em>, <em>#</em>, <em>@</em> and + <em>-</em> as <em>bullets</em> to indicate, progressively, the + depth within the six nesting levels.</p> + + <p>Lynx treats UL, OL, DIR, and MENU blocks as having the COMPACT + attribute by default, i.e., single spaces between LH and LI + elements within those blocks. For DL blocks, double spacing will + be used to separate the DT and DD elements unless the COMPACT + attribute has been specified.</p> + + <p>[<a href="#ToC-Lists">ToC</a>]</p> + + <h2 id="id-Quotes"><a name="Quotes" id="Quotes"><em>Lynx and HTML + Quotes</em></a></h2> + + <p>The <a href= + "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> and + later specifications provide for two classes of quotation in HTML + documents. Block quotes, designated by the BLOCKQUOTE element (or + 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.</p> + + <p>Lynx renders block quotes with a greater than normal left and + right indentation. Lynx does not support italics, and normally + substitutes underlining, but does not underline block quotes so + as not to obscure any explicit emphasis elements within the + quotation. The BLOCKQUOTE or BQ block can include a CREDIT + container element, whose content will be rendered as an implied + new paragraph with a <em>CREDIT:</em> label at the beginning of + its first line.</p> + + <p>Lynx respects nested Q start and end tags, and will use ASCII + double-quotes (<em>"</em>) versus grave accent (<em>`</em>) and + apostrophe (<em>'</em>), respectively, for even versus odd depths + in the nest.</p> + + <p>Any ID attributes in BLOCKQUOTE, BQ or Q elements can be the + target of a hyperlink in the form URL#id. It is treated just like + the NAME in <em>A</em>nchors.</p> + + <p>[<a href="#ToC-Quotes">ToC</a>]</p> + + <h2 id="id-Eightbit"><a name="Eightbit" id="Eightbit"><em>Lynx + and HTML Internationalization: 8bit, UNICODE, etc.</em></a></h2> + + <p>Lynx has superior support for HTML 4.0/I18N + internationalization issues. However, to see the characters other + than 7bit properly you <em>should</em> set your <a href= + "keystrokes/option_help.html#DC">display character set</a> from + Option Menu and save its value, this is a Frequently Asked + Question. Fine-turning is also available from <a href= + "#lynx.cfg">lynx.cfg</a></p> + + <p>[<a href="#ToC-Eightbit">ToC</a>]</p> + + <h2 id="id-USEMAP"><a name="USEMAP" id="USEMAP"><em>Lynx and + Client-Side-Image-Maps</em></a></h2> + + <p>HTML includes markup, designed primarily for graphic clients, + that treats inlined images as maps, such that areas of the image + within which a mouse cursor was positioned when the mouse was + <em>clicked</em> can correspond to URLs which should be + retrieved. The original implementations were based on the client + sending an http server the x,y coordinates associated with the + <em>click</em>, for handling by a script invoked by the server, + and have been termed <em>server-side-image-maps</em>. Lynx has no + rational way of coping with such a procedure, and thus simply + sends a 0,0 coordinate pair, which some server scripts treat as + an instruction to return a document suitable for a text + client.</p> + + <p>Newer HTML markup provides bases for the client to determine + the URLs associated with areas in the image map, and/or for a + text client to process alternative markup and allow the user to + make choices based on textual information. These have been termed + <em>client-side-image-maps</em>.</p> + + <p>Lynx recognizes and processes the MAP container element and + its AREA elements, and will create a menu of links for the HREF + of each AREA when the link created for the IMG element with a + USEMAP attribute is activated. The menu uses the ALT attributes + of the AREA elements as the link names, or, if the document's + author has disregard for text clients and sight-challenged + Webizens, and thus did not include ALT attributes, Lynx uses the + resolved URLs pointed to by the HREF attributes as the link + names. Lynx uses the TITLE attribute of the IMG element, or the + TITLE attribute of the MAP, if either was present in the markup, + as the title and main header of the menu. Otherwise, it uses the + ALT attribute of the IMG element. If neither TITLE nor ALT + attributes were present in the markup, Lynx creates and uses a + <em>[USEMAP]</em> pseudo-ALT. The MAPs need not be in the same + document as the IMG elements. If not in the same document, Lynx + will fetch the document which contains the referenced MAP, and + locate it based on its NAME or ID attribute. All MAPs encountered + in documents during a Lynx session are cached, so that they need + not be retrieved repeatedly when referenced in different + documents.</p> + + <p>If the IMG element also indicates a + <em>server-side-image-map</em> via an ISMAP attribute, Lynx + normally will create a link for that as well, using an + <em>[ISMAP]</em> pseudo-ALT (followed by a hyphen to indicate its + association with the <em>client-side-image-map</em>) rather than + ignoring it, and will submit a 0,0 coordinate pair if that link + is activated. Although, the <em>client-side-image-map</em> may be + more useful for a client such as Lynx, because all of the URLs + associated with the image map can be accessed, and their nature + indicated via ALT attributes, Lynx-friendly sites can map 0,0 + such that the server returns a for-text-client document + homologous to the content of FIG elements (see below). Inclusion + of such a link for submissions to the server can be disabled by + default via the configuration file (<a href= + "#lynx.cfg">lynx.cfg</a>), and the default can be toggled via the + <em>-ismap</em> command line switch.</p> + + <p>Lynx also recognizes the <a href= + "http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> FIG + and OVERLAY elements, and will handle them as intended for text + clients. These are the ideal way to handle + <em>client-side-image-maps</em>, because the FIG content provides + complete alternative markup, rather than relying on the client to + construct a relatively meager list of links with link names based + on ALT strings.</p> + + <p>The presently experimental OBJECT element encompasses much of + the functionality of the FIG element for + <em>client-side-image-maps</em>. Lynx will render and display the + content of OBJECT elements which have the SHAPES attribute + equivalently to its handling of FIG. Lynx also handles OBJECT + elements with the USEMAP and/or ISMAP attributes equivalently to + its handling of IMG elements with <em>client-side-image-maps</em> + and/or <em>server-side-image-maps</em>.</p> + + <p>[<a href="#ToC-USEMAP">ToC</a>]</p> + + <h2 id="id-Refresh"><a name="Refresh" id="Refresh"><em>Lynx and + Client-Side-Pull</em></a></h2> + + <p>HTML includes provision for passing instructions to clients + via directives in META elements, and one such instruction, via + the token <em>Refresh</em>, should invoke reloading of the + document, fetched from a server with the same URL or a new URL, + at a specified number of seconds following receipt of the current + document. This procedure has been termed + <em>client-side-pull</em>. An example of such an element is:</p> + <pre> + <em><META HTTP-EQUIV="Refresh" CONTENT="3; URL=http://host/path"></em> +</pre>which instructs a client to fetch the indicated URL in 3 +seconds after receiving the current document. If the <em>URL=</em> +field is omitted, the URL defaults to that of the current document. +A <em>no-cache</em> directive is implied when the <em>Refresh</em> +if for the same URL. + + <p>Lynx recognizes and processes <em>Refresh</em> directives in + META elements, but puts up a labeled link, typically in the upper + left corner of the display, indicating the number of seconds + intended before a refresh, and the URL for the refresh, instead + of making the request automatically after the indicated number of + seconds. This allows people using a braille interface any amount + of time to examine the current document before activating the + link for the next URL. In general, if the number of seconds + indicated is short, the timing is not critical and you can + activate the link whenever you like. If it is long (e.g., 60 + seconds), a server process may be generating new documents or + images at that interval, and you would be wasting bandwidth by + activating the link at a shorter interval.</p> + + <p>[<a href="#ToC-Refresh">ToC</a>]</p> + + <h2 id="id-Cookies"><a name="Cookies" id="Cookies"><em>Lynx State + Management</em></a> (Me want <em>cookie</em>!)</h2> + + <p>HTTP provides a means to carry state information across + successive connections between a browser and an http server. + Normally, http servers respond to each browser request without + relating that request to previous or subsequent requests. Though + the inclusion of INPUT fields with TYPE="hidden" can be used as a + sort of state management by <a href="#Forms">HTML Forms</a>, a + more general approach involves exchanges of MIME headers between + the server and browser. When replying to a request, the server + can send a <em>Set-Cookie</em> MIME header which contains + information (<em>cookies</em>) relevant to the browser's request, + and in subsequent requests the browser can send a <em>Cookie</em> + MIME header with information derived from previously received + cookies.</p> + + <p>State Management via cookie exchanges originally was + implemented by Netscape, and such cookies are now designated as + <em>Version 0</em>. A more elaborate format for cookies, + designated as <em>Version 1</em>, is being standardized by the + IETF (Internet Engineering Task Force). Lynx supports both + <em>Version 0</em> and <em>Version 1</em> cookie exchanges. This + support can be disabled by default via the SET_COOKIES symbol in + the compilation (<em>userdefs.h</em>) and/or run time (<a href= + "#lynx.cfg">lynx.cfg</a>) configuration files, and that default + setting can be toggled via the <em>-cookies</em> command line + switch. The SET_COOKIES symbol can be further modified by the + ACCEPT_ALL_COOKIES mode. If ACCEPT_ALL_COOKIES is set TRUE, and + SET_COOKIES is TRUE, Lynx will accept all cookies. Additionally, + the cookies that are automatically accepted or rejected by Lynx + can be further modified with the COOKIE_ACCEPT_DOMAINS and + COOKIE_REJECT_DOMAINS options in your .lynxrc file, each of which + is a comma-separated list of domains to perform the desired + action. The domain listed in these options must be identical to + the domain the cookie comes from, there is no wildcard matching. + If a domain is specific in both COOKIE_ACCEPT_DOMAINS and + COOKIE_REJECT_DOMAINS, rejection will take precedence.</p> + + <p>When cookie support is enabled, <em>Set-Cookie</em> MIME + headers received from an http server invoke confirmation prompts + with possible replies of '<em>Y</em>'es or '<em>N</em>'o for + acceptance of the cookie, '<em>A</em>'lways to accept the cookie + and to allow all subsequent cookies from that <em>domain</em> + (server's Fully Qualified Domain Name, or site-identifying + portion of the FQDN) without further confirmation prompts, or + ne'<em>V</em>'er to never allow cookies from that <em>domain</em> + to be accepted (silently ignore its <em>Set-Cookie</em> MIME + headers). All unexpired cookies are held in a hypothetical + <em>Cookie Jar</em> which can be examined via the COOKIE_JAR + keystroke command, normally mapped to <em>Ctrl-K</em>, for + invoking the <a href="keystrokes/cookie_help.html">Cookie Jar + Page</a>. If Lynx has been compiled with the + --enable-persistent-cookies flag, then unexpired cookies will be + stored between sessions in the filename set with the COOKIE_FILE + option in your .lynxrc.</p> + + <p>A common use of cookies by http servers is simply to track the + documents visited by individual users. Though this can be useful + to the site's WebMaster for evaluating and improving the + organization of links in the various documents of the site, if + the user has configured Lynx to include a <em>From</em> MIME + header with the user's email address in http requests, or has + passed personal information to the server via a form submission, + the tracking might be used to draw inferences, possibly + incorrect, about that user, and may be considered by some as an + invasion of privacy.</p> + + <p>An example of worthwhile State Management via cookies is the + setting of personal preferences, typically via a form submission + to the site, which will then apply to all documents visited at + that site.</p> + + <p>If you accept cookies when accessing a site, but are given no + indication about how they will be used in subsequent requests to + that site, nor can infer how they will be used, you can + <em>Gobble</em> (delete) the cookies and/or change the 'allow' + setting for its <em>domain</em> via the <a href= + "keystrokes/cookie_help.html">Cookie Jar Page</a>.</p> + + <p>[<a href="#ToC-Cookies">ToC</a>]</p> + + <h2 id="id-Cache"><a name="Cache" id="Cache"><em>Cached + Documents</em></a></h2> + + <p>A list of documents which are in lynx's internal cache is + accessible through hypothetical <em>Cache Jar</em> which can be + examined via the CACHE_JAR keystroke command, normally mapped to + <em>Ctrl-X</em>.</p> + + <p>Entries in the <em>Cache Jar</em> are ordered from oldest (at + the top) to newest. The user can easily access any document which + is in the cache, especially those which may be soon removed due + to configurable limits on the maximum number of cached documents, + as well as the maxmimum amount of memory used by the cache.</p> + + <p>The structure of <em>Cache Jar</em> is simple:</p> + + <ul> + <li>Each entry starts with its ordinal number (within the + session), recently added documents in cache have a smaller + number than documents which are added before, and are + positioned at the end of <em>Cache Jar</em></li> + + <li>Following its ordinal number is the document title, which + is also a link. On activating this link, the user is prompted + if they want to delete the document from <em>Cache Jar</em>. + The document's address (also a link) follows the title. It is + distinguished by a <code>URL:</code> label preceding the link. + Activating this link, lynx displays the corresponding cached + document.</li> + + <li>Below each cached document URL lynx shows the document + properties which include: + + <ul> + <li>Lines,</li> + + <li>Size,</li> + + <li>File-Cache,</li> + + <li>Content-Type,</li> + + <li>Content-Language,</li> + + <li>Content-Encoding,</li> + + <li>Content-Location,</li> + + <li>Subject,</li> + + <li>Owner,</li> + + <li>Date,</li> + + <li>Expires,</li> + + <li>Last-Modified,</li> + + <li>ETag,</li> + + <li>Server, and</li> + + <li>Source-Cache-File.</li> + </ul> + </li> + </ul> + + <p>This feature can be enabled by default using the USE_CACHEJAR + symbol in the compilation (<code>userdefs.h</code>), as well as + enabled in lynx.cfg</p> + + <p>[<a href="#ToC-Cache">ToC</a>]</p> + + <h2 id="id-Sessions"><a name="Sessions" id= + "Sessions"><em>Sessions</em></a></h2> + + <p>Lynx's current state (all information about the user's current + activity with lynx) is called a session. Sessions are useful in + particular if you are in the middle of exploring something on the + web and you were forced to stop abruptly, losing any trace of + your current work.</p> + + <p>A session can be automatically restored as lynx starts after a + clean exit. The session data is saved if lynx is invoked with the + <em>-session=FILENAME</em> switch. The <em>FILENAME</em> is the + name of the file where the session will be stored.</p> + + <p>There are also switches for only restoring: + <em>-sessionin=FILENAME</em> and for only saving: + <em>-sessionout=FILENAME</em> sesions:</p> + + <p>If you do not want to specify these options at each lynx + startup, there is an option in <em>lynx.cfg</em> to enable + automatic saving/restoring of session. To keep lynx startup/exit + reasonable fast there is also an option in <em>lynx.cfg</em> + specifying how much information about the current lynx session + will be stored in file.</p> + + <p>The syntax of the session file is simple. You can use a text + editor to modify, add new entries, or remove URLs you no longer + want.</p> + + <p>[<a href="#ToC-Sessions">ToC</a>]</p> + + <h2 id="id-Invoking"><a name="Invoking" id="Invoking"><em>The + Lynx command line</em></a></h2> + + <p>A summary of the Lynx command line options (switches) is + returned to stdout if Lynx is invoked with the <em>-help</em> + switch. A description of the options also should be available via + the system man (Unix) pages or help (VMS) libraries. On Win32, + typing lynx -help in a DOS window should display similarly. The + basic syntax of the Lynx command line can be represented as one + of the following:</p> + + <dl> + <dt><code>Command</code></dt> + + <dd><code>lynx [options]</code></dd> + + <dd><code>lynx [options] startfile</code></dd> + </dl>where + + <dl> + <dt><code>startfile</code></dt> + + <dd> + is the file or URL that Lynx will load at start-up. + + <ul> + <li>If startfile is not specified, Lynx will use a default + starting file and base directory determined during + installation.</li> + + <li>If a specified file is local (i.e., not a URL) Lynx + displays that file and uses the directory in which that + file resides as the base directory.</li> + + <li>If a URL is specified, the file will be retrieved, and + only the server base directory will be relevant to further + accesses.</li> + + <li>If more than one local file or remote URL is listed on + the command line, Lynx will open only the last + interactively. All of the names (local files and remote + URLs) are added to the G)oto history.</li> + </ul> + </dd> + + <dt><code>options</code></dt> + + <dd> + Lynx uses only long option names. Option names can begin with + double dash as well, underscores and dashes can be intermixed + in option names (in the reference below options are with one + dash before them and with underscores). + + <p>Lynx provides many command-line options. Some options + require a value (string, number or keyword). These are noted + in the reference below. The other options set boolean values + in the program. There are three types of boolean options: + set, unset and toggle. If no option value is given, these + have the obvious meaning: set (to true), unset (to false), or + toggle (between true/false). For any of these, an explicit + value can be given in different forms to allow for operating + system constraints, e.g.,</p> + <pre> +<code> + -center:off + -center=off + -center-</code> +</pre>Lynx recognizes "1", "+", "on" and "true" for true values, +and "0", "-", "off" and "false" for false values. Other +option-values are ignored. + + <p>The default boolean, number and string option values that + are compiled into lynx are displayed in the help-message + provided by lynx -help. Some of those may differ according to + how lynx was built; see the help message itself for these + values. The -help option is processed before any option, + including those that control reading from the lynx.cfg file. + Therefore runtime configuration values are not reflected in + the help-message.</p> + + <p>Capitalized items in the option summary indicate that a + substitution must be made. These are the options:</p> + + <dl> + <dt><code>-</code></dt> + + <dd>If the argument is only '<code>-</code>' (dash), then + Lynx expects to receive the arguments from stdin. This is + to allow for the potentially very long command line that + can be associated with the <em>-get_data</em> or + <em>-post_data</em> arguments (see below). It can also be + used to avoid having sensitive information in the invoking + command line (which would be visible to other processes on + most systems), especially when the <em>-auth</em> or + <em>-pauth</em> options are used. On VMS, the dash must be + encased in double-quotes ("-") and the keyboard input + terminated with <em>Control-Z</em> or the command file + input terminated by a line that begins with '<em>$</em>'. + On Unix, the keyboard input terminator is + <em>Control-D</em>. On Win32, [???].</dd> + + <dt><code>-accept_all_cookies</code></dt> + + <dd>accept all cookies.</dd> + + <dt><code>-anonymous</code></dt> + + <dd>apply restrictions appropriate for an anonymous + account, see <em>-restrictions</em> below for some + details.</dd> + + <dt><code>-assume_charset=MIMENAME</code></dt> + + <dd>charset for documents that don't specify it.</dd> + + <dt><code>-assume_local_charset=MIMENAME</code></dt> + + <dd>charset assumed for local files, i.e., files which lynx + creates such as internal pages for the options menu.</dd> + + <dt><code>-assume_unrec_charset=MIMENAME</code></dt> + + <dd>use this instead of unrecognized charsets.</dd> + + <dt><code>-auth=ID:PW</code></dt> + + <dd>set authorization ID and password for protected + documents at startup. Be sure to protect any script files + which use this switch.</dd> + + <dt><code>-base</code></dt> + + <dd>prepend a request URL comment and BASE tag to text/html + outputs for -source dumps.</dd> + + <dt><code>-bibp=URL</code></dt> + + <dd>specify a local bibp server (default + http://bibhost/).</dd> + + <dt><code>-blink</code></dt> + + <dd>forces high intensity background colors for color mode, + if available and supported by the terminal. This applies to + the slang library (for a few terminal emulators), or to + OS/2 EMX with ncurses.</dd> + + <dt><code>-book</code></dt> + + <dd>use the bookmark page as the startfile. The default or + command line startfile is still set for the Main screen + command, and will be used if the bookmark page is + unavailable or blank.</dd> + + <dt><code>-buried_news</code></dt> + + <dd>toggles scanning of news articles for buried + references, and converts them to news links. Not + recommended because email addresses enclosed in angle + brackets will be converted to false news links, and + uuencoded messages can be trashed.</dd> + + <dt><code>-cache=NUMBER</code></dt> + + <dd>set the <em>NUMBER</em> of documents cached in memory. + The default is 10.</dd> + + <dt><code>-center</code></dt> + + <dd>Toggle center alignment in HTML TABLE.</dd> + + <dt><code>-case</code></dt> + + <dd>enable case-sensitive string searching.</dd> + + <dt><code>-cfg=FILENAME</code></dt> + + <dd>specifies a Lynx configuration file other than the + default <a href="#lynx.cfg">lynx.cfg</a>.</dd> + + <dt><code>-child</code></dt> + + <dd>exit on left-arrow in startfile, and disable save to + disk.</dd> + + <dt><code>-child_relaxed</code></dt> + + <dd>exit on left-arrow in startfile, but allow save to disk + and associated print/mail options.</dd> + + <dt><code>-cmd_log=FILENAME</code></dt> + + <dd>write keystroke commands and related information to the + specified file.</dd> + + <dt><code>-cmd_script=FILENAME</code></dt> + + <dd> + read keystroke commands from the specified file. You can + use the data written using the <em>-cmd_log</em> option. + Lynx will ignore other information which the + command-logging may have written to the log- file. Each + line of the command script contains either a comment + beginning with "#", or a keyword: + + <dl> + <dt><code>exit</code></dt> + + <dd>causes the script to stop, and forces lynx to exit + immediately.</dd> + + <dt><code>key</code></dt> + + <dd>the character value, in printable form. Cursor and + other special keys are given as names, e.g., <code>Down + Arrow</code>. Printable 7-bit ASCII codes are given + as-is, and hexadecimal values represent other 8-bit + codes.</dd> + + <dt><code>set</code></dt> + + <dd>followed by a "name=value" allows one to override + values set in the lynx.cfg file.</dd> + </dl> + </dd> + + <dt><code>-color</code></dt> + + <dd>forces color mode on, if available. Default color + control sequences which work for many terminal types are + assumed if the terminal capability description does not + specify how to handle color. Lynx needs to be compiled with + the slang library for this flag. It is equivalent to + setting the COLORTERM environment variable. (If color + support is instead provided by a color-capable curses + library like ncurses, Lynx relies completely on the + terminal description to determine whether color mode is + possible, and this flag is not needed and thus + unavailable.) A saved show_color=always setting found in a + .lynxrc file at startup has the same effect. A saved + show_color=always found in .lynxrc on startup is overridden + by this flag.</dd> + + <dt><code>-connect_timeout=N</code></dt> + + <dd>Sets the connection timeout, where N is given in + seconds.</dd> + + <dt><code>-cookie_file=FILENAME</code></dt> + + <dd>specifies a file to use to read cookies. If none is + specified, the default value is ~/.lynx_cookies for most + systems, but ~/cookies for MS-DOS.</dd> + + <dt><code>-cookie_save_file=FILENAME</code></dt> + + <dd>specifies a file to use to store cookies. If none is + specified, the value given by <code>-cookie_file</code> is + used.</dd> + + <dt><code>-cookies</code></dt> + + <dd>toggles handling of Set-Cookie headers.</dd> + + <dt><code>-core</code></dt> + + <dd>toggles forced core dumps on fatal errors. (Unix + only)</dd> + + <dt><code>-crawl</code></dt> + + <dd>with <em>-traversal</em>, output each page to a + file.<br> + with <em>-dump</em>, format output as with + <em>-traversal</em>, but to stdout.</dd> + + <dt><code>-curses_pads</code></dt> + + <dd>toggles the use of curses "pad" feature which supports + left/right scrolling of the display.</dd> + + <dt><code>-debug_partial</code></dt> + + <dd>separate incremental display stages with MessageSecs + delay</dd> + + <dt><code>-display=DISPLAY</code></dt> + + <dd>set the display variable for X rexe-ced programs.</dd> + + <dt><code>-display_charset=MIMEname</code></dt> + + <dd>set the charset for the terminal output.</dd> + + <dt><code>-dont_wrap_pre</code></dt> + + <dd>inhibit wrapping of text in <pre> when -dump'ing + and -crawl'ing, mark wrapped lines in interactive + session.</dd> + + <dt><code>-dump</code></dt> + + <dd>dumps the formatted output of the default document or + one specified on the command line to standard out. This can + be used in the following way:<br> + <em>lynx -dump http://www.w3.org/</em></dd> + + <dt><code>-editor=EDITOR</code></dt> + + <dd>enable external editing using the specified + <em>EDITOR</em>. (vi, ed, emacs, etc.)</dd> + + <dt><code>-emacskeys</code></dt> + + <dd>enable emacs-like key movement.</dd> + + <dt><code>-enable_scrollback</code></dt> + + <dd>toggles behavior compatible with the scrollback keys in + some communications software (may be incompatible with some + curses packages).</dd> + + <dt><code>-error_file=FILENAME</code></dt> + + <dd>the status code from the HTTP request is placed in this + file.</dd> + + <dt><code>-exec</code></dt> + + <dd>enable local program execution (normally not + configured).</dd> + + <dt><code>-fileversions</code></dt> + + <dd>include all versions of files in local VMS directory + listings.</dd> + + <dt><code>-find_leaks</code></dt> + + <dd>toggles the memory leak checking off. Normally this is + not compiled-into your executable, but when it is, it can + be disabled for a session.</dd> + + <dt><code>-force_empty_hrefless_a</code></dt> + + <dd>force HREF-less 'A' elements to be empty (close them as + soon as they are seen).</dd> + + <dt><code>-force_html</code></dt> + + <dd>forces the first document to be interpreted as + HTML.</dd> + + <dt><code>-force_secure</code></dt> + + <dd>toggles forcing of the secure flag for SSL + cookies.</dd> + + <dt><code>-forms_options</code></dt> + + <dd>toggles whether the Options Menu is key-based or + form-based.</dd> + + <dt><code>-from</code></dt> + + <dd>toggles transmissions of From headers to HTTP or HTTPS + servers.</dd> + + <dt><code>-ftp</code></dt> + + <dd>disable ftp access.</dd> + + <dt><code>-get_data</code></dt> + + <dd>properly formatted data for a get form are read in from + stdin and passed to the form. Input is terminated by a line + that starts with '---'.</dd> + + <dt><code>-head</code></dt> + + <dd>send a HEAD request for the mime headers.</dd> + + <dt><code>-help</code></dt> + + <dd>print this Lynx command syntax usage message.</dd> + + <dt><code>-hiddenlinks=<em>option</em></code></dt> + + <dd> + control the display of hidden links. Option values are: + + <dl> + <dt><code>merge</code></dt> + + <dd>hidden links show up as bracketed numbers and are + numbered together with other links in the sequence of + their occurrence in the document.</dd> + + <dt><code>listonly</code></dt> + + <dd>hidden links are shown only on <em>L</em>ist + screens and listings generated by <code>-dump</code> or + from the <em>P</em>rint menu, but appear separately at + the end of those lists. This is the default + behavior.</dd> + + <dt><code>ignore</code></dt> + + <dd>hidden links do not appear even in listings.</dd> + </dl> + </dd> + + <dt><code>-historical</code></dt> + + <dd>toggles use of '>' or '-->' as a terminator for + comments.</dd> + + <dt><code>-homepage=URL</code></dt> + + <dd>set homepage separate from start page. Will be used if + a fetch of the start page fails or if it is a script which + does not return a document, and as the <code>URL</code> for + the '<em>m</em>'ain menu command.</dd> + + <dt><code>-image_links</code></dt> + + <dd>toggles inclusion of links for all images.</dd> + + <dt><code>-ismap</code></dt> + + <dd>toggles inclusion of ISMAP links when client-side MAPs + are present.</dd> + + <dt><code>-index=URL</code></dt> + + <dd>set the default index file to the specified + <em>URL</em></dd> + + <dt><code>-justify</code></dt> + + <dd>do justification of text.</dd> + + <dt><code>-link=NUMBER</code></dt> + + <dd>starting count for lnk#.dat files produced by + <em>-crawl</em>.</dd> + + <dt><code>-localhost</code></dt> + + <dd>disable URLs that point to remote hosts.</dd> + + <dt><code>-locexec</code></dt> + + <dd>enable local program execution from local files only + (if lynx was compiled with local execution enabled).</dd> + + <dt><code>-lss=FILENAME</code></dt> + + <dd>specify filename containing color-style information. + The default is lynx.lss.</dd> + + <dt><code>-mime_header</code></dt> + + <dd>include mime headers and force source dump.</dd> + + <dt><code>-minimal</code></dt> + + <dd>toggles minimal versus valid comment parsing. When + minimal, any '-->' serves as a terminator for a comment + element. When valid, pairs of '--' are treated as + delimiters for series of comments within the overall + comment element. If historical is set, that overrides + minimal or valid comment parsing.</dd> + + <dt><code>-nested_tables</code></dt> + + <dd>toggles nested-tables logic (for debugging).</dd> + + <dt><code>-newschunksize=NUMBER</code></dt> + + <dd>number of articles in chunked news listings.</dd> + + <dt><code>-newsmaxchunk=NUMBER</code></dt> + + <dd>maximum news articles in listings before chunking.</dd> + + <dt><code>-nobold</code></dt> + + <dd>disable bold video-attribute.</dd> + + <dt><code>-nobrowse</code></dt> + + <dd>disable directory browsing.</dd> + + <dt><code>-nocc</code></dt> + + <dd>disable Cc: prompts for self copies of mailings. Note + that this does not disable any CCs which are incorporated + within a mailto URL or form ACTION.</dd> + + <dt><code>-nocolor</code></dt> + + <dd>force color mode off, overriding terminal capabilities + and any <em>-color</em> flags, <em>COLORTERM</em> variable, + and saved .lynxrc settings.</dd> + + <dt><code>-noexec</code></dt> + + <dd>disable local program execution. (DEFAULT)</dd> + + <dt><code>-nofilereferer</code></dt> + + <dd>disable transmissions of Referer headers for file + URLs.</dd> + + <dt><code>-nolist</code></dt> + + <dd>disable the link list feature in dumps.</dd> + + <dt><code>-nolog</code></dt> + + <dd>disable mailing of error messages to document + owners.</dd> + + <dt><code>-nomargins</code></dt> + + <dd>disable left/right margins in the default style + sheet.</dd> + + <dt><code>-nomore</code></dt> + + <dd>disable -more- string in statusline messages.</dd> + + <dt><code>-nonrestarting_sigwinch</code></dt> + + <dd>make window size change handler non-restarting. This + flag is not available on all systems, Lynx needs to be + compiled with HAVE_SIGACTION defined. If available, this + flag <em>may</em> cause Lynx to react more immediately to + window changes when run within an xterm.</dd> + + <dt><code>-nopause</code></dt> + + <dd>disable forced pauses for statusline messages.</dd> + + <dt><code>-noprint</code></dt> + + <dd>disable most print functions.</dd> + + <dt><code>-noredir</code></dt> + + <dd>don't follow URL redirections</dd> + + <dt><code>-noreferer</code></dt> + + <dd>disable transmissions of Referer headers.</dd> + + <dt><code>-noreverse</code></dt> + + <dd>disable reverse video-attribute.</dd> + + <dt><code>-nosocks</code></dt> + + <dd>disable SOCKS proxy usage by a SOCKSified Lynx.</dd> + + <dt><code>-nostatus</code></dt> + + <dd>disable the retrieval status messages.</dd> + + <dt><code>-notitle</code></dt> + + <dd>disable title and blank line from top of page.</dd> + + <dt><code>-nounderline</code></dt> + + <dd>disable underline video-attribute.</dd> + + <dt><code>-number_fields</code></dt> + + <dd>force numbering of links as well as form input + fields.</dd> + + <dt><code>-number_links</code></dt> + + <dd>force numbering of links.</dd> + + <dt><code>-partial</code></dt> + + <dd>toggles displaying of partial pages while loading.</dd> + + <dt><code>-partial_thres=<em>NUMBER</em></code></dt> + + <dd>number of lines to render before repainting display + with partial-display logic.</dd> + + <dt><code>-pauth=ID:PW</code></dt> + + <dd>set authorization ID and password for a protected proxy + server at startup. Be sure to protect any script files + which use this switch.</dd> + + <dt><code>-popup</code></dt> + + <dd>toggles handling of single-choice SELECT options via + popup windows or as lists of radio buttons. The default + configuration can be changed in userdefs.h or <a href= + "#lynx.cfg">lynx.cfg</a>. It also can be set and saved via + the 'o'ptions menu. The command line switch toggles the + default.</dd> + + <dt><code>-post_data</code></dt> + + <dd>properly formatted data for a post form are read in + from stdin and passed to the form. Input is terminated by a + line that starts with '---'.</dd> + + <dt><code>-preparsed</code></dt> + + <dd>show source preparsed and reformatted when used with + -source or in source view ('<em>\</em>'). May be useful for + debugging of broken HTML markup to visualize the difference + between SortaSGML and TagSoup <a href= + "keystrokes/option_help.html#tagsoup">recovery modes</a>, + switched by '<em>^V</em>'.</dd> + + <dt><code>-prettysrc</code></dt> + + <dd>do syntax highlighting and hyperlink handling in source + view.</dd> + + <dt><code>-print</code></dt> + + <dd>enable print functions. (default)</dd> + + <dt><code>-pseudo_inlines</code></dt> + + <dd>toggles pseudo-ALTs for inline images with no ALT + string.</dd> + + <dt><code>-raw</code></dt> + + <dd>toggles default setting of 8-bit character translations + or CJK mode for the startup character set.</dd> + + <dt><code>-realm</code></dt> + + <dd>restricts access to URLs in the starting realm.</dd> + + <dt><code>-reload</code></dt> + + <dd>flushes the cache on a proxy server (only the first + document affected).</dd> + + <dt><code>-restrictions</code></dt> + + <dd>allows a list of services to be disabled selectively + and takes the following form:</dd> + + <dd><em>lynx + -restrictions=[option][,option][,option]...</em></dd> + + <dd> + The list of recognized options is printed if none are + specified. + + <dl> + <dt>?</dt> + + <dd>if used alone, lists restrictions in effect.</dd> + + <dt>all</dt> + + <dd>restricts all options listed below.</dd> + + <dt>bookmark</dt> + + <dd>disallow changing the location of the bookmark + file.</dd> + + <dt>bookmark_exec</dt> + + <dd>disallow execution links via the bookmark + file.</dd> + + <dt>change_exec_perms</dt> + + <dd>disallow changing the eXecute permission on files + (but still allow it for directories) when local file + management is enabled.</dd> + + <dt>chdir</dt> + + <dd>disallow command which changes Lynx's working + directory.</dd> + + <dt>default</dt> + + <dd>same as command line option <em>-anonymous</em>. + Set default restrictions for anonymous users. All + specific services listed are always restricted, except + for: inside_telnet, outside_telnet, inside_ftp, + outside_ftp, inside_rlogin, outside_rlogin, + inside_news, outside_news, telnet_port, jump, mail, + print, exec, and goto. The settings for these, as well + as additional goto restrictions for specific URL + schemes that are also applied, are derived from + definitions within userdefs.h.<br> + Note that this is the only option value that may have + the effect of <em>removing</em> some restrictions, if + they have been set by other options, namely for those + services that <em>are</em> allowed by default according + to userdefs.h. However, if the separate command line + option form (<em>-anonymous</em>) is used, Lynx takes + care to set the default restrictions before handling + additional <em>-restrictions=</em> options (even if + they precede the <em>anonymous</em> option), so that + this cannot happen.</dd> + + <dt>dired_support</dt> + + <dd>disallow local file management.</dd> + + <dt>disk_save</dt> + + <dd>disallow saving to disk in the download and print + menus.</dd> + + <dt>dotfiles</dt> + + <dd>disallow access to, or creation of, hidden (dot) + files.</dd> + + <dt>download</dt> + + <dd>disallow some downloaders in the download menu. + This does <em>not</em> imply the disk_save restriction. + It also does not disable the DOWNLOAD command, and does + not prevent "Download or Cancel" offers when a MIME + type cannot otherwise be handled. Those are only + disabled if additionally the disk_save restriction is + in effect <em>and</em> no download methods are defined + in a <a href="#lynx.cfg">Lynx configuration file</a> + that are marked as "always ENABLED" (or, alternatively, + if the -validate switch is used).</dd> + + <dt>editor</dt> + + <dd>disallow external editing.</dd> + + <dt>exec</dt> + + <dd>disable execution scripts.</dd> + + <dt>exec_frozen</dt> + + <dd>disallow the user from changing the local execution + option.</dd> + + <dt>externals</dt> + + <dd>disallow some "EXTERNAL" configuration lines, if + support for passing URLs to external applications (with + the EXTERN_LINK or EXTERN_PAGE command) is compiled + in.</dd> + + <dt>file_url</dt> + + <dd>disallow using G)oto, served links or bookmarks for + file: URLs.</dd> + + <dt>goto</dt> + + <dd>disable the '<em>g</em>' (goto) command.</dd> + + <dt>inside_ftp</dt> + + <dd>disallow ftps for people coming from inside your + domain.</dd> + + <dt>inside_news</dt> + + <dd>disallow USENET news reading and posting for people + coming from inside you domain. This applies to "news", + "nntp", "newspost", and "newsreply" URLs, but not to + "snews", "snewspost", or "snewsreply" in case they are + supported.</dd> + + <dt>inside_rlogin</dt> + + <dd>disallow rlogins for people coming from inside your + domain.</dd> + + <dt>inside_telnet</dt> + + <dd>disallow telnets for people coming from inside your + domain.</dd> + + <dt>jump</dt> + + <dd>disable the '<em>j</em>' (jump) command.</dd> + + <dt>lynxcgi</dt> + + <dd>disallow execution of Lynx CGI URLs.</dd> + + <dt>mail</dt> + + <dd>disallow mailing feature.</dd> + + <dt>multibook</dt> + + <dd>disallow multiple bookmarks.</dd> + + <dt>news_post</dt> + + <dd>disallow USENET News posting,</dd> + + <dt>options_save</dt> + + <dd>disallow saving options in .lynxrc.</dd> + + <dt>outside_ftp</dt> + + <dd>disallow ftps for people coming from outside your + domain.</dd> + + <dt>outside_news</dt> + + <dd>disallow USENET news reading and posting for people + coming from outside you domain. This applies to "news", + "nntp", "newspost", and "newsreply" URLs, but not to + "snews", "snewspost", or "snewsreply" in case they are + supported.</dd> + + <dt>outside_rlogin</dt> + + <dd>disallow rlogins for people coming from outside + your domain.</dd> + + <dt>outside_telnet</dt> + + <dd>disallow telnets for people coming from outside + your domain.</dd> + + <dt>print</dt> + + <dd>disallow most print options.</dd> + + <dt>shell</dt> + + <dd>disallow shell escapes.</dd> + + <dt>suspend</dt> + + <dd>disallow <em>Control-Z</em> suspends with escape to + shell on Unix.</dd> + + <dt>telnet_port</dt> + + <dd>disallow specifying a port in telnet G)oto's.</dd> + + <dt>useragent</dt> + + <dd>disallow modifications of the User-Agent + header.</dd> + </dl> + </dd> + + <dt><code>-resubmit_posts</code></dt> + + <dd>toggles forced resubmissions (no-cache) of forms with + method POST when the documents they returned are sought + with the PREV_DOC (<em>left-arrow</em>) command or from the + <em>History Page</em>.</dd> + + <dt><code>-rlogin</code></dt> + + <dd>disable recognition of rlogin commands.</dd> + + <dt><code>-scrollbar</code></dt> + + <dd>toggles showing scrollbar.</dd> + + <dt><code>-scrollbar_arrow</code></dt> + + <dd>toggles showing arrows at ends of the scrollbar.</dd> + + <dt><code>-selective</code></dt> + + <dd>require .www_browsable files to browse + directories.</dd> + + <dt><code>-session=FILENAME</code></dt> + + <dd>resumes from specified file on startup and saves + session to that file on exit.</dd> + + <dt><code>-sessionin=FILENAME</code></dt> + + <dd>resumes session from specified file.</dd> + + <dt><code>-sessionout=FILENAME</code></dt> + + <dd>saves session to specified file.</dd> + + <dt><code>-short_url</code></dt> + + <dd>show very long URLs in the status line with "..." to + represent the portion which cannot be displayed. The + beginning and end of the URL are displayed, rather than + suppressing the end.</dd> + + <dt><code>-show_cursor</code></dt> + + <dd>If enabled the cursor will not be hidden in the right + hand corner but will instead be positioned at the start of + the currently selected link. Show cursor is the default for + systems without FANCY_CURSES capabilities. The default + configuration can be changed in userdefs.h or <a href= + "#lynx.cfg">lynx.cfg</a>. It also can be set and saved via + the 'o'ptions menu. The command line switch toggles the + default.</dd> + + <dt><code>-show_rate</code></dt> + + <dd>If enabled the transfer rate is shown in bytes/second. + If disabled, no transfer rate is shown. Use lynx.cfg or the + options menu to select KiB/second and/or ETA.</dd> + + <dt><code>-soft_dquotes</code></dt> + + <dd>toggles emulation of the old Netscape and Mosaic bug + which treated '<em>></em>' as a co-terminator for + double-quotes and tags.</dd> + + <dt><code>-source</code></dt> + + <dd> + works the same as dump but outputs HTML source instead of + formatted text. For example + <pre> +<tt> + lynx -source . >foo.html + </tt> +</pre>generates HTML source listing the files in the current +directory. Each file is marked by an HREF relative to the parent +directory. Add a trailing slash to make the HREF's relative to the +current directory: + <pre> +<tt> + lynx -source ./ >foo.html + </tt> +</pre> + </dd> + + <dt><code>-stack_dump</code></dt> + + <dd>disable SIGINT cleanup handler.</dd> + + <dt><code>-startfile_ok</code></dt> + + <dd>allow non-http startfile and homepage with + <em>-validate</em>.</dd> + + <dt><code>-stderr</code></dt> + + <dd>When dumping a document using <code>-dump</code> or + <code>-source</code>, Lynx normally does not display alert + (error) messages that you see on the screen in the status + line. Use the <code>-stderr</code> option to tell Lynx to + write these messages to the standard error.</dd> + + <dt><code>-stdin</code></dt> + + <dd>read the startfile from standard input (UNIX + only).</dd> + + <dt><code>-syslog=<em>text</em></code></dt> + + <dd>information for syslog call.</dd> + + <dt><code>-syslog-urls</code></dt> + + <dd>log requested URLs with syslog.</dd> + + <dt><code>-tagsoup</code></dt> + + <dd>initialize DTD with "TagSoup" tables, <a href= + "keystrokes/option_help.html#tagsoup">more + details</a>.</dd> + + <dt><code>-telnet</code></dt> + + <dd>disable recognition of telnet commands.</dd> + + <dt><code>-term=TERM</code></dt> + + <dd>tell Lynx what terminal type to assume its talking to. + (This may be useful for remote execution, when, for + example, Lynx connects to a remote TCP/IP port that starts + a script that, in turn, starts another Lynx process.)</dd> + + <dt><code>-timeout=<em>N</em></code></dt> + + <dd>For win32, sets the network read-timeout, where N is + given in seconds.</dd> + + <dt><code>-tlog</code></dt> + + <dd>toggles use of a <em>Lynx Trace Log</em> for the + session. The log is named <em>Lynx.trace</em> and is + created in the home directory when Lynx trace mode is + turned on via the <em>-trace</em> command line switch (see + below), or via the TRACE_TOGGLE (<em>Control-T</em>) + keystroke command. Once a log is started for the session, + all trace and other stderr messages are written to the log. + The contents of the log can be examined during the session + via the TRACE_LOG (normally, '<em>;</em>') keystroke + command. If use of a Lynx Trace Log is turned off, any + trace output will go to the standard error stream.</dd> + + <dt><code>-tna</code></dt> + + <dd>turns on <a href="#tna">"Textfields Need + Activation"</a> mode.</dd> + + <dt><code>-trace</code></dt> + + <dd>turns on Lynx trace mode. If a Lynx Trace Log + (<em>Lynx.trace</em> in the home directory) has been + started for the current session, all trace messages are + written to that log, and can be examined during the session + via the TRACE_LOG (normally, '<em>;</em>') command. If no + Trace Log file is in use, trace messages go to stderr.</dd> + + <dt><code>-trace_mask=<em>value</em></code></dt> + + <dd> + turn on optional traces, which may result in very large + trace files. Logically OR the values to combine options: + + <dl> + <dt>1</dt> + + <dd>SGML character parsing states</dd> + + <dt>2</dt> + + <dd>color-style</dd> + + <dt>4</dt> + + <dd>TRST (table layout)</dd> + + <dt>8</dt> + + <dd>config (lynx.cfg and .lynxrc contents)</dd> + + <dt>16</dt> + + <dd>binary string copy/append, used in form data + construction.</dd> + </dl> + </dd> + + <dt><code>-traversal</code></dt> + + <dd>traverse all http links derived from startfile. When + used with <em>-crawl</em>, each link that begins with the + same string as startfile is output to a file, intended for + indexing. See CRAWL.announce for more information.</dd> + + <dt><code>-trim_input_fields</code></dt> + + <dd>trim input text/textarea fields in forms.</dd> + + <dt><code>-underscore</code></dt> + + <dd>toggles use of _underline_ format in dumps.</dd> + + <dt><code>-use_mouse</code></dt> + + <dd>turn on mouse support, if available.</dd> + + <dt><code>-useragent=STRING</code></dt> + + <dd>set different Lynx User-Agent header. Lynx produces a + warning on startup if the STRING does not contain "Lynx" or + "L_y_n_x", see the <a href="#noteUA">note</a> in the + Options Menu section for rationale.</dd> + + <dt><code>-validate</code></dt> + + <dd>accept only http URLs (meant for validation).</dd> + + <dd>This flag implies security restrictions generally more + severe than <em>-anonymous</em>: restriction options as for + <em>-restrictions=all</em>, with the notable exception that + goto remains enabled for http and https URLs; in addition, + the PRINT and DOWNLOAD commands are completely disabled, + and use of a Trace Log file is forced off.</dd> + + <dd>Any relaxing of restriction that might be implied by an + also present (or implied) <em>-anonymous</em> flag is + overridden, the only way to possibly relax <em>some</em> of + the restrictions to the level applicable for "anononymous" + accounts is with an explicit + <em>-restrictions=default</em>.</dd> + + <dt><code>-verbose</code></dt> + + <dd>toggles [LINK], [IMAGE] and [INLINE] comments with + filenames of these images.</dd> + + <dt><code>-version</code></dt> + + <dd>print version information.</dd> + + <dt><code>-vikeys</code></dt> + + <dd>enable vi-like key movement.</dd> + + <dt><code>-wdebug</code></dt> + + <dd>enable Waterloo tcp/ip packet debug (print to watt + debugfile). This applies only to DOS versions compiled with + WATTCP or WATT-32.</dd> + + <dt><code>-width=NUMBER</code></dt> + + <dd>number of columns for formatting of dumps, default is + 80.</dd> + + <dt><code>-with_backspaces</code></dt> + + <dd>emit backspaces in output if -dumping or -crawling + (like <code>man</code> does).</dd> + </dl> + </dd> + </dl> + + <p>No options are required, nor is a startfile argument required. + White space can be used in place of equal sign separators + ('<em>=</em>') appearing in the option list above. It can not be + used in place of the equal signs in forms like "-option=on" and + "-option=off" for simple switches and toggles, for which + "-option" alone (without a value) is valid.</p> + + <p>[<a href="#ToC-Invoking">ToC</a>]</p> + + <h2 id="Environments"><a name="Environment" id= + "Environment"><em>Environment variables used by + Lynx</em></a></h2> + + <p>Lynx uses certain environment variables and sets a few of + them. Please visit a <a href= + "keystrokes/environments.html">separate page</a> for this rather + technical information.</p> + + <p>[<a href="#ToC-Environment">ToC</a>]</p> + + <h2 id="id-lynx.cfg"><a name="lynx.cfg" id="lynx.cfg"><em>Main + configuration file lynx.cfg</em></a></h2> + + <p>Lynx has several levels of customization: from the Options + Menu (accessible on-line, and possibly stored in your local + .lynxrc file), via command-line switches on startup (mainly for + batch processing). The most important and numerous default + settings are stored in the Lynx configuration file + <em>lynx.cfg</em>.</p> + + <p>If you are on a UNIX system you should have appropriate + permissions to make changes there or ask your system + administrator to modify lynx.cfg for your needs. This file + provides default settings for all accounts on your system. It may + be copied to your shell account and included with -cfg command + line switch or via an environment variable LYNX_CFG (if you have + shell access). Starting with version 2.8.1 Lynx has an include + facility so you can load the system-wide configuration file and + easily add one or more settings from your local add-on + configuration file. It is really cool to read lynx.cfg with its + comments for hundreds of options, most of them commented out + because they are built-in defaults. You may visit an index of + options: <a href= + "http://lynx.isc.org/release/lynx2-8-7/lynx_help/cattoc.html">by + category</a> or <a href= + "http://lynx.isc.org/release/lynx2-8-7/lynx_help/alphatoc.html">by + alphabet</a>.</p> + + <p>To view your current configuration derived from lynx.cfg and + any included configuration files, press <em>'g'</em> and type in + '<em>lynxcfg:</em>'. If you are using the forms-based <em>Options + Menu</em>, you may press <em>'o'</em> for the Options Menu and + follow the '<em>Check your lynx.cfg</em>' link near the + bottom.</p> + + <p>However, for those who have a restricted account many Lynx + features may be disabled by the system administrator, you + probably will not see your lynx.cfg.</p> + + <p>[<a href="#ToC-lynx.cfg">ToC</a>]</p> + + <h2 id="id-Hist"><a name="Hist" id="Hist"><em>Lynx development + history</em></a></h2> + + <p>Lynx grew out of efforts to build a campus-wide information + system at The University of Kansas. The earliest versions of Lynx + provided a user-friendly, distributed hypertext interface for + users connected to multiuser (Unix and VMS) systems via + curses-oriented display devices. A custom hypertext format was + developed to support hypertext links to local files and files on + remote Gopher servers. Using Gopher servers for distributed file + service allowed information providers to publish information from + a wide variety of platforms (including Unix, VMS, VM/CMS and + Macintosh). In addition, Lynx became the most user-friendly + Gopher client, although that was only an ancillary + capability.</p> + + <p>This distributed approach let providers retain complete + control over their information, but it made communication between + users and providers somewhat more difficult. Following the lead + of Neal Erdwien, of Kansas State University, the Lynx hypertext + format was extended to include links for including ownership + information with each file. This information made it possible for + users running Lynx clients to send comments and suggestions via + e-mail to the providers.</p> + + <p>This early version of Lynx was also augmented to support + hypertext links to programs running on remote systems. It + included the ability to open a Telnet connection, as well as the + ability to start programs via rexec, inetd, or by direct socket + connects. These capabilities were included to allow users to + access databases or custom program interfaces.</p> + + <p>A subsequent version of Lynx incorporated the World Wide Web + libraries to allow access to the full list of WWW servers, along + with the option to build hypertext documents in HTML, rather than + the native Lynx format. HTML has become far more widely used, and + the native format has been phased out. With the addition of the + WWW libraries, Lynx became a fully-featured WWW client, limited + only by the display capabilities offered in the curses + environment.</p> + + <p>Lynx was designed by Lou Montulli, Charles Rezac and Michael + Grobe of Academic Computing Services at The University of Kansas. + Lynx was implemented by Lou Montulli and maintained by Garrett + Arch Blythe and Craig Lavender.</p> + + <p><em>Foteos Macrides</em> and members of the <a href= + "lynx-dev.html">lynx-dev</a> list have developed and supported + Lynx since release of v2.3 in May 1994.<br> + The Lynx2-3FM code set was released as v2.4 in June 1995.<br> + The Lynx2-4FM code set was released as v2.5 in May 1996.<br> + The Lynx2-5FM code set was released as v2.6 in September + 1996.<br> + The Lynx2-6FM code set was released as v2.7 in February 1997.<br> + The v2-7FM code set was released as v2.7.1 in April 1997.<br> + The v2-7-1FM code set was released as v2.7.2 in January 1998.<br> + The 2.7.1 development set was released as v2.8 in March 1998.<br> + The 2.8 development set was released as v2.8.1 in October + 1998.<br> + The 2.8.1 development set was released as v2.8.2 in June + 1999.<br> + The 2.8.2 development set was released as v2.8.3 in April + 2000.<br> + The 2.8.3 development set was released as v2.8.4 in July + 2001.<br> + The 2.8.4 development set was released as v2.8.5 in February + 2004.<br> + The 2.8.5 development set was released as v2.8.6 in October + 2006.<br> + The 2.8.6 development set was released as v2.8.7 in July + 2009.<br></p> + + <p>Since early 1997, the Lynx code has expanded into + autoconfigure and PC versions. The branching of the Lynx source + base from a single source into two sources (FM/Foteos Macrides + and ac/autoconfigure) should be considered a healthy synergism + among groups of computer professionals acting in their spare time + out of a common goal.</p> + + <p>Lynx has incorporated code from a variety of sources along the + way. The earliest versions of Lynx included code from Earl Fogel + of Computing Services at the University of Saskatchewan, who + implemented HYPERREZ in the Unix environment. Those versions also + incorporated libraries from the Unix Gopher clients developed at + the University of Minnesota, and the later versions of Lynx rely + on the WWW client library code developed by Tim Berners-Lee (and + others) and the WWW community.</p> + + <p>Contributors have generally been acknowledged in the CHANGES + file. Earlier CHANGES file can be found in the docs/ subdirectory + of this distribution.</p> + + <p>Information on obtaining the most current version of Lynx is + available at <a href="http://lynx.isc.org/current/index.html">the + current distribution page</a>.</p> + + <p>[<a href="#Contents">ToC</a>]</p> +</body> +</html> diff --git a/lynx_help/about_lynx.html b/lynx_help/about_lynx.html new file mode 100644 index 00000000..4243bb43 --- /dev/null +++ b/lynx_help/about_lynx.html @@ -0,0 +1,108 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: about_lynx.html,v 1.16 2012/01/31 10:51:52 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>About Lynx</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <blockquote> + [ <a href="lynx-dev.html">About Lynx-Dev</a> | <a href= + "http://mail.gnu.org/mailman/listinfo/lynx-dev/">Lynx-Dev + Archives</a> ] + </blockquote> + + <h1><em>About Lynx</em></h1> + + <p>Lynx is a fully-featured <em>World Wide Web</em> + (<em>WWW</em>) browser for users on Unix, VMS, and other + platforms running cursor-addressable, character-cell terminals or + emulators. That includes vt100 terminals, other character-cell + displays, and vt100 emulators such as Kermit or Procomm running + on PCs or Macs.</p> + + <p>For information on how to use Lynx see the <a href= + "Lynx_users_guide.html">Lynx User's Guide</a>, or the <a href= + "lynx_help_main.html">Lynx help files</a>.</p> + + <h2><em>Credits and Copyright</em></h2> + + <p>Lynx was a product of the Distributed Computing Group within + Academic Computing Services of <a href= + "http://www.cc.ukans.edu/">The University of Kansas</a>.</p> + + <p>Lynx was originally developed by <a href= + "http://www.cc.ukans.edu/cwis/people/Lou.Montulli.html">Lou + Montulli</a>, <a href="http://www.cc.ku.edu/~grobe/">Michael + Grobe</a>, and <a href= + "http://www.cc.ukans.edu/cwis/people/Charles.Rezac.html">Charles + Rezac</a>. <a href= + "http://www.cc.ukans.edu/cwis/people/Garrett/Garrett_Arch_Blythe.html"> + Garrett Blythe</a> created <a href= + "http://www.cc.ukans.edu/about_doslynx/doslynx.html">DosLynx</a> + and later joined the Lynx effort as well. Following the + departures of Lou and Garrett for positions at Netscape in the + summer of 1994, <em>Craig Lavender</em> provided support services + for Lynx, and <em>Ravikumar Kolli</em> for DosLynx.</p> + + <p>Lynx is maintained and supported by members of the Internet + community coordinated via the <a href= + "#lynx-dev_list"><em>lynx-dev mailing list</em></a>.</p> + + <p>Lynx is derived from material copyrighted by the University of + Kansas. However most of the release (and corresponding copyright) + is the work of developers on the <a href= + "#lynx-dev_list"><em>lynx-dev mailing list</em></a>. It is + distributed <a href="COPYHEADER">without restrictions on usage or + redistribution</a> under the <a href="COPYING">GNU General Public + License (Version 2)</a>.</p> + + <p>Lynx was built over an early version of the Common Code + Library developed by the CERN WWW Project. That code is + copyrighted by CERN. Lynx contains other sections of code that + are copyrighted by other institutions or individuals. The Lynx + copyright does not override or invalidate those copyrights.</p> + + <p>Thanks to <a name="13" href= + "http://www.w3.org/People/Berners-Lee/">Tim Berners-Lee</a> and + the other <a name="14" href="http://www.w3.org/People.html">CERN + World Wide Web wizards</a> for the WWW client library code and + all of their other work on the WWW project, NCSA and the <a href= + "http://archive.ncsa.uiuc.edu/SDG/Software/Mosaic/NCSAMosaicHome.html"> + Mosaic</a> developers, and to everyone out in netland who has + contributed to Lynx's development either directly (through + comments or bug reports) or indirectly (through inspiration and + development of other systems).</p> + + <p>Also, special thanks go to <em>Foteos Macrides</em> who ported + much of Lynx to VMS and did much of its development following Lou + Montulli's and Garrett Blythe's departures from the University of + Kansas, and to <em>Earl Fogel</em> of the University of + Saskatchewan. Earl implemented the hypertext engine HYPERREZ in + the Unix environment. HYPERREZ was developed by Niel Larson of + Think.com and served as the model for the early versions of Lynx + which did not use the WWW libraries and had their own hypertext + format.</p> + + <h2><a name="availability"><em>Availability</em></a></h2> + + <p>Information on obtaining the most current version of Lynx is + available via <a href="http://www.subir.com/lynx.html">Lynx + links</a>.</p> + + <h2><a name="lynx-dev_list"><em>Mailing List</em></a></h2> + + <p>We have a mailing list for lynx development discussion. If you + are interested in joining the list, follow this <a href= + "lynx-dev.html">link</a>. There also are links to <a href= + "http://mail.gnu.org/mailman/listinfo/lynx-dev/">archives</a> in + html format for this mailing list.</p> +</body> +</html> diff --git a/lynx_help/help_files.txt b/lynx_help/help_files.txt new file mode 100644 index 00000000..326ddbd4 --- /dev/null +++ b/lynx_help/help_files.txt @@ -0,0 +1,38 @@ +# $LynxId: help_files.txt,v 1.12 2012/01/31 10:52:22 tom Exp $ +# +# Format: +# KEYWORD=<filename>.html +# No space is allowed. +# +# Usage: +# ... href="@KEYWORD@">whatever keyword says</a> +# ... href="@KEYWORD@#section>...</a> +# ... href="../@KEYWORD#section>...</a> +# +# Help files which are used in Lynx's help directory. +# Each filename has to end with '.html' otherwise install-help will fail. +# +ABOUT_LYNX=about_lynx.html +ALT_EDIT_HELP=alt_edit_help.html +BASHLIKE_EDIT_HELP=bashlike_edit_help.html +BOOKMARK_HELP=bookmark_help.html +COOKIE_HELP=cookie_help.html +DIRED_HELP=dired_help.html +EDIT_HELP=edit_help.html +ENVIRONMENTS=environments.html +FOLLOW_HELP=follow_help.html +GOPHER_TYPES_HELP=gopher_types_help.html +HISTORY_HELP=history_help.html +KEYSTROKE_HELP=keystroke_help.html +LYNX_HELP_MAIN=lynx_help_main.html +LYNX_URL_SUPPORT=lynx_url_support.html +LYNX_USERS_GUIDE=Lynx_users_guide.html +MOVEMENT_HELP=movement_help.html +OPTION_HELP=option_help.html +OTHER_HELP=other_help.html +PRINT_HELP=print_help.html +SCROLLING_HELP=scrolling_help.html +TEST_DISPLAY=test_display.html +VISITED_HELP=visited_help.html +XTERM_HELP=xterm_help.html +LYNX_DEV=lynx-dev.html diff --git a/lynx_help/keystrokes/alt_edit_help.html b/lynx_help/keystrokes/alt_edit_help.html new file mode 100644 index 00000000..690537a0 --- /dev/null +++ b/lynx_help/keystrokes/alt_edit_help.html @@ -0,0 +1,78 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: alt_edit_help.html,v 1.9 2012/01/31 23:22:53 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Line Editor Alternative Key Binding</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <link rel="Sibling" title="Default Binding" href= + "edit_help.html"> + <link rel="Sibling" title="Bash-Like Binding" href= + "bashlike_edit_help.html"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>ALTERNATIVE BINDING</h1> + + <p>Lynx invokes a built-in <em>Line Editor</em> for entering + strings in response to prompts, in forms, and for email messages + if an external editor has not been defined. Additional + alternative key-bindings can be offered by configuring with + --enable-alt-bindings or by adding them in LYEditmap.c before + compiling Lynx. If available, they may be selected via the + 'o'ptions menu, or by editing lineedit_mode in the '.lynxrc' + file.</p> + + <p>Note: setting emacs/vi keys ON has no direct effect on + line-editor bindings.</p> + + <p>This is the <em>Alternative Binding</em> keymap:</p> + <pre> + ENTER Input complete - RETURN + TAB Input complete - TAB, Do + ABORT Input cancelled - Ctrl-G, Ctrl-O, (Ctrl-C on some systems) + ERASE Erase the line - Ctrl-U + + BACK Cursor back char - Left-Arrow, Ctrl-B + FORW Cursor forward char - Right-Arrow, Ctrl-F + BACKW Cursor back word - Ctrl-P + FORWW Cursor forward word - Ctrl-N + BOL Go to begin of line - Ctrl-A, Home, Find + EOL Go to end of line - Ctrl-E, End, Select + + DELP Delete prev char - Ctrl-H, DELETE, Remove + DELN Delete next [1] char - Ctrl-D + DELPW Delete prev word - Ctrl-R + DELNW Delete next word - Ctrl-T + DELEL Delete to end of line - Ctrl-K + + UPPER Upper case the line - Ctrl-^ + LOWER Lower case the line - Ctrl-_ + + LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) [2] + +<a name= +"TASpecial">Special commands for use only in textarea fields</a>[3]: + + Textarea external edit - Ctrl-X e + Insert file in textarea - Ctrl-X i + Grow textarea - Ctrl-X g + +[1] "next" means the character "under" a box or underline style cursor; it + means "to the immediate right of" an I-beam (between characters) type + cursor. + +[2] Follow Ctrl-V with any recognized key command, to "escape" from a text + input field. + +[3] For other key combinations using Ctrl-X as a prefix key, see the + Help page for the <a rel="Sibling" title="Bash-Like Binding" +href="bashlike_edit_help.html">Bash-Like</a> Binding. +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/bashlike_edit_help.html b/lynx_help/keystrokes/bashlike_edit_help.html new file mode 100644 index 00000000..14a3a4ff --- /dev/null +++ b/lynx_help/keystrokes/bashlike_edit_help.html @@ -0,0 +1,237 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: bashlike_edit_help.html,v 1.8 2012/01/31 23:21:55 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Line Editor Bash-Like Key Binding</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <link rel="Sibling" title="Default Binding" href= + "edit_help.html"> + <link rel="Sibling" title="Alternative Binding" href= + "alt_edit_help.html"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>BASH-LIKE BINDING</h1> + + <p>Lynx invokes a built-in <em>Line Editor</em> for entering + strings in response to prompts, in forms, and for email messages + if an external editor has not been defined. Several sets of + key-bindings can be offered by configuring with + --enable-alt-bindings or by adding them in LYEditmap.c before + compiling Lynx. If available, they may be selected via the + 'o'ptions menu, or by editing lineedit_mode in the '.lynxrc' + file.</p> + + <p>Note: setting emacs/vi keys ON has no direct effect on + line-editor bindings.</p> + + <p>This is the <em>Bash-like Binding</em> keymap.</p> + + <h2>Basic commands</h2> + <pre> + ENTER Input complete - Enter, RETURN + TAB Completion [2]/ Next - TAB, Do + ABORT Cancel / Undo Change - C-g, C-_ + ERASE Erase the line - M-k, C-x k + + BACK Cursor back char - Left-Arrow, C-b + FORW Cursor forward char - Right-Arrow, C-f + BACKW Cursor back word - M-b, C-r + FORWW Cursor forward word - M-f, C-s [5] + BOL Go to begin of line - C-a, Home, Find + EOL Go to end of line - C-e [4], End, Select + + DELP Delete prev char - C-h, Backspace, Rubout + DELN Delete next [1] char - C-d, Delete, Remove + DELPW Delete prev word - C-w [3], M-Backspace, M-Delete (?) + DELNW Delete next word - M-d + DELBL Delete to beg of line - C-u + DELEL Delete to end of line - C-k [4] + + UPPER Upper case the line - M-u + LOWER Lower case the line - M-l + + LKCMD Invoke cmd prompt - C-v [FORM] + SWMAP Switch input keymap - C-^ (if compiled in) + +<a name= +"TASpecial">Special commands for use in textarea fields</a> [FORM]: + + PASS! Textarea external edit - C-e C-e [4], C-x e + PASS! Insert file in textarea - C-x i + PASS! Grow textarea - C-x g +</pre> + + <p>Here is a little textarea for practice:<br></p> + + <form action=""> + <textarea name="practice" cols="40" rows="5"> +This text cannot be submitted. Normally lines like +these would be part of a form that is filled out and +then submitted. You can move around here and delete +or add text as you like, using the Line-Editor keys. +</textarea><input type="reset" value="[reset content]"> + </form> + <pre> + +Advanced emacs-like commands: + + TPOS Transpose characters - C-t + SETMARK Set mark at current position in line - C-@ + XPMARK Exchange current position with mark - C-x C-x + KILLREG Kill region between mark and position - C-x C-w [3] + YANK Insert text last killed (with KILLREG) - C-y +</pre> + + <h2>Notes</h2> + + <p><samp><dfn>C-</dfn><strong>key</strong> means + Control+<strong><kbd>key</kbd></strong>. + <dfn><code>C-x</code></dfn> <strong>key</strong> means first + Control+<kbd>x</kbd>, then <strong><kbd>key</kbd></strong>. + <dfn>M-</dfn>key means Meta+<strong><kbd>key</kbd></strong>, + where Meta is a modifier that can be entered in a variety of + ways:</samp></p> + + <ul> + <li>First ESC, then the <strong><kbd>key</kbd></strong>. This + doesn't work with all systems or on all connections, and if it + does may not work for some keys (because the ESC character is + also part of code sequences for "normal" function keys).</li> + + <li>Alt+<strong><kbd>key</kbd></strong>. This works if the + terminal, console, or comm program is set up to interpret Alt + as a modifier to send ESC. The Linux console acts like that by + default for most keys; Kermit can be set up to do it, xterm can + be for some keys, and so on. But the same caveats as for the + previous item apply. This Alt mapping may also be possible, + independent of the ESC character, for some keys in Lynx for + DOS/i386 or for Win32.</li> + + <li>C-x <strong><kbd>key</kbd></strong>. Actually, currently + the same internal table is used for Meta and the C-x prefix. + Therefore all M-<strong><kbd>key</kbd></strong> combinations + can also be typed as C-x <strong><kbd>key</kbd></strong>, and + vice versa.</li> + </ul> + <pre> +[1] "next" means the character "under" a box or underline style cursor; it + means "to the immediate right of" an I-beam (between characters) type + cursor. +[2] For entering strings in response to prompts (that is, when not editing + form text fields), some keys have different actions: TAB tries to + complete input based on previous response; Up-Arrow and Down-Arrow + may offer previous response and next response, respectively, from + recall buffer for some prompts. +[3] C-w can only be used for editing functions if its default KEYMAP + to REFRESH is changed. This can be done in the lynx.cfg file, + for example with the line "KEYMAP:^W:DO_NOTHING". This also applies + for other keys: as long as the key's action is mapped to REFRESH, + either with an explicit KEYMAP in lynx.cfg or by default, the + key's Line Editor binding is disabled. +[4] These keys invoke special behavior when pressed twice in a row: + C-e C-e calls the external editor for changing the text in a + textarea (if available). C-k C-k will move to the next link, + so that all lines in a textarea can be conveniently cleared by + repeating C-k. +[5] Key is likely unavailable for Lynx, because it is interpreted by + operating system, comm program, or curses library, or swallowed + as part of escape sequence recognition. Binding is provided for + the benefit of those where this doesn't apply. +[FORM] In form text fields, only. Ignored by Line Editor elsewhere. + +More notes + + When a text input field, including a textarea line, is selected, + the Line Editor functions get a first grab at the keys entered. + If a key has no function defined in the Line Editor binding, it + can either be ignored, or passed on for normal key command handling, + where modifiers like C-x or Meta currently have no effect (see the + <a href= +"LYNXKEYMAP:">Key Map Page</a> accessible with the key <kbd>K</kbd> for current information). +</pre> + + <h2>Additional details on other keys, for the curious (very much + subject to change)</h2> + <pre> +Normal key action when used in form fields, subject to remapping +with KEYMAP: [FORM (except Up-Arrow, Down-Arrow)] + C-l [3], C-o, C-z [5], C-\ [5], C-] [5] + C-n [emacskey], C-p [emacskey] + Up-Arrow [2], Down-Arrow [2] + Page-Up, Page-Down, F1, Back-Tab + +Normal key command with Meta modifier ignored when used in form fields, +subject to remapping with KEYMAP: [FORM (except Up-Arrow, Down-Arrow)] + M-C-l [3], M-C-o [!], M-C-z [5], M-C-\ [5], M-C-] [5] + M-C-u, M-/, M-n + M-Up-Arrow [2][!], M-Down-Arrow [2][!] + M-Page-Up [!], M-Page-Down [!], M-Home, M-End + +Passed as specific command: + lynx action duplicates by default + ----------- --------------------- + M-C-d NEXT_LINK Down-Arrow + M-C-e EDITTEXTAREA C-e C-e + M-C-k LPOS_NEXT_LINK (none, Down-Arrow suggested) + M-e EDITTEXTAREA C-e C-e + M-g GROWTEXTAREA (none, C-v $ suggested?) + M-i INSERTFILE (none, C-v # suggested?) + M-< HOME M-Home + M-> END M-End + M-F1 DWIMHELP F1 + M-Find WHEREIS C-v / + M-Select NEXT C-v n + +Duplicates function of other key(s): + edit action duplicates + ----------- ---------- + M-C-b BACKW M-b, C-r + M-C-f FORWW M-f + M-C-n FORWW M-f + M-C-p BACKW M-b, C-r + M-C-r BACKW M-b, C-r + M-a BOL C-a, Home, ... + +Modifier ignored, and duplicates function of other key(s): + edit action duplicates + ----------- ---------- + M-C-a BOL C-a, Home, ... + M-C-g ABORT C-g, ... + M-TAB TAB C-i [!] + M-C-j ENTER C-m, C-j, Enter / RETURN + M-RETURN ENTER C-m, C-j, Enter / RETURN + M-C-y YANK C-y [!] + M-C-^ SWMAP C-^ [!] (if compiled in) + M-Right-Arrow FORW Right-Arrow [!], C-f + M-Left-Arrow BACK Left-Arrow [!], C-b + M-Do TAB C-i [!] + +Key completely ignored: + C-q, Insert + M-C-q, M-C-s [5], M-C-t, M-C-v, M-ESC + M-C-@, M-C-_, M-Remove, M-Insert [!] + +Meta + other (mostly, printable character) keys: + Modifier ignored, or sequence swallowed (see [5]). + M-@, M-E...M-Z [5], M-\, M-^, M-_ attempt to interpret + as 7-bit escape representation for character in 8-bit + control (C1) range if appropriate according to + Display Character Set. + +[emacskey] Normal key action subject to emacs_keys setting. + +[!] Action of key with Meta modifier follows action of key without + Meta. If you manage to enter the Meta key while Line-Editor + Binding is not set to Bash-Like, and the unmodified binding + is different from that listed here, M-<<var>key</var>> will act + like <<var>key</var>>. +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/bookmark_help.html b/lynx_help/keystrokes/bookmark_help.html new file mode 100644 index 00000000..df5adad1 --- /dev/null +++ b/lynx_help/keystrokes/bookmark_help.html @@ -0,0 +1,38 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: bookmark_help.html,v 1.6 2012/01/31 11:00:10 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Bookmark Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Bookmark Help</h1> + + <p><em>Bookmark files</em> are documents that reside on your + local machine and you are able to edit and change:</p> + + <ul> + <li>The append feature, invoked by pressing an '<em>a</em>' + while viewing a document will add the current document or the + currently highlighted link to your default <em>Bookmark + file</em>, or to one you select if multiple bookmarks are + enabled.</li> + + <li>The remove feature, invoked by pressing an '<em>r</em>' + when a <em>Bookmark file</em> is being displayed, will remove + the currently highlighted link.</li> + + <li>You may set and modify the paths and names of your + <em>Bookmark files</em> and enable or disable multiple + bookmarks in the <a href="option_help.html">Options + Menu</a>.</li> + </ul> +</body> +</html> diff --git a/lynx_help/keystrokes/cookie_help.html b/lynx_help/keystrokes/cookie_help.html new file mode 100644 index 00000000..ad4c4240 --- /dev/null +++ b/lynx_help/keystrokes/cookie_help.html @@ -0,0 +1,60 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: cookie_help.html,v 1.7 2012/01/31 23:19:37 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on the Cookie Jar Page</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Cookie Jar Page Help</h1> + + <p>The Cookie Jar Page displays all of the unexpired cookies you + have accumulated in the hypothetical <em>Cookie Jar</em>. The + cookies are obtained via <em>Set-Cookie</em> MIME headers in + replies from http servers, and are used for <a href= + "../Lynx_users_guide.html#Cookies">State Management</a> across + successive requests to the servers.</p> + + <p>The cookies are listed by <em>domain</em> (server's Fully + Qualified Domain Name, or site-identifying portion of the FQDN), + and in order of decreasing specificity (number of slash-separated + symbolic elements in the <em>path</em> attribute of the cookie). + When Lynx sends requests to an http server whose address + tail-matches a <em>domain</em> in the <em>Cookie Jar</em>, all + its cookies with a <em>path</em> which head-matches the path in + the URL for that request are included as a <em>Cookie</em> MIME + header. The 'allow' setting for accepting cookies from each + domain (always, never, or via prompt) also is indicated in the + listing.</p> + + <p>The listing also shows the <em>port</em> (normally 80) of the + URL for the request which caused the cookie to be sent, and + whether the <em>secure</em> flag is set for the cookie, in which + case it will be sent only via secure connections (presently, only + SSL). The <em>Maximum Gobble Date</em>, i.e., when the cookie is + intended to expire, also is indicated. Also, a server may change + the expiration date, or cause the cookie to be deleted, in its + replies to subsequent requests from Lynx. If the server included + any explanatory comments in its <em>Set-Cookie</em> MIME headers, + those also are displayed in the listing.</p> + + <p>The <em>domain</em>=value pairs, and each cookie's name=value, + are links in the listing. Activating a <em>domain</em>=value link + will invoke a prompt asking whether all cookies in that + <em>domain</em> should be <em>Gobbled</em> (deleted from the + <em>Cookie Jar</em>), and/or whether the <em>domain</em> entry + should be <em>Gobbled</em> if all of its cookies have been + <em>Gobbled</em>, or whether to change the 'allow' setting for + that <em>domain</em>. Activating a cookie's name=value link will + cause that particular cookie to be <em>Gobbled</em>. You will be + prompted for confirmations of deletions, to avoid any accidental + <em>Gobbling</em>.</p> +</body> +</html> diff --git a/lynx_help/keystrokes/dired_help.html b/lynx_help/keystrokes/dired_help.html new file mode 100644 index 00000000..a692c1b9 --- /dev/null +++ b/lynx_help/keystrokes/dired_help.html @@ -0,0 +1,62 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: dired_help.html,v 1.7 2012/01/31 23:19:02 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Dired Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>DIRED HELP</h1> + + <p>Lynx changes into Dired mode when you use a URL of the type + <em>file://localhost/path/</em>. While in Dired mode, some keys + are remapped to do the following functions:</p> + <pre> + + C)reate - Create a new, empty file in the current + directory. You will be prompted to enter + a name for the file. + + F)ull menu - Show a full menu of commands for currently + selected file or directory. + + M)odify - Modify the name or location of selection. If + multiple files have been selected, you will + only be able to change the location. Choose + between changing the name or location and then + enter a new filename or path. + + R)emove - Delete currently selected files. + + T)ag - Tag the highlighted file. Multiple files may + be tagged and all other commands except "Create" + will be performed on tagged files instead of the + one highlighted. Press '<em>t</em>' again to untag + a file. + + U)pload - Upload a file to the current directory using + one of the options listed in the upload screen. +</pre> + + <p>Some other keys useful in Dired mode:</p> + <pre> + D)ownload - Download selection using options listed in + the download options screen. + + E)dit - Spawn the editor defined in the <a href= +"option_help.html">Options Menu</a> + and load selection for editing. +</pre> + + <p><em>Note:</em> Dired mode must be activated at compile time. + Otherwise, the above commands will not be available and Lynx will + treat a directory listing as an HTML file.</p> +</body> +</html> diff --git a/lynx_help/keystrokes/edit_help.html b/lynx_help/keystrokes/edit_help.html new file mode 100644 index 00000000..d18eb255 --- /dev/null +++ b/lynx_help/keystrokes/edit_help.html @@ -0,0 +1,79 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: edit_help.html,v 1.13 2012/01/31 23:17:33 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Line Editor Default Key Binding</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>DEFAULT BINDING</h1> + + <p>Lynx invokes a built-in <em>Line Editor</em> for entering + strings in response to prompts, in forms, and for email messages + if an external editor has not been defined. Alternative key + bindings can be offered by configuring with --enable-alt-bindings + or by adding them in LYEditmap.c before compiling Lynx. If + available, they may be selected via the 'o'ptions menu, or by + editing lineedit_mode in the '.lynxrc' file.</p> + + <p>Two such alternative key bindings, which may be available on + your system, are the <a href="alt_edit_help.html">Alternative + Binding</a> keymap and the <a href= + "bashlike_edit_help.html">Bash-like Binding</a> keymap.</p> + + <p>Note: setting emacs/vi keys ON has no effect on line-editor + bindings.</p> + + <p>This is the <em>Default Binding</em> keymap:</p> + <pre> + ENTER Input complete - RETURN + TAB Input complete - TAB, Do + ABORT Input cancelled - Ctrl-G, Ctrl-O, (Ctrl-C on some systems) + ERASE Erase the line - Ctrl-U + + BACK Cursor back char - Left-Arrow + FORW Cursor forward char - Right-Arrow + BACKW Cursor back word - Ctrl-P + FORWW Cursor forward word - Ctrl-N + BOL Go to begin of line - Ctrl-A, Home, Find + EOL Go to end of line - Ctrl-E, End, Select + + DELP Delete prev char - Ctrl-H, DELETE, Remove + DELN Delete next [1] char - Ctrl-D, Ctrl-R + DELPW Delete prev word - Ctrl-B + DELNW Delete next word - Ctrl-F + DELEL Delete to end of line - Ctrl-_ + + UPPER Upper case the line - Ctrl-T + LOWER Lower case the line - Ctrl-K + + LKCMD Invoke cmd prompt - Ctrl-V (in form text fields, only) [2] + SWMAP Switch input keymap - Ctrl-^ (if compiled in) + +<a name= +"TASpecial">Special commands for use only in textarea fields</a>[3]: + + Textarea external edit - Ctrl-X e + Insert file in textarea - Ctrl-X i + Grow textarea - Ctrl-X g + +[1] "next" means the character "under" a box or underline style cursor; it + means "to the immediate right of" an I-beam (between characters) type + cursor. + +[2] Follow Ctrl-V with any recognized key command, to "escape" from a text + input field. + +[3] For other key combinations using Ctrl-X as a prefix key, see the + Help page for the <a rel="Sibling" title="Bash-Like Binding" +href="bashlike_edit_help.html">Bash-Like</a> Binding. +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/environments.html b/lynx_help/keystrokes/environments.html new file mode 100644 index 00000000..c6988b0c --- /dev/null +++ b/lynx_help/keystrokes/environments.html @@ -0,0 +1,480 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: environments.html,v 1.14 2012/01/31 23:25:10 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on Environment variables</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <pre> + +<em>ENVIRONMENT</em> + In addition to various "standard" environment variables + such as HOME, PATH, USER, DISPLAY, TMPDIR, etc, Lynx utilizes + several Lynx-specific environment variables, <a href= +"#env">if they exist</a>. + + Others may be created or modified by Lynx to pass data to + an external program, or for other reasons. These are + listed separately <a href="#setenv">below</a>. + + See also the sections on <a href= +"#cgi">SIMULATED CGI SUPPORT</a> and + <a href="#language">NATIVE LANGUAGE SUPPORT</a>, below. + + Note: Not all environment variables apply to all types of + platforms supported by Lynx, though most do. Feedback on + platform dependencies is solicited. See also <a href= +"#dos">win32/dos</a> specific + variables. + +<a name="env"><em> +Environment Variables Used By Lynx: +</em></a> + COLORTERM + If set, color capability for the terminal + is forced on at startup time. The actual + value assigned to the variable is ignored. + This variable is only meaningful if Lynx + was built using the slang screen-handling + library. + + LYNX_CFG + This variable, if set, will override + the default location and name of the + global configuration file (normally, + lynx.cfg) that was defined by the + LYNX_CFG_FILE constant in the + userdefs.h file, during installation. + See the userdefs.h file for more + information. + + LYNX_HELPFILE + If set, this variable overrides the + compiled-in URL and configuration file + URL for the lynx help file. + + LYNX_LOCALEDIR + If set, this variable overrides the + compiled-in location of the locale + directory which contains native lan- + guage (NLS) message text. + + LYNX_LSS + This variable, if set, specifies the + location of the default Lynx character + style sheet file. [Currently only + meaningful if Lynx was built using + experimental color style support.] + + LYNX_SAVE_SPACE + This variable, if set, will override + the default path prefix for files + saved to disk that is defined in the + lynx.cfg SAVE_SPACE: statement. See + the lynx.cfg file for more information. + + LYNX_TEMP_SPACE + This variable, if set, will override + the default path prefix for temporary + files that was defined during installation, + as well as any value that may + be assigned to the TMPDIR variable. + + LYNX_TRACE + If set, causes Lynx to write a trace + file as if the -trace option were sup- + plied. + + LYNX_TRACE_FILE + If set, overrides the compiled-in name + of the trace file, which is either + Lynx.trace or LY-TRACE.LOG (the latter + on the DOS platform). The trace file + is in either case relative to the home + directory. + + MAIL + This variable specifies the default + inbox Lynx will check for new mail, if + such checking is enabled in the + lynx.cfg file. + + NEWS_ORGANIZATION + This variable, if set, provides the + string used in the Organization: + header of USENET news postings. It will + override the setting of the ORGANIZATION + environment variable, if it is also set + (and, on UNIX, the contents of an + /etc/organization file, if present). + + NNTPSERVER + If set, this variable specifies the + default NNTP server that will be used + for USENET news reading and posting + with Lynx, via news: URL's. + + ORGANIZATION + This variable, if set, provides the + string used in the Organization: + header of USENET news postings. On + UNIX, it will override the contents of + an /etc/organization file, if present. + + PROTOCOL_proxy + Lynx supports the use of proxy servers + that can act as firewall gateways and + caching servers. They are preferable + to the older gateway servers (see + WWW_access_GATEWAY, below). + Each protocol used by Lynx (http, ftp, + gopher, etc), can be mapped separately + by setting environment variables of + the form PROTOCOL_proxy (literally: + http_proxy, ftp_proxy, gopher_proxy, + etc), to "http://some.server.dom:port/". + See <a href= +"#proxy">Proxy details and examples</a>. + + WWW_access_GATEWAY + Lynx still supports use of gateway + servers, with the servers specified + via "WWW_access_GATEWAY" variables + (where "access" is lower case and can + be "http", "ftp", "gopher" or "wais"), + however most gateway servers have been + discontinued. Note that you do not + include a terminal '/' for gateways, + but do for proxies specified by PROTOCOL_proxy + environment variables. See <a href= +"#proxy">Proxy details</a>. + + WWW_HOME + This variable, if set, will override + the default startup URL specified in + any of the Lynx configuration files. + +<a name="setenv"><em> +Environment Variables Set or Modified By Lynx: +</em></a> + + LYNX_PRINT_DATE This variable is set by the Lynx + p(rint) function, to the Date: string + seen in the document's "Information + about" page (= cmd), if any. It is + created for use by an external program, + as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or "No Date" under VMS. + + LYNX_PRINT_LASTMOD This variable is set by the Lynx + p(rint) function, to the Last Mod: + string seen in the document's "Information + about" page (= cmd), if any. + It is created for use by an external + program, as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or "No LastMod" under VMS. + + LYNX_PRINT_TITLE This variable is set by the Lynx + p(rint) function, to the Linkname: + string seen in the document's "Information + about" page (= cmd), if any. + It is created for use by an external + program, as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or "No Title" under VMS. + + LYNX_PRINT_URL This variable is set by the Lynx + p(rint) function, to the URL: string + seen in the document's "Information + about" page (= cmd), if any. It is + created for use by an external program, + as defined in a lynx.cfg + PRINTER: definition statement. If the + field does not exist for the document, + the variable is set to a null string + under UNIX, or "No URL" under VMS. + + LYNX_VERSION This variable is always set by Lynx, + and may be used by an external program + to determine if it was invoked by + Lynx. See also the comments in the + distribution's sample mailcap file, + for notes on usage in such a file. + + SSL_CERT_DIR Set to the directory containing trusted + certificates. + + SSL_CERT_FILE Set to the full path and filename for + your file of trusted certificates. + + TERM Normally, this variable is used by + Lynx to determine the terminal type + being used to invoke Lynx. If, however, + it is unset at startup time (or + has the value "unknown"), or if the + -term command-line option is used, + Lynx will set or modify its value + to the user specified terminal type + (for the Lynx execution environment). + Note: If set/modified by Lynx, the values of + the LINES and/or COLUMNS environment + variables may also be changed. + + +<a name="cgi"><em> +SIMULATED CGI SUPPORT +</em></a> + If built with the cgi-links option enabled, Lynx allows + access to a cgi script directly without the need for an + http daemon. + + When executing such "lynxcgi scripts" (if enabled), the + following variables may be set for simulating a CGI environment: + + CONTENT_LENGTH + + CONTENT_TYPE + + DOCUMENT_ROOT + + HTTP_ACCEPT_CHARSET + + HTTP_ACCEPT_LANGUAGE + + HTTP_USER_AGENT + + PATH_INFO + + PATH_TRANSLATED + + QUERY_STRING + + REMOTE_ADDR + + REMOTE_HOST + + REQUEST_METHOD + + SERVER_SOFTWARE + + Other environment variables are not inherited by the + script, unless they are provided via a LYNXCGI_ENVIRONMENT + statement in the configuration file. See the lynx.cfg + file, and the (draft) CGI 1.1 Specification + <http://Web.Golux.Com/coar/cgi/draft-coar-cgi-v11-00.txt> + for the definition and usage of these variables. + + The CGI Specification, and other associated documentation, + should be consulted for general information on CGI script + programming. + +<a name="language"><em> +NATIVE LANGUAGE SUPPORT +</em></a> + If configured and installed with Native Language Support, + Lynx will display status and other messages in your local + language. See the file ABOUT_NLS in the source distribution, + or at your local GNU site, for more information about + internationalization. + + The following environment variables may be used to alter + default settings: + + LANG This variable, if set, will override + the default message language. It is + an ISO 639 two-letter code identifying + the language. Language codes are NOT + the same as the country codes given in + ISO 3166. + + LANGUAGE This variable, if set, will override + the default message language. This is a + GNU extension that has higher priority for + setting the message catalog than LANG or + LC_ALL. + + LC_ALL and + + LC_MESSAGES These variables, if set, specify the + notion of native language formatting + style. They are POSIXly correct. + + LINGUAS This variable, if set prior to configuration, + limits the installed languages to specific values. + It is a space-separated list of two-letter codes. + Currently, it is hard-coded to a wish list. + + NLSPATH This variable, if set, is used as the + path prefix for message catalogs. + +<a name="proxy"><em> +Proxy details and examples: +</em></a> + + To set your site's NTTP server as the default host for news reading + and posting via Lynx, set the environment variable NNTPSERVER so that + it points to its Internet address. The variable "NNTPSERVER" is used + to specify the host which will be used as the default for news URLs. + + UNIX + setenv NNTPSERVER "news.server.dom" + + VMS + define/system NNTPSERVER "news.server.dom" + + Lynx still supports use of gateway servers, with the servers specified + via the variables "WWW_access_GATEWAY", where "access" is lower case + and can be "http", "ftp", "gopher" or "wais". Most of the gateway + servers have been discontinued, but "http://www.w3.org:8001" is + available for wais searches (note that you do not include a + terminal '/' for gateways, but do for proxies; see below). + + Lynx version 2.2 and beyond supports the use of proxy servers that + can act as firewall gateways and caching servers. They are + preferable to the older gateway servers. Each protocol used by + Lynx can be mapped separately using PROTOCOL_proxy environment + variables of the form: + + UNIX + setenv http_proxy "http://some.server.dom:port/" + setenv https_proxy "http://some.server.dom:port/" + setenv ftp_proxy "http://some.server.dom:port/" + setenv gopher_proxy "http://some.server.dom:port/" + setenv news_proxy "http://some.server.dom:port/" + setenv newspost_proxy "http://some.server.dom:port/" + setenv newsreply_proxy "http://some.server.dom:port/" + setenv snews_proxy "http://some.server.dom:port/" + setenv snewspost_proxy "http://some.server.dom:port/" + setenv snewsreply_proxy "http://some.server.dom:port/" + setenv nntp_proxy "http://some.server.dom:port/" + setenv wais_proxy "http://some.server.dom:port/" + setenv finger_proxy "http://some.server.dom:port/" + setenv cso_proxy "http://some.server.dom:port/" + + VMS + define "http_proxy" "http://some.server.dom:port/" + define "https_proxy" "http://some.server.dom:port/" + define "ftp_proxy" "http://some.server.dom:port/" + define "gopher_proxy" "http://some.server.dom:port/" + define "news_proxy" "http://some.server.dom:port/" + define "newspost_proxy" "http://some.server.dom:port/" + define "newsreply_proxy" "http://some.server.dom:port/" + define "snews_proxy" "http://some.server.dom:port/" + define "snewspost_proxy" "http://some.server.dom:port/" + define "snewsreply_proxy" "http://some.server.dom:port/" + define "nntp_proxy" "http://some.server.dom:port/" + define "wais_proxy" "http://some.server.dom:port/" + define "finger_proxy" "http://some.server.dom:port/" + define "cso_proxy" "http://some.server.dom:port/" + (Encase *BOTH* strings in double-quotes to maintain + lower case for the PROTOCOL_proxy variable and for + the http access type; include /system if you want + proxying for all clients on your system.) + + If you wish to override the use of a proxy server for specific hosts or + entire domains you may use the "no_proxy" environment variable. + The no_proxy variable can be a comma-separated list of strings defining + no-proxy zones in the DNS domain name space. If a tail substring of the + domain-path for a host matches one of these strings, transactions with that + node will not be proxied. Here is an example use of "no_proxy": + + UNIX + setenv no_proxy "host.domain.dom, domain1.dom, domain2" + + VMS + define "no_proxy" "host.domain.dom, domain1.dom, domain2" + + You can include a port number in the no_proxy list to override use + of a proxy server for the host accessed via that port, but not via + other ports. For example, if you use "host.domain.dom:119" and/or + "host.domain.dom:210", then news (port 119) URLs and/or any wais + (port 210) searches on that host would be excluded, but http, ftp, + and gopher services (if normally proxied) would still be included, + as would any news or wais services on other hosts. + + Warning: Note that setting 'il' as an entry in this list + will block proxying for the .mil domain as well as the .il domain. + If the entry is '.il' this will not happen. + + If you wish to override the use of a proxy server completely (i.e., + globally override any existing proxy variables), set the value of + "no_proxy" to "*". This is the only allowed use of * in no_proxy. + + Note that Lynx treats file URLs on the local host as requests for + direct access to the file, and does not attempt ftp if that fails. + It treats both ftp URLs and file URLs on remote hosts as ftp URLs, + and does not attempt direct file access for either. If ftp URLs are + being proxied, file URLs on a remote host will be converted to ftp + URLs before submission by Lynx to the proxy server, so no special + procedure for inducing the proxy server to handle them is required. + Other WWW clients may require that the http server's configuration + file have "Map file:* ftp:*" in it to perform that conversion. + + If you have not set NNTPSERVER, proxy or no_proxy environment variables + you can set them at run time via the configuration file lynx.cfg + (this will not override external settings). + +<a name="dos"><em> +Win32 (95/NT) and 386 DOS +</em></a> + (adapted from "readme.txt" by Wayne Buttles + and "readme.dos" by Doug Kaufman) + + Here are some environment variables that should be set, usually in a + batch file that runs the lynx executable. Make sure that you have enough + room left in your environment. You may need to change your "SHELL=" + setting in config.sys. In addition, lynx looks for a "SHELL" environment + variable when shelling to DOS. If you wish to preserve the environment + space when shelling, put a line like this in your AUTOEXEC.BAT file also + "SET SHELL=C:\COMMAND.COM /E:2048". It should match CONFIG.SYS. + + HOME Where to keep the bookmark file and personal config files. + TEMP or TMP Bookmarks are kept here with no HOME. Temp files here. + USER Set to your login name + LYNX_CFG Set to the full path and filename for lynx.cfg + + 386 version only: + WATTCP.CFG Set to the full path for the WATTCP.CFG directory + (Depending on how you compiled libtcp.a, you may have to use WATCONF.) + + Define these in your batch file for running Lynx. For example, if your + application line is "D:\win32\lynx.bat", lynx.bat for Win32 may look like: + @ECHO OFF + set home=d:\win32 + set temp=d:\tmp + set lynx_cfg=d:\win32\lynx.cfg + d:\win32\lynx.exe %1 %2 %3 %4 %5 + + In lynx_386, a typical batch file might look like: + + @echo off + set HOME=f:/lynx2-8 + set USER=your_login_name + set LYNX_CFG=%HOME%/lynx.cfg + set WATTCP.CFG=%HOME% + f:\lynx2-8\lynx %1 %2 %3 %4 %5 %6 %7 %8 %9 + + You will also need to make sure that the WATTCP.CFG file has the + correct information for IP number, Gateway, Netmask, and Domain Name + Server. This can also be automated in the batch file. + + +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/follow_help.html b/lynx_help/keystrokes/follow_help.html new file mode 100644 index 00000000..394b3553 --- /dev/null +++ b/lynx_help/keystrokes/follow_help.html @@ -0,0 +1,187 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!-- $LynxId: follow_help.html,v 1.10 2012/01/31 23:16:38 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on the Follow link (or page) number feature</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Follow link (or goto link or page) number Help<br> + Select option (or page) number Help</h1> + + <p>If a user has set <em>Keypad mode</em> to <em>Links are + numbered</em>, or <em>Form fields are numbered</em>, or <em>Links + and form fields are numbered</em> as the default or for the + current session via the <em>Options menu</em>, then hypertext + links (and form fields, depending on the keypad mode) are + prefixed with numbers in square brackets. Entering a keyboard or + keypad number is treated as an <em>F_LINK_NUM</em> command, and + should invoke the <em>Follow link (or goto link or page) + number:</em> statusline prompt for a potentially multiple digit + number corresponding to an indicated link number. If RETURN is + pressed to terminate the number entry (e.g., <em>123</em>) and it + corresponds to a hypertext link, Lynx will retrieve the document + for that link as if you had paged or used other navigation + commands to make it the current link and then ACTIVATE-ed it. The + prompt can be invoked via '<em>0</em>', but it will not be + treated as the lead digit for the number entry, whereas + '<em>1</em>' through '<em>9</em>' both invoke the prompt and are + treated as the first digit. In <em>Form fields are numbered</em> + or <em>Links and form fields are numbered</em> mode, if the + number corresponds to a form field you will be positioned on that + field, but if it is a submit button it will not be + ACTIVATE-ed.</p> + + <p>If the number entered at the prompt has a '<em>g</em>' suffix + (e.g., <em>123g</em>), then Lynx will make the link corresponding + to that number the current link, paging as appropriate if the + link does not appear in the currently displayed page. The + '<em>g</em>' suffix is inferred (need not be entered) for form + fields in <em>Form fields are numbered</em> or <em>Links and form + fields are numbered</em> mode.</p> + + <p>Alternatively, if the number is given a '<em>p</em>' suffix + (e.g., <em>123p</em>), Lynx will make the page corresponding to + that number the currently displayed page, and the first link on + that page, if any, the current link. The '<em>g</em>' and + '<em>p</em>' suffixes thus convert the <em>Follow link (or goto + link or page) number:</em> feature to an advanced navigation + aid.</p> + + <p>Finally, a user may add a <em>+</em> or <em>-</em> suffix to a + number command to indicate jumping forward or back relative to + the current link or page. For example, typing <em>1g+</em> + followed by RETURN will move the current link to the next + numbered link, skipping any intervening pages or unnumbered + links; <em>1g-</em> goes to the preceding numbered link. On a + page without links, <em>3g+</em> goes to the 3rd link + <em>following</em> the page. <em>5p+</em> skips ahead 5 pages, + and so on. You can also enter <em>5+</em> or <em>5-</em>, which + will activate the 5th link ahead/behind where you are currently + positioned. Note that typing <em>1g+</em> is different from + typing a down arrow in that <em>1g+</em> skips pages containing + no links, or intervening non-numbered links, such as form fields + when form fields are not numbered. It also differs from the + <em><tab></em> command in that <em>1g+</em> does not skip + over whole textareas, unless form fields are not numbered.</p> + + <p><em>NOTE:</em> <em>1+g 1-g 1+p 1-p</em> are all recognized as + equivalent to <em>1g+ 1g- 1p+ 1p-</em> . Any other (mistyped) + characters end the formula: e.g. <em>1gh+</em> is treated as + <em>1g</em>.</p> + + <p>If the user has set <em>Keypad mode</em> to <em>Numbers act as + arrows</em>, then only '<em>0</em>', rather than every number, + will be treated as an <em>F_LINK_NUM</em> command for invoking + the <em>Follow link (or goto link or page) number:</em> prompt. + The '<em>0</em>' will not be treated as the first digit for the + number, or number plus suffix, entry.</p> + + <p>Numbers are associated with form fields only when <em>Form + fields are numbered</em> or <em>Links and form fields are + numbered</em> mode has been selected. If you have selected + <em>Numbers act as arrows</em> or <em>Links are numbered</em> + mode, you can seek form fields in the document via WHEREIS + searches for strings in their displayed values. If they are INPUT + or TEXTAREA fields with no values as yet, you can use two or more + underscores as the search string, because underscores are used as + placeholders for form fields in the displayed document.</p> + + <p id="select-option">When you have invoked a popup window for a + list of OPTIONs in a form's SELECT block, each OPTION is + associated with a number, and that number will be displayed in + <em>Form fields are numbered</em> or <em>Links and form fields + are numbered</em> mode. In any keypad mode, the + <em>F_LINK_NUM</em> ('<em>0</em>') command will invoke a + <em>Select option (or page) number:</em> prompt, and you can + enter a number, and optionally a '<em>g</em>' or '<em>p</em>' + suffix, to select or seek an OPTION in that list. If only a + number is entered at the prompt, the corresponding OPTION will be + selected and the popup will be retracted. If the '<em>g</em>' + suffix is included, then you will be positioned on the + corresponding OPTION in the list, paging through the list if + necessary, but it will not be treated as selected unless you + enter the ACTIVATE (RETURN or right-arrow) command when + positioned on the OPTION. For purposes of paging (e.g., in + conjunction with the '<em>p</em>' suffix), a <em>page</em> is + defined as the number of OPTIONs displayed within the vertical + dimension of the popup window. Finally, the <em>+</em> and + <em>-</em> suffixes can be used to move forward or back from the + current option or page in a popup menu, similarly to the way they + are used for links For example, while viewing a popup window, the + user can type <em>3p+</em> and RETURN to skip ahead 3 pages, and + <em>50g-</em> will move the current selection back 50 options. + This will work whether or not <em>keypad mode</em> is <em>Form + fields are numbered</em> or <em>Links and form fields are + numbered</em> since options are numbered internally. If form + field numbering is turned off, the option numbers won't appear on + screen, but the user can still navigate using these commands.</p> + + <p>Note that HTML can be structured so that it includes + <em>hidden links</em>, i.e., without a visible link name intended + for ACTIVATE-ing the link. Such links may be created, for + example, by making an IMG element the sole content of an Anchor + element, and including an ALT="" attribute name/value pair to + suppress access to the link when the browser does not have + support for image handling available. They also can be created by + having truly empty Anchor content, in cases for which the value + of an Anchor's HREF attribute is intended as a navigation aid for + robots (typically indexers) and not as content for a browser's + rendition of the document. With the <em>-ismap</em> command line + switch, Lynx will additionally treat a link to a server-side + image maps as hidden if there also is a client-side map for the + same image. Finally, in some cases links that are not intended to + be hidden may effectively become <em>hidden links</em> because of + bad HTML. The <em>hidden links</em> differ from Anchors that have + only a NAME or ID attribute name/value pair (intended as + positioning targets from other links which do have HREF + attributes and values that include a fragment).</p> + + <p>Lynx respects instructions for <em>hidden links</em> and + normally does not include them in the rendition of the document. + However, if the command line switch <em>-hiddenlinks=merge</em> + is used, such links will still be numbered in sequence with other + links which are not hidden, and if <em>Links are numbered</em> + mode is also on, link numbers will appear for them in the + displayed text (except for links to image maps which are hidden + because of <em>-ismap</em>). If <em>-hiddenlinks=listonly</em> or + <em>-hiddenlinks=ignore</em> is in effect, <em>hidden links</em> + will not be shown in the text even in <em>links are numbered</em> + mode. Not using a <em>-hiddenlinks</em> flag at all is equivalent + to <em>-hiddenlinks=listonly</em>.</p> + + <p>If a document includes <em>hidden links</em>, they will be + reported, with appropriate labeling, in the menus created for the + LIST ('<em>l</em>') or ADDRLIST ('<em>A</em>') commands, unless + <em>-hiddenlinks=ignore</em> is used. They can then be + ACTIVATE-ed via those menus. Also, if a link was hidden because + of an ALT attribute in an IMG element, it will be converted to a + <em>visible link</em> whenever the IMAGE_TOGGLE ('<em>*</em>') + command is used to create links for SRC attribute values of IMG + elements, because this indicates that the user does have some + form of image handling enabled via a helper application, or + wishes to download files for subsequent use with a graphic + browser or other suitable software.</p> + + <p>HTML forms also may have fields with a HIDDEN attribute, + indicating that a name/value pair for the fields should be + included in the content submitted for the form, but the value + should not be displayed in the rendered form. Lynx respects this + attribute as well, and neither displays the HIDDEN field, nor + assigns it a number for the F_LINK_NUM ('<em>0</em>') command and + <em>Form fields are numbered</em> or <em>Links and form fields + are numbered</em> keypad mode handling, nor includes an entry for + it in the menus created for the LIST ('<em>l</em>') or ADDRLIST + ('<em>A</em>') commands. However, the HIDDEN name/value pairs are + included in any displays of submitted form content in the + <em>Information about the current document</em> that is invoked + by the INFO ('<em>=</em>') command.</p> +</body> +</html> diff --git a/lynx_help/keystrokes/gopher_types_help.html b/lynx_help/keystrokes/gopher_types_help.html new file mode 100644 index 00000000..5af38dbd --- /dev/null +++ b/lynx_help/keystrokes/gopher_types_help.html @@ -0,0 +1,83 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: gopher_types_help.html,v 1.7 2012/01/31 23:15:38 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Listing of Gopher types</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Gopher Types</h1> + + <dl compact> + <dt>(FILE)</dt> + + <dd>An ASCII file</dd> + + <dt>(DIR)</dt> + + <dd>A directory listing</dd> + + <dt>(CSO)</dt> + + <dd>The Computing Services Organizations nameserver + interface</dd> + + <dt>(BIN)</dt> + + <dd> + A binary file with one of the following meanings + + <ul> + <li>A Binary file with PC extensions</li> + + <li>A Binary file with UNIX extensions</li> + </ul> + </dd> + + <dt>(HQX)</dt> + + <dd>A Macintosh file that has been BinHexed</dd> + + <dt>(?)</dt> + + <dd>A searchable database</dd> + + <dt>(IMG)</dt> + + <dd>An unknown image type<br> + You must have an <a href="xterm_help.html">X terminal</a> to + view images</dd> + + <dt>(GIF)</dt> + + <dd>An image in Graphics Interchange Format<br> + You must have an <a href="xterm_help.html">X terminal</a> to + view images</dd> + + <dt>(HTML)</dt> + + <dd>A World Wide Web hypertext file</dd> + + <dt>(TEL)</dt> + + <dd>The link will open a connection to another host using + telnet</dd> + + <dt>(3270)</dt> + + <dd>The link will open a connection to another host using + tn3270</dd> + + <dt>(UKN)</dt> + + <dd>An unknown or unsupported type</dd> + </dl> +</body> +</html> diff --git a/lynx_help/keystrokes/history_help.html b/lynx_help/keystrokes/history_help.html new file mode 100644 index 00000000..f8f4566a --- /dev/null +++ b/lynx_help/keystrokes/history_help.html @@ -0,0 +1,48 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: history_help.html,v 1.5 2012/01/31 23:14:48 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on the History Page</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>History Page Help</h1> + + <p>The History Page displays all of the links that you have + traveled through to reach your current point, including any + temporary menu or list files that included links, bookmark files, + and any documents associated with POST content. If you entered a + document and then left it by using the <em>left-arrow</em> key, + it will <em>not</em> be in the history stack. If you entered a + document and left it by selecting another link within that + document, it <em>will</em> be in the history stack.</p> + + <p>You may <a href="movement_help.html">select</a> any link on + the History Page to review a document that you have previously + visited. That link, and any subsequent to it, will not be removed + from the history stack if you return to it via the History Page. + You thus should use a History Page link, rather than the + <em>left-arrow</em> key, if you wish to review previous documents + without needing to remember and repeat the series of selections + for reaching your currently displayed document.</p> + + <p>Upon using <em>left-arrow</em> in the document selected via + the History Page, you will be returned to the document from which + you initially went to the History Page.</p> + + <p>If a previously visited link has been removed from the history + stack, and it was not a temporary menu or list file, bookmark + file, or document associated with POST content, it can still be + selected conveniently via the <a href="visited_help.html">Visited + Links Page</a>. The latter also will include links which were + '<em>d</em>'ownloaded or passed to a helper application, and thus + were not included in the history stack.</p> +</body> +</html> diff --git a/lynx_help/keystrokes/keystroke_help.html b/lynx_help/keystrokes/keystroke_help.html new file mode 100644 index 00000000..01855e3d --- /dev/null +++ b/lynx_help/keystrokes/keystroke_help.html @@ -0,0 +1,150 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: keystroke_help.html,v 1.17 2012/01/31 23:25:43 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on Lynx Keystroke Commands</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Keystroke Commands</h1> + <pre> + <a href= +"movement_help.html">MOVEMENT</a>: Down arrow - Highlight next topic + Up arrow - Highlight previous topic + Right arrow, - Jump to highlighted topic + Return, Enter - Follow selected link + Left arrow - Return to previous topic + + <a href= +"scrolling_help.html">SCROLLING</a>: + - Scroll down to next page (Page-Down) + - - Scroll up to previous page (Page-Up) + SPACE - Scroll down to next page (Page-Down) + b - Scroll up to previous page (Page-Up) + CTRL-A - Go to first page of the current document (Home) + CTRL-E - Go to last page of the current document (End) + CTRL-B - Scroll up to previous page (Page-Up) + CTRL-F - Scroll down to next page (Page-Down) + CTRL-N - Go forward two lines in the current document + CTRL-P - Go back two lines in the current document + ) - Go forward half a page in the current document + ( - Go back half a page in the current document + ^ - Go to the first link on the current line + $ - Go to the last link on the current line + < - Go to the previous link in the current column + > - Go to the next link in the current column + # - Go to Toolbar or Banner in the current document + + <a href= +"dired_help.html">DIRED</a>: c - Create a new file + d - Download selected file + e - Edit selected file + f - Show a full menu of options for current file + m - Modify the name or location of selected file + r - Remove selected file + t - Tag highlighted file + u - Upload a file into the current directory + + <a href= +"other_help.html">OTHER</a>: ? (or h) - Help (this screen) + a - Add the current link to a bookmark file + c - Send a comment to the document owner + d - Download the current link + e - Edit the current file + E - Edit the current link's URL (or ACTION) and + use that as a goto URL. + g - Goto a user specified <a href= +"../lynx_url_support.html">URL</a> or file + G - Edit the current document's URL and use that + as a goto URL. + i - Show an index of documents + j - Execute a jump operation + k - Show list of actual key mappings + l - List references (links) in current document + m - Return to main screen + o - Set your <a href= +"option_help.html">options</a> + p - <a href= +"print_help.html">Print</a> to a file, mail, printers, or other + q - Quit (Capital '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 + N - Go to the previous search string + v - View a <a href= +"bookmark_help.html">bookmark file</a> + V - Go to the <a href= +"visited_help.html">Visited Links Page</a> + x - Force submission of form or link with no-cache + z - Cancel transfer in progress + [backspace] - Go to the <a href= +"history_help.html">History Page</a> + = - Show info about current document, URL and link + \ - Toggle document source/rendered view + ! - Spawn your default shell + ' - Toggle "historical" vs minimal or valid comment + parsing + _ - Clear all authorization info for this session + ` - Toggle minimal or valid comment parsing + * - Toggle image_links mode on and off + @ - Toggle raw 8-bit translations or CJK mode + on or off + . - Run external program on the current link. + , - Run external program on the current document. + { - Shift the screen left. + } - Shift the screen right. + | - Toggle line-wrap mode. When line-wrap is + off, you may use { and } to shift the screen + left/right. The screen width is set to 999. + ~ - Toggle parsing of nested tables (experimental). + [ - Toggle pseudo_inlines mode on and off + ] - Send a HEAD request for the current doc or link + " - Toggle valid or "soft" double-quote parsing + CTRL-R - Reload current file and refresh the screen + CTRL-L - Refresh the screen + + CTRL-V - Outside of a text input line or field, + switch to <a href= +"option_help.html#tagsoup">alternative parsing</a> of HTML. + - In a form text input field, + CTRL-V prompts for a key command (allows + <a href= +"../Lynx_users_guide.html#CtrlVNote">escaping</a> from the field). + + Note that on most UNIX hosts, CTRL-V is bound + via stty to the lnext (literal-next) code but + the exact behavior of that is implementation + specific. On Solaris you must type CTRL-V + twice to use it, since it quotes the following + keystroke. + + CTRL-U - Inside text input line or field, + erase input line (<a href= +"edit_help.html">more input line commands</a>) + - Outside of text input or field, + undo returning to previous topic. + + CTRL-G - Cancel input or transfer + + CTRL-T - Toggle trace mode on and off + ; - View the Lynx Trace Log for the current session + CTRL-K - Invoke the <a href= +"cookie_help.html">Cookie Jar Page</a> + CTRL-X - Invoke the <a href= +"../Lynx_users_guide.html#Cache">Cache Jar Page</a> + numbers - Invoke the prompt + <a href= +"follow_help.html">Follow link (or goto link or page) number:</a> + or the + <a href= +"follow_help.html#select-option">Select option (or page) number:</a> + prompt +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/movement_help.html b/lynx_help/keystrokes/movement_help.html new file mode 100644 index 00000000..a08534b9 --- /dev/null +++ b/lynx_help/keystrokes/movement_help.html @@ -0,0 +1,57 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: movement_help.html,v 1.6 2012/01/31 23:24:18 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on Lynx Movement commands</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>MOVEMENT HELP</h1> + <pre> + Down arrow, - Move to the next hypertext link, + TAB or scroll down if there are no more + links on the page to move to. + + Up arrow - Move to the previous hypertext link, + or scroll up if there are no links + above the current one, and there are + previous pages to move to. + + Right arrow, - select the link that the cursor is + Return, Enter positioned on. + + Left arrow - Retreat from a link. Go back to the + previous topic. + + + *note: If 'VI Keys' are enabled from the options menu or + from the '.lynxrc' file, lowercase h,j,k,l will + move left, down, up, and right, respectively. + + *note: If 'Emacs Keys' are enabled from the options menu or + from the '.lynxrc' file, Ctrl-B, Ctrl-N, Ctrl-P, + Ctrl-F will move left, down, up, and right, respectively. + + *note: If the 'Num Lock' on your keyboard is on, Lynx will + translate the numbers of your keypad into movement + commands. The translation is as follows. + + 9 - page up + 8 - up arrow + 7 8 9 7 - moves to the top of a document + \|/ 6 - right arrow + 4 - 5 - 6 5 - nothing + /|\ 4 - left arrow + 1 2 3 3 - page down + 2 - down arrow + 1 - moves to the end of a document +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/option_help.html b/lynx_help/keystrokes/option_help.html new file mode 100644 index 00000000..7854b8af --- /dev/null +++ b/lynx_help/keystrokes/option_help.html @@ -0,0 +1,531 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: option_help.html,v 1.24 2012/01/31 23:12:34 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Form-based Options Menu : Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>FORM-BASED OPTIONS MENU : HELP</h1> + + <p>The Options Menu allows you to set and modify many Lynx + features.<br> + Note: some options appear on the screen only if they have been + compiled in or chosen in `lynx.cfg':</p> + + <ul> + <li>General Preferences + + <ul> + <li><a href="#UM">User Mode</a></li> + + <li><a href="#ED">Editor</a></li> + + <li><a href="#ST">Searching type</a></li> + + <li><a href="#CK">Cookies</a></li> + </ul> + </li> + + <li>Keyboard Input + + <ul> + <li><a href="#KM">Keypad mode</a></li> + + <li><a href="#EM">Emacs keys</a></li> + + <li><a href="#VI">VI keys</a></li> + + <li><a href="#LE">Line edit style</a></li> + </ul> + </li> + + <li>Display and Character Set + + <ul> + <li><a href="#DC">Display Character set</a></li> + + <li><a href="#AD">Assumed document character set</a></li> + + <li><a href="#JK">Raw 8-bit or CJK mode</a></li> + + <li><a href="#DV">X DISPLAY variable</a></li> + </ul> + </li> + + <li>Document Appearance + + <ul> + <li><a href="#SC">Show color</a></li> + + <li><a href="#CL">Show cursor for current link or + option</a></li> + + <li><a href="#PU">Pop-ups for select fields</a></li> + + <li><a href="#tagsoup">HTML error recovery</a></li> + + <li><a href="#SI">Show Images</a></li> + + <li><a href="#VB">Verbose Images</a></li> + </ul> + </li> + + <li>Headers Transferred to Remote Servers + + <ul> + <li><a href="#PM">Personal Mail Address</a></li> + + <li><a href="#PC">Preferred Document Charset</a></li> + + <li><a href="#PL">Preferred Document Language</a></li> + + <li><a href="#UA">User Agent</a></li> + </ul> + </li> + + <li>Listing and Accessing Files + + <ul> + <li><a href="#FT">FTP sort criteria</a></li> + + <li><a href="#LD">Local directory sort criteria</a></li> + + <li><a href="#DF">Show dot files</a></li> + + <li><a href="#LL">Execution links</a></li> + </ul> + </li> + + <li>Special Files and Screens + + <ul> + <li><a href="#MB">Multi-bookmarks</a></li> + + <li><a href="#BF">Bookmark file</a></li> + + <li><a href="#VP">Visited Pages</a></li> + </ul> + </li> + </ul> + + <h1><a name="CK">Cookies</a></h1> + + <p>This can be set to accept or reject all cookies or to ask each + time. See the Users Guide for details of <a href= + "../Lynx_users_guide.html#Cookies">cookie usage</a>.</p> + + <h1><a name="ED">Editor</a></h1> + + <p>This is the editor to be invoked when editing browsable files, + sending mail or comments, or filling form's textarea (multiline + input field). The full pathname of the editor command should be + specified when possible. It is assumed the text editor supports + the same character set you have for "display character set" in + Lynx.</p> + + <h1><a name="EM">Emacs keys</a></h1> + + <p>If set to 'ON' then the CTRL-P, CTRL-N, CTRL-F and CTRL-B keys + will be mapped to up-arrow, down-arrow, right-arrow and + left-arrow respectively. Otherwise, they remain mapped to their + configured bindings (normally UP_TWO lines, DOWN_TWO lines, + NEXT_PAGE and PREV_PAGE respectively).</p> + + <p>Note: setting emacs keys does not affect the line-editor + bindings.</p> + + <h1><a name="LL">Execution links</a></h1> + + <p>If set to 'ALWAYS ON', Lynx will locally execute commands + contained inside any links. This can be HIGHLY DANGEROUS, so it + is recommended that they remain 'ALWAYS OFF' or 'FOR LOCAL FILES + ONLY'.</p> + + <h1><a name="KM">Keypad mode</a></h1> + + <p>This gives the choice between navigating with the keypad (as + arrows; see Lynx Navigation) and having every link numbered + (numbered links) so that the links may be selected by numbers + instead of moving to them with the arrow keys. You can also + number form fields.</p> + + <h1><a name="LE">Line edit style</a></h1> + + <p>This allows you to set alternate key bindings for the built-in + line editor, if <a href="alt_edit_help.html">Alternate + Bindings</a> have been installed. Otherwise, Lynx uses the + <a href="edit_help.html">Default Binding</a>.</p> + + <h1><a name="PM">Personal Mail Address</a></h1> + + <p>You may set your mail address here so that when mailing + messages to other people or mailing files to yourself, your email + address can be automatically filled in. Your email address will + also be sent to HTTP servers in a `from:' field.</p> + + <h1><a name="PU">Pop-ups for select fields</a></h1> + + <p>Lynx normally uses a pop-up window for the OPTIONs in form + SELECT fields when the field does not have the MULTIPLE attribute + specified, and thus only one OPTION can be selected. The use of + pop-up windows can be disabled by changing this setting to OFF, + in which case the OPTIONs will be rendered as a list of radio + buttons. Note that if the SELECT field does have the MULTIPLE + attribute specified, the OPTIONs always are rendered as a list of + checkboxes.</p> + + <h1><a name="ST">Searching type</a></h1> + + <p>If set to 'case sensitive', user searches invoked by '/' will + be case-sensitive substring searches. Default is 'Case + Insensitive'.</p> + + <h1><a name="SC">Show color</a></h1> + + <p>This will be present if color support is available.</p> + + <ul> + <li>If set to ON or ALWAYS, color mode will be forced on if + possible. If (n)curses color support is available but cannot be + used for the current terminal type, selecting ON is rejected + with a message.</li> + + <li>If set to OFF or NEVER, color mode will be turned off.</li> + + <li>ALWAYS and NEVER are not offered in anonymous accounts. If + saved to a '.lynxrc' file in non-anonymous accounts, ALWAYS + will cause Lynx to set color mode on at startup if + supported.</li> + </ul>If Lynx is built with slang, this is equivalent to having + included the -color command line switch or having the COLORTERM + environment variable set. If color support is provided by curses + or ncurses, this is equivalent to the default behavior of using + color when the terminal type supports it. If (n)curses color + support is available but cannot be used for the current terminal + type, the preference can still be saved but will have no effect. + + <p>A saved value of NEVER will cause Lynx to assume a monochrome + terminal at start-up. It is similar to the -nocolor switch, but + (when the slang library is used) can be overridden with the + -color switch. If the setting is OFF or ON when the current + options are saved to a '.lynxrc' file, the default start-up + behavior is retained, such that color mode will be turned on at + startup only if the terminal info indicates that you have a + color-capable terminal, or (when slang is used) if forced on via + the -color switch or COLORTERM variable. This default behavior + always is used in anonymous accounts, or if the 'option'_save + restriction is set explicitly. If for any reason the start-up + color mode is incorrect for your terminal, set it appropriately + on or off via this option.</p> + + <h1><a name="CL">Show cursor for current link or option</a></h1> + + <p>Lynx normally hides the cursor by positioning it to the right + and if possible the very bottom of the screen, so that the + current link or OPTION is indicated solely by its highlighting or + color. If show cursor is set to ON, the cursor will be positioned + at the left of the current link or OPTION. This is helpful when + Lynx is being used with a speech or braille interface. It is also + useful for sighted users when the terminal cannot distinguish the + character attributes used to distinguish the current link or + OPTION from the others in the display.</p> + + <h1><a name="UM">User Mode</a></h1> + + <dl> + <dt><em>Novice</em>: Shows 2 extra lines of help at the bottom + of the screen for beginners.</dt> + + <dt><em>Intermediate (normal)</em>: Normal status-line messages + appear.</dt> + + <dt><em>Advanced</em>: The URL is shown on the status + line.</dt> + </dl> + + <h1><a name="AD">Assumed document character set</a></h1> + + <p>This changes the handling of documents which do not explicitly + specify a charset. Normally Lynx assumes that 8-bit characters in + those documents are encoded according to iso-8859-1 (the official + default for HTTP protocol). Unfortunately, many non-English web + pages forget to include proper charset info; this option helps + you browse those broken pages if you know somehow what the + charset is. When the value given here or by an -assume_charset + command-line flag is in effect, Lynx will treat documents as if + they were encoded accordingly. Option is active when 'Raw 8-bit + or CJK Mode' is OFF.</p> + + <h1><a name="JK">Raw 8-bit or CJK mode</a></h1> + + <p>This is set automatically, but can be toggled manually in + certain cases: it toggles whether 8-bit characters are assumed to + correspond with the display character set and therefore are + processed without translation via the chartrans conversion + tables. ON by default when the display character set is one of + the Asian (CJK) sets and the 8-bit characters are Kanji + multibytes. OFF for the other display character sets, but can be + turned ON when the document's charset is unknown (e.g., is not + ISO-8859-1 and no charset parameter was specified in a reply + header from an HTTP server to indicate what it is), but you have + no better idea than viewing it as from display character set (see + 'assumed document character set' for best choice). Should be OFF + when an Asian (CJK) set is selected but the document is + ISO-8859-1 or another 'assumed document character set'. The + setting can also be toggled via the RAW_TOGGLE command, normally + mapped to '@', and at startup via the -raw switch.</p> + + <h1><a name="tagsoup">HTML error recovery</a></h1> + + <p>Lynx often has to deal with invalid HTML markup. It always + tries to recover from errors, but there is no universally correct + way for doing this. As a result, there are two parsing modes: + "<dfn>SortaSGML</dfn>" attempts to enforce valid nesting of most + tags at an earlier stage of processing, while + "<dfn>TagSoup</dfn>" relies more on the HTML rendering stage to + mimic the behavior of some other browsers. You can also switch + between these modes with the CTRL-V key, and the default can be + changed in lynx.cfg or with the -tagsoup command line switch.</p> + + <p>The "SortaSGML" mode will often appear to be more strict, and + makes some errors apparent that are otherwise unnoticeable. One + particular difference is the handling of block elements or + <li>..</li> inside <a + HREF="some.url">..</a>. Invalid nesting like this may + turn anchors into hidden links which cannot be easily followed, + this is avoided in "TagSoup" mode. See the <a href= + "follow_help.html">help on following links by number</a> for more + information on hidden links. Often pages may be more readable in + "TagSoup" mode, but sometimes the opposite is true. Most + documents with valid HTML, and documents with only minor errors, + should be rendered the same way in both modes.</p> + + <p>If you are curious about what goes on behind the scenes, but + find that the information from the -trace switch is just too + much, Lynx can be started with the -preparsed switch; going into + SOURCE mode ('\' key) and toggling the parsing mode (with CTRL-V) + should then show some of the differences. <!-- +LP's version - for reference - TD + +While the proper HTML markup should be canonical, badly nested HTML pages +may be recovered in different ways. There are two error recovery modes +in Lynx: SortaSGML with the recovery at SGML stage and TagSoup mode +with the recovery at HTML parsing stage, the latter gives more +recovery and was the default in Lynx 2.7.2 and before, +and the first may be useful for page validation purposes. +One particular difference is known for <li>..</li> +or similar strong markup inside <a HREF="some.url">..</a> +anchor text - those links are not reachable in SortaSGML +(such markup should be placed outside <a>..</a> indeed). +Default recovery mode can also be switched with CTRL-V key, +from lynx.cfg or command line switch. +--></p> + + <h1><a name="SI">Show Images</a></h1> + + <p>This option combines the effects of the `*' & `[' keys as + follows:</p> + <pre> + <em>ignore</em> all images which lack an ALT= text string, + <em>show labels</em>, e.g. [INLINE] — see `Verbose Images' below — , + <em>use links</em> for every image, enabling downloading. +</pre> + + <p>This option setting cannot be saved between sessions. See + <a href="../Lynx_users_guide.html#Images">Users Guide</a> & + <em>lynx.cfg</em> for more details.</p> + + <h1><a name="VB">Verbose Images</a></h1> + + <p>This allows you to replace [LINK], [INLINE] and [IMAGE] — for + images without ALT — with filenames: this can be helpful by + revealing which images are important & which are merely + decoration, e.g. <em>button.gif</em>, <em>line.gif</em>. See + <a href="../Lynx_users_guide.html#Images">Users Guide</a> & + <em>lynx.cfg</em> for more details.</p> + + <h1><a name="VI">VI keys</a></h1> + + <p>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.</p> + + <p>The uppercase H, J, K, and L keys remain mapped to their + configured bindings (normally HELP, JUMP, KEYMAP and LIST, + respectively).</p> + + <p>Note: setting vi keys does not affect the line-editor + bindings.</p> + + <h1><a name="DC">Display Character set</a></h1> + + <p>This allows you to set up the default character set for your + specific terminal. The display character set provides a mapping + from the character encodings of viewed documents and from HTML + entities into viewable characters. It should be set according to + your terminal's character set so that characters other than 7-bit + ASCII can be displayed correctly, using approximations if + necessary, <a href="test_display.html">try the test here</a>. + Since Lynx now supports a wide range of platforms it may be + useful to note that cpXXX codepages are used within IBM PC + computers, and windows-xxxx within native MS-Windows + applications.</p> + + <h1><a name="DV">X DISPLAY variable</a></h1> + + <p>This option is only relevant to X Window users. It specifies + the DISPLAY (Unix) or DECW$DISPLAY (VMS) variable. It is picked + up automatically from the environment if it has been previously + set.</p> + + <h1><a name="MB">Multi-bookmarks</a></h1> + + <p>Manage multiple bookmark files:</p> + + <ul> + <li>When OFF, the default bookmark file is used for the + 'v'iew-bookmarks and 'a'dd-bookmark link commands.</li> + + <li>If set to STANDARD, a menu of available bookmarks is always + invoked when you seek to view a bookmark file or add a link, + and you select the bookmark file by its letter token in that + menu.</li> + + <li>If set to ADVANCED, you are instead prompted for the letter + of the desired bookmark file, but can enter '=' to invoke the + STANDARD selection menu, or RETURN for the default bookmark + file.</li> + </ul> + + <h1><a name="BF">Bookmark file</a></h1> + + <p>Manage the default bookmark file:</p> + + <ul> + <li>If non-empty and multi-bookmarks is OFF, it specifies your + default '<a href="bookmark_help.html">Bookmark file</a>'.</li> + + <li>If multi-bookmarks is STANDARD or ADVANCED, entering 'B' + will invoke a menu in which you can specify filepaths and + descriptions of up to 26 bookmark files.</li> + </ul>The filepaths must be from your home directory and begin + with './' if subdirectories are included (e.g., + './BM/lynx_bookmarks.html'). + + <p>Lynx will create bookmark files when you first 'a'dd a link, + but any subdirectories in the filepath must already exist.</p> + + <h1><a name="VP">Visited Pages</a></h1> + + <p>This allows you to change the appearance of the <a href= + "visited_help.html">Visited Links Page</a> Normally it shows a + list, in reverse order of the pages visited. The popup menu + allows you these choices:</p> + + <dl> + <dt><em>By First Visit</em>: The default appearance, shows the + pages based on when they were first visited. The list is shown + in reverse order, to make the current page (usually) at the top + of the list.</dt> + + <dt><em>By First Visit Reversed</em> The default appearance, + shows the pages based on when they were first visited. The list + is shown in order, to make the current page (usually) at the + bottom of the list.</dt> + + <dt><em>As Visit Tree</em> Combines the first/last visited + information, showing the list in order of the first visit, but + using the indentation level of the page immediately previous to + determine indentation of new entries. That gives a clue to the + order of visiting pages when moving around in the History or + Visited Pages lists.</dt> + + <dt><em>By Last Visit</em> The default appearance, shows the + pages based on when they were last visited. The list is shown + in reverse order, to make the current page (usually) at the top + of the list.</dt> + + <dt><em>By Last Visit Reversed</em> The default appearance, + shows the pages based on when they were last visited. The list + is shown in order, to make the current page (usually) at the + bottom of the list.</dt> + </dl> + + <h1><a name="FT">FTP sort criteria</a></h1> + + <p>This allows you to specify how files will be sorted within FTP + listings. The current options include `By Filename', + `By Size', `By Type', `By Date'.</p> + + <h1><a name="LD">List directory style</a></h1> + + <p>Applies to Directory Editing. Files and directories can be + presented in the following ways:</p> + + <dl> + <dt><em>Mixed style</em>: Files and directories are listed + together in alphabetical order.</dt> + + <dt><em>Directories first</em>: Files and directories are + separated into 2 alphabetical lists: directories are listed + first.</dt> + + <dt><em>Files first</em>: Files and directories are separated + into 2 alphabetical lists: files are listed first.</dt> + </dl> + + <h1><a name="DF">Show dot files</a></h1> + + <p>If display/creation of hidden (dot) files/directories is + enabled, you can turn the feature on or off via this setting.</p> + + <h1><a name="PC">Preferred Document Charset</a></h1> + + <p>The character set you prefer if sets in addition to ISO-8859-1 + and US-ASCII are available from servers. Use MIME notation (e.g., + ISO-8859-2) and do not include ISO-8859-1 or US-ASCII, since + those values are always assumed by default. Can be a + comma-separated list, which may be interpreted by servers as + descending order of preferences; you can make your order of + preference explicit by using `q factors' as defined by the HTTP + protocol, for servers which understand it: e.g., <kbd>iso-8859-5, + utf-8;q=0.8</kbd>.</p> + + <h1><a name="PL">Preferred Document Language</a></h1> + + <p>The language you prefer if multi-language files are available + from servers. Use RFC 1766 tags, e.g., `en' English, `fr' French. + Can be a comma-separated list, and you can use `q factors' (see + previous help item): e.g., <kbd>da, en-gb;q=0.8, en;q=0.7</kbd> + .</p> + + <h1><a name="UA">User Agent</a></h1> + + <p>The header string which Lynx sends to servers to indicate the + User-Agent is displayed here. Changes may be disallowed via the + -restrictions switch. Otherwise, the header can be changed + temporarily to e.g., L_y_n_x/2.8.3 for access to sites which + discriminate against Lynx based on checks for the presence of + `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 Options Menu. Changes of the + header are not saved in the .lynxrc file.</p> + + <p>NOTE 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'.</p> +</body> +</html> diff --git a/lynx_help/keystrokes/other_help.html b/lynx_help/keystrokes/other_help.html new file mode 100644 index 00000000..866c4d9a --- /dev/null +++ b/lynx_help/keystrokes/other_help.html @@ -0,0 +1,189 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: other_help.html,v 1.12 2012/01/31 23:23:40 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on Misc. Lynx Commands</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Other Commands</h1> + <pre> + a - Places the link that you are currently positioned + on into a personal <a href= +"bookmark_help.html">bookmark file</a>. + + c - Allows you to send a mail message to the owner + or maintainer of the data that you are currently + viewing. In the case that no owner is known, + you cannot send a comment. + + d - Downloads the file pointed to by the current link + and displays an option menu allowing the file to + be saved or transferred by configurable options. + Can also be used when positioned on a form SUBMIT + button to download the reply to a form submission. + + e - Allows you to edit the current document if it is a + local file. + + E - Allows you to edit the current link's URL (or ACTION) and + use that as a <em>goto</em> URL. + + g - Allows you to enter any <a href= +"http://archive.ncsa.uiuc.edu/demoweb/url-primer.html">URL</a> or filename that + you wish to view, and then <em>goto</em> it. + + G - Allows you to edit the current document's URL and use that + as a <em>goto</em> URL. + + ? or H - Hypertext help to explain how to navigate in + Lynx and use its features. + + i - Shows an index of files or subjects, + which may be changed in <em>lynx.cfg</em>. + + j - Allows you to enter a short name to goto an URL, + if a jumps file has been defined. Press "?" + and ENTER to see the list of defined jump commands. + + k - Shows a list of key mappings. Keys remapped in + "lynx.cfg" show up in this list. + + l - Brings up a list of references (links) in the current + document, which can be used for rapid access to the + links in large documents. + + m - Returns to the first screen and empties the + history stack. + + p - Brings up a list of <a href= +"print_help.html">print commands</a>. + + o - Brings up a list of settable <a href= +"option_help.html">options</a>. + + q - Quits Lynx. ('Q' quits without asking) + + / - Search for a string of characters in the current document + (case insensitive or case sensitive + depending on the <a href= +"option_help.html">options</a> set). + + s - Search through an external searchable indexed document. + + n - Move to the next instance of a search string if you + have searched previously. + + v - View a <a href= +"bookmark_help.html">Bookmark file</a>. + + V - Go to the <a href= +"visited_help.html">Visited Links Page</a> + + x - Force submission of form or link with no-cache. + + z - Abort a network transfer in progress. If any partial + data has been transferred it will be displayed. + + <backspace> - displays the <a href= +"history_help.html">History Page</a>. + + = - Show information about the file and link that you + are currently viewing. + + \ - Toggles between viewing the HTML source of a + document and the rendered version of the document. + + ! - Spawns your default operating system shell. + + ' - Toggles "historical" vs minimal or valid comment parsing. + When historical, any close-angle-bracket will be treated + as a comment terminator, emulating the parsing bug in old + versions of Mosaic and Netscape, rather than validly + requiring pairs of two successive dashes to delimit + comments within the angle-brackets. + + _ - Clears all authorization info for the current session. Can + be used when leaving one's terminal without ending the Lynx + session, to guard against someone else retrieving protected + documents with previously entered username/password info. + Note that any protected documents that are still in cache + can still be accessed. + + ` - Toggles minimal or valid comment parsing. When minimal, any + two successive dashes followed by a close-angle-bracket will + be treated as a comment terminator, emulating the parsing bug + in Netscape v2.0. If historical comment parsing is set, that + will override minimal or valid comment parsing. + + * - Toggles image_links mode on and off. When on, links will + be created for all images, including inlines. + + @ - Toggles raw 8-bit translations or CJK mode on and off, only + for documents which does not specify character set explicitly. + Should be on when the document's charset matches the + display character set, and otherwise off so that 8-bit + characters will be translated by Lynx with respect to the + Assumed document charset, using approximations if necessary + (see <a href="option_help.html">options</a>). + + [ - Toggles pseudo_inlines mode on and off. When on, inline + images which have no ALT string specified will have an + "[INLINE]" pseudo-ALT string inserted in the Lynx display. + When off, they will be treated as having ALT="" (i.e., + they'll be ignored). If image_links mode is toggled on, + the pseudo-ALT strings will be restored, to serve as links + to the inline images' sources. + + ] - Sends a HEAD request for the current document or link. It + applies only to documents or links (or form submit buttons) + of http servers. A statusline message will notify you if + the context for this command was inappropriate. The HEAD + requests always are sent to the http server, i.e., Lynx + does not retrieve any previous server replies from its + cache. Note that for form submissions, http servers vary + in whether they'll treat HEAD requests as valid and return + the CGI script's headers, or treat it as invalid and return + an error message. + + " - Toggles valid or "soft" double-quote parsing. When soft, + a close-angle-bracket will serve as both a close-double- + quote and close-tag, emulating the parsing bug in old + versions of Mosaic and Netscape. + + CTRL-R - Reloads the current document and resets the display. + + CTRL-V - Switches to an alternative way of parsing HTML documents. + This may help to get a more readable rendering of some + documents with invalidly placed HTML tags, <a href= +"option_help.html#tagsoup">more details</a>. + + CTRL-W - Resets or cleans up the display. + + CTRL-U - Clears text from an input field or prompt. + + CTRL-G - Cancels any input prompt, mail message or data transfer. + + CTRL-T - Toggles trace mode on and off. + + ; - Views the Lynx Trace Log for the current session. + + CTRL-K - Invokes the Cookie Jar Page. + + numbers - Lynx offers other, advanced navigation features when + numbers are used to invoke the + <a href= +"follow_help.html">Follow link (or goto link or page) number:</a> or + <a href= +"follow_help.html#select-option">Select option (or page) number:</a> + prompts. +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/print_help.html b/lynx_help/keystrokes/print_help.html new file mode 100644 index 00000000..b6f14003 --- /dev/null +++ b/lynx_help/keystrokes/print_help.html @@ -0,0 +1,49 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: print_help.html,v 1.6 2012/01/31 11:56:00 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Print Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Printing Help</h1> + + <p>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:</p> + + <dl> + <dt>Print to a local file:</dt> + + <dd>This allows you to save the current file as ASCII text to + your local disk. You will be asked for a path and filename to + save the file to. If no path is given, the file will be saved + to the directory that you were in when you began Lynx.</dd> + + <dt>Print to the screen:</dt> + + <dd>This option simply scrolls the entire document up the + screen and is intended for those who wish to capture the + document with their terminal.</dd> + + <dt>Mail the file to yourself:</dt> + + <dd>This option allows you to mail the file, in ASCII form, to + any valid e-mail address.</dd> + + <dt>Custom print options:</dt> + + <dd>Any number of custom print options may be defined in + <em>lynx.cfg</em>.</dd> + </dl> +</body> +</html> diff --git a/lynx_help/keystrokes/scrolling_help.html b/lynx_help/keystrokes/scrolling_help.html new file mode 100644 index 00000000..872991c5 --- /dev/null +++ b/lynx_help/keystrokes/scrolling_help.html @@ -0,0 +1,74 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: scrolling_help.html,v 1.8 2012/01/31 11:53:58 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx Scrolling Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>SCROLLING HELP</h1> + <pre> + + (or SPACE, - If the bottom of the screen informs you + or CTRL-F) that there is 'more' to see, you may + move to the next page (Page-Down). + + - (or b, - If you have moved down in a document, this + or CTRL-B) will bring you back up one page (Page-Up). + + If the 'Num Lock' on your keyboard is on, Lynx translates + 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). + + ^ - Go to the first link on the current line. + + $ - Go to the last link on the current line. + + < - Go to the previous link in the current column. + + > - Go to the next link in the current column. + + # - Jumps you to the pseudo Toolbar or Banner if + present in the current document. Use left-arrow + to return from there to your previous position + in the document. +</pre> +</body> +</html> diff --git a/lynx_help/keystrokes/test_display.html b/lynx_help/keystrokes/test_display.html new file mode 100644 index 00000000..51dbbedb --- /dev/null +++ b/lynx_help/keystrokes/test_display.html @@ -0,0 +1,58 @@ +<!DOCTYPE html PUBLIC "-//IETF//DTD HTML 3.0//EN"> +<!-- $LynxId: test_display.html,v 1.7 2012/01/31 11:53:11 tom Exp $ --> +<!-- do not use tidy for this page --> +<HTML> +<HEAD> +<TITLE>Quick test for identifying display character set</TITLE> +<LINK rev="made" href="mailto:lynx-dev@nongnu.org"> +<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> +</HEAD> +<BODY> +<h1 ALIGN=LEFT>Try this page with Lynx 2.7.2 or above:</h1> + +If you see several letters instead of a single - your promised display charset +does not support this character so "7 bit approximation" is in effect. +If you see any single letter which definitely far from being supposed +you have a wrong lynx settings. +<em>Press 'o' for Options menu and change "Display character set"</em>. +Try again if necessary.<br> +When you are satisfied save your changes in Options menu, thanks. +<PRE> + + +0x00A9 © # COPYRIGHT SIGN + +0x00C7 Ç # LATIN CAPITAL LETTER C WITH CEDILLA + +0x00DC Ü # LATIN CAPITAL LETTER U WITH DIAERESIS + +0x00D1 Ñ # LATIN CAPITAL LETTER N WITH TILDE + +0x0107 ć # LATIN SMALL LETTER C WITH ACUTE +0x0108 Ĉ # LATIN CAPITAL LETTER C WITH CIRCUMFLEX +0x010C Č # LATIN CAPITAL LETTER C WITH CARON + + +0x03BB λ # GREEK SMALL LETTER LAMDA + +0x041B Л # CYRILLIC CAPITAL LETTER EL +0x042E Ю # CYRILLIC CAPITAL LETTER YU +0x043B л # CYRILLIC SMALL LETTER EL +0x044E ю # CYRILLIC SMALL LETTER YU + +0x2026 … # HORIZONTAL ELLIPSIS +0x2122 ™ # TRADE MARK SIGN + +0x255D ╝ # BOX DRAWINGS DOUBLE UP AND LEFT +0x255E ╞ # BOX DRAWINGS VERTICAL SINGLE AND RIGHT DOUBLE + +0xFB01 fi # LATIN SMALL LIGATURE FI + + + +</PRE> +This is only a quick test to see obvious problems. + + +</BODY> +</HTML> diff --git a/lynx_help/keystrokes/visited_help.html b/lynx_help/keystrokes/visited_help.html new file mode 100644 index 00000000..891845ea --- /dev/null +++ b/lynx_help/keystrokes/visited_help.html @@ -0,0 +1,46 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: visited_help.html,v 1.7 2012/01/31 11:50:47 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Help on the Visited Links Page</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>Visited Links Page Help</h1> + + <p>The Visited Links Page displays all of the links that you have + traveled through during the current Lynx session, except for any + temporary menu or list files, bookmark files, or any documents + associated with POST content. The VLINKS keystroke command for + invoking this page normally is mapped to uppercase '<em>V</em>'. + The list of Visited Links is normally in order of recency (most + recently visited links first), without repetitions in the list if + a link was visited more than once during the session (unless the + URLs differ due to appended fragments), and is supplementary to + the <a href="history_help.html">History Page</a>.</p> + + <p>You may <a href="movement_help.html">select</a> any link on + the Visited Links Page to retrieve a document that you had + previously visited, or you can use this list to save such links + in your <a href="bookmark_help.html">bookmark files</a>, or to + <a href="../Lynx_users_guide.html#RemoteSource">Download</a> + them.</p> + + <p>In contrast to the History Page, the Visited Links Page + includes any links which were retrieved for + '<em>d</em>'ownloading or were passed to helper applications, + i.e., not just the links that were rendered and displayed by + Lynx, itself.</p> + + <p>You may change the appearance of the Visited Links Page via a + popup menu on that page (which also appears on the <a href= + "option_help.html#VP">Options Menu</a>).</p> +</body> +</html> diff --git a/lynx_help/keystrokes/xterm_help.html b/lynx_help/keystrokes/xterm_help.html new file mode 100644 index 00000000..e76674ca --- /dev/null +++ b/lynx_help/keystrokes/xterm_help.html @@ -0,0 +1,43 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: xterm_help.html,v 1.6 2012/01/31 11:49:45 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>X Terminal Help</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h1>X Terminal or X Server</h1> + + <p>An X terminal is an electronic display terminal that + communicates with a host computer system using the X Window + protocol developed at the Massachusetts Institute of + Technology.</p> + + <p>The X Window protocol allows a program running on the host + computer system to display both formatted text and graphics on + the X terminal. Since the X Window protocol is defined to work + over any TCP/IP network, X terminals connected to the Internet + can be connected to hosts located anywhere on the Internet.</p> + + <p>Personal computers (including both PCs and Macintoshes) can + execute programs, usually called X servers, that make them act + like X Window terminals and are frequently used as X + terminals.</p> + + <dl> + <dt>Note:</dt> + + <dd>The terminology used to describe processes associated with + X terminals can be confusing. An X terminal is also known as an + "X display server," and the program running on the host + computer is usually known as the "X client."</dd> + </dl> +</body> +</html> diff --git a/lynx_help/lynx-dev.html b/lynx_help/lynx-dev.html new file mode 100644 index 00000000..b3cf4670 --- /dev/null +++ b/lynx_help/lynx-dev.html @@ -0,0 +1,99 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<!-- $LynxId: lynx-dev.html,v 1.13 2012/01/31 10:51:43 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>Lynx-Dev Discussion List</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <blockquote> + [ <a href= + "http://mail.gnu.org/mailman/listinfo/lynx-dev/">Lynx-Dev + Archive</a> | <a href="about_lynx.html">About Lynx</a> ] + </blockquote> + + <h1><em>The Lynx Development Process</em></h1> + + <p>Lynx is maintained and improved by an international + co-operative of volunteers. Newcomers are welcome to join the + group: you needn't be a super programmer, but you should be + prepared to listen and learn, as well as to contribute patches if + you can. Since everyone is a volunteer, you will usually be + expected to try to implement any suggestions you make.</p> + + <h1><em>Lynx-Dev Discussion List</em></h1> + + <p>The developers communicate through a mailing list — see + below for details — which is open to interested users as + well as programmers. Topics include fixing bugs, increasing + Lynx's tools and powers, meeting the ever-changing demands of the + Internet and porting Lynx to new systems.</p> + + <p>Anyone may read what has been said on the list by visiting + <a href= + "http://mail.gnu.org/mailman/listinfo/lynx-dev/"> the + Archive</a>.</p> + + <h1><em>Development Versions of Lynx</em></h1> + + <p>Besides <em>releases</em>, which are stable versions of Lynx + which come out once or twice a year and can be obtained from + <a href="http://lynx.isc.org/release/">the release site</a>, + there are <em>development</em> versions, which are experimental + — though usually stable enough to use — and appear + every few weeks, depending on current activity.</p> + + <p>You can find the latest <em>development</em> version of Lynx + by visiting <a href="http://lynx.isc.org/current/">the + development site</a>.</p> + + <h1><em>Subscribing to Lynx-Dev</em></h1> + + <p>If you are interested in joining the Lynx mailing list, send + e-mail to <a href= + "mailto:lynx-dev-request@nongnu.org?subject=subscribe"> lynx-dev-request@nongnu.org</a> + with "subscribe" as the subject line.</p> + + <p>You will need to answer one follow-up question to confirm you + want to subscribe. Mailman will then enroll you and send all + messages which you address to <em>lynx-dev@nongnu.org</em> to all + subscribers; you will also receive all messages sent by other + subscribers.</p> + + <h1><em>Unsubscribing from Lynx-Dev</em></h1> + + <p>To <em>unsubscribe</em>, send an e-mail to <a href= + "mailto:lynx-dev-request@nongnu.org?subject=unsubscribe"> lynx-dev-request@nongnu.org</a> + with "unsubscribe" as the subject line.</p> + + <h1><em>Casual Inquiries</em></h1> + + <p>Anyone may ask a question or offer a comment by sending e-mail + to <a href="mailto:lynx-dev@nongnu.org"> the list</a>. Since + all subscribers are volunteers, you depend on their goodwill and + will be more likely to get a response if you give the e-mail a + meaningful `Subject' and include details of your version of Lynx, + hardware and software. You can check the Archive to find any + responses.</p> + + <p>Messages from non-subscribers are not immediately distributed + to avoid spam. Usually, if your message appears genuine, it will + be retrieved from the pile headed for the wastebasket within a + day or so and distributed to the list. For best results, + subscribe as described above.</p> + + <h1><em>The Lynx-Dev Archive</em></h1> + + <p>Messages posted to lynx-dev are archived in html format so + that you can view them using Lynx: go to the <a href= + "http://mail.gnu.org/mailman/listinfo/lynx-dev/">Mail + Archive</a>.</p> +</body> +</html> diff --git a/lynx_help/lynx_help_main.html b/lynx_help/lynx_help_main.html new file mode 100644 index 00000000..4e601b03 --- /dev/null +++ b/lynx_help/lynx_help_main.html @@ -0,0 +1,179 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"> +<!-- $LynxId: lynx_help_main.html,v 1.38 2012/01/31 10:50:33 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>The Lynx Help Page</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <h2>Lynx help files (usually in your local directories):</h2> + + <ul> + <li><a href="Lynx_users_guide.html">Lynx Users Guide</a> + — complete account of all Lynx features</li> + + <li><a href="keystrokes/keystroke_help.html">Key-stroke + Commands</a> — quick outline of what various keys do</li> + + <li><a href="keystrokes/edit_help.html">Line Editor</a> — + when entering URLs etc</li> + + <li><a href="lynx_url_support.html">Supported URLs</a> — + how Lynx handles various types of URL</li> + + <li><a href="about_lynx.html">About Lynx</a> — credits, + copyright etc</li> + + <li><a href="lynx-dev.html">About Lynx-Dev</a> — the + developers & how to contact them</li> + </ul> + + <h2>Other sources of Lynx help:</h2> + + <ul> + <li><a href= + "http://lynx.isc.org/release/lynx2-8-7/lynx_help/cattoc.html">lynx.cfg + options</a> — a reference for advanced + configurations</li> + + <li><a href="http://lynx.isc.org/release/lynx2-8-7/docs/">lynx + documentation</a> — supplementary documentation</li> + + <li><a href= + "http://www.chass.utoronto.ca/%7Epurslow/lhfb.html">Lynx Help + for Beginners</a> — quick help on many common problems + <!-- {li}{a href="http://lynx.isc.org/cgi-bin/fom"}The Lynx FAQ-O-Matic{/a} .. many common queries, some more advanced; users may add answers. --></li> + + <li><a href="http://www.subir.com/lynx.html">Lynx Links</a> + — source & binaries, FAQs, developers & + archives,<br> + SSL & security, and more</li> + + <li><a href="http://leb.net/blinux/blynx/">Blynx</a> — + Speech-Friendly Help for the visually impaired</li> + </ul> + + <h2>World Wide Web Consortium documents:</h2> + + <ul> + <li>HTML — <a href= + "http://www.w3.org/TR/REC-html40/">4.0</a> — <a href= + "http://www.w3.org/MarkUp/">3.2</a> — <a href= + "http://www.w3.org/MarkUp/html3/Contents.html">3.0</a> — + <a href= + "http://www.w3.org/MarkUp/html-spec/html-spec_toc.html">2.0</a></li> + + <li>HTTP — <a href="http://www.w3.org/Protocols/">1.1</a> + — <a href= + "http://www.isi.edu/in-notes/rfc1945.txt">1.0</a></li> + + <li><a href="http://www.w3.org/Addressing/">Web Naming & + Addressing Overview: URIs, URLs etc</a></li> + + <li><a href="http://www.w3.org/International/">HTML + Internationalization</a></li> + + <li><a href="http://www.w3.org/">WWW Consortium: home + page</a></li> + </ul> + + <h2>Help with HTML:</h2> + + <ul> + <li><a href="http://www.htmlhelp.com/reference/html40/">HTML + 4.0 Reference</a></li> + + <li><a href= + "http://archive.ncsa.uiuc.edu/General/Internet/WWW/HTMLPrimer.html"> + NCSA Beginner's Guide To HTML</a></li> + + <li><a href= + "http://www.ku.edu/acs/documentation/docs/html_quick.shtml">HTML + Quick Reference Guide</a></li> + </ul> + + <h2>HTML validation services:</h2> + + <ul> + <li><a href="http://validator.w3.org/">W3C HTML Validation + Service</a></li> + + <li><a href="http://www.htmlhelp.com/tools/validator/">WDG HTML + Validator</a></li> + </ul> + + <h2>Other browsing software:</h2> + + <ul> + <li><a href="http://wget.sunsite.dk/">GNU wget</a> — + powerful & flexible non-interactive downloader</li> + + <li><a href="http://www.idata.sk/~ondrej/pavuk/">Pavuk</a> + — powerful & an even more-featured downloader</li> + + <li><a href="http://curl.haxx.se/">cURL</a> — + non-interactive downloader which supports HTTPS</li> + + <li><a href="http://www.xach.com/snarf/">snarf</a> — + small simple 1-file non-interactive downloader</li> + </ul> + + <h2>Meta-indexes: lists of links</h2> + + <ul> + <li><a href= + "http://archive.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html"> + NCSA Mosaic</a></li> + </ul> + + <h2>Search engines:</h2> + + <ul> + <li><a href="http://www.alltheweb.com/">AlltheWeb.com</a></li> + + <li><a href="http://www.altavista.com/">AltaVista</a></li> + + <li><a href="http://www.ask.com/">Ask.com</a></li> + + <li><a href="http://www.excite.com/">Excite</a></li> + + <li><a href="http://www.go.com/">GO.com</a></li> + + <li><a href="http://www.google.com/">Google</a></li> + + <li><a href="http://search.lycos.com/">Lycos</a></li> + + <li><a href="http://www.metacrawler.com/">MetaCrawler</a></li> + + <li><a href="http://www.search.com/">Search.com</a></li> + + <li><a href="http://www.teoma.com/">Teoma</a></li> + + <li><a href="http://www.webcrawler.com/">WebCrawler</a></li> + + <li><a href="http://www.yahoo.com/">Yahoo!</a></li> + </ul> + + <h2>Free WWW E-mail services:</h2> + + <ul> + <li><a href="http://www.eudoramail.com/">Eudora + Web-Mail</a></li> + + <li><a href="http://www.excite.com/">Excite Inbox</a></li> + + <li><a href="http://www.hotmail.com/">Hotmail</a></li> + + <li><a href="http://www.netaddress.com/">Net@ddress</a></li> + + <li><a href="http://mail.yahoo.com/">Yahoo! Mail</a></li> + </ul> +</body> +</html> diff --git a/lynx_help/lynx_url_support.html b/lynx_help/lynx_url_support.html new file mode 100644 index 00000000..390c0153 --- /dev/null +++ b/lynx_help/lynx_url_support.html @@ -0,0 +1,700 @@ +<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 3.2//EN"> +<!-- $LynxId: lynx_url_support.html,v 1.30 2012/01/31 10:52:00 tom Exp $ --> + +<html> +<head> + <meta name="generator" content= + "HTML Tidy for Linux/x86 (vers 6 November 2007), see www.w3.org"> + + <title>URL Schemes Supported in Lynx</title> + <link rev="made" href="mailto:lynx-dev@nongnu.org"> + <meta http-equiv="Content-Type" content= + "text/html; charset=us-ascii"> +</head> + +<body> + <blockquote> + <em>[</em><a href="#http_url">http, https</a> <em>|</em> + <a href="#telnet_url">telnet, tn3270, rlogin</a> <em>|</em> + <a href="#gopher_url">gopher</a> <em>|</em> <a href= + "#file_url">file</a> <em>|</em> <a href="#ftp_url">ftp</a> + <em>|</em> <a href="#wais_url">wais</a> <em>|</em> <a href= + "#news_url">news, nntp, snews</a> <em>|</em> <a href= + "#newspost_url">newspost, newsreply, snewspost, snewsreply</a> + <em>|</em> <a href="#mailto_url">mailto</a> <em>|</em> <a href= + "#finger_url">finger</a> <em>|</em> <a href="#cso_url">cso</a> + <em>|</em> <a href="#bibp_url">bibp</a> <em>|</em> <a href= + "#exec_url">lynxexec, lynxprog</a> <em>|</em> <a href= + "#cgi_url">lynxcgi</a><em>|</em> <a href="#ncftp_url">NcFTP</a> + <em>|</em> <a href="#internal_url">internal</a><em>]</em> + </blockquote> + + <h1><em>URL Schemes Supported in Lynx</em></h1> + + <p>Lynx handles a number of URL types, that are enumerated below. + For more details about URLs (Uniform Resource Locators) see + <em>RFC1738</em>:</p> + + <ul> + <li><a href= + "http://www.w3.org/Addressing/rfc1738.txt">http://www.w3.org/Addressing/rfc1738.txt</a></li> + + <li><a href= + "ftp://ftp.rfc-editor.org/in-notes/rfc1738.txt">ftp://ftp.rfc-editor.org/in-notes/rfc1738.txt</a></li> + </ul> + + <p>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 + <em>RFC1808</em>:</p> + + <ul> + <li><a href= + "http://www.w3.org/Addressing/rfc1808.txt">http://www.w3.org/Addressing/rfc1808.txt</a></li> + + <li><a href= + "ftp://ftp.rfc-editor.org/in-notes/rfc1808.txt">ftp://ftp.rfc-editor.org/in-notes/rfc1808.txt</a></li> + </ul>and in subsequent drafts of the <em>IETF</em>: + + <ul> + <li><a href="http://www.ics.uci.edu/pub/ietf/uri/">Uniform + Resource Identifiers (URI) Working Group</a></li> + </ul> + + <p>When entering a URL on the command line to be used as the + <em>startfile</em>, or at the prompt for a '<em>g</em>'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 + <em>lynx.cfg</em>.</p> + + <p>For example, <em>wfbr</em> will be treated as + <em>http://www.wfbr.edu/</em>, and <em>wfbr/dir/lynx</em> will be + treated as <em>http://www.wfbr.edu/dir/lynx</em>, but + <em>gopher.wfbr.edu/11/_fileserv/_lynx</em> will be treated as + <em>gopher://gopher.wfbr.edu/11/_fileserv/_lynx</em>.</p> + + <p>For files or directories on the local host, a tilde + (<em>~</em>) is expanded to the path of the account's login + directory, e.g., <em>~/foo</em> will be expanded to + <em>file://localhost/your/login/directory/foo</em>. The tilde + expansion is done homologously on Unix and VMS.</p> + + <p>On VMS, Lynx also will expand any file or directory spec + recognizable to DCL into a valid URL, e.g., <em>[]</em> will be + expanded to + <em>file://localhost/current/default/directory</em>.</p> + + <p>These expansions are <em>SOLELY</em> for <em>startfile</em> or + '<em>g</em>'oto entries! Any partial or relative URLs within HTML + documents are resolved according to the rules specified in + RFC1808 and subsequent IETF drafts.</p> + <hr> + + <h2><a name="http_url">The <em>http</em> and <em>https</em> + URLs:</a></h2> + + <p>Lynx handles http URLs exactly as specified in RFC1738. The + format is:</p> + <pre> + <em>http://host:port/path?searchpart#fragment</em> +</pre>where <em>:port</em> is optional and defaults to +<em>:80</em>, <em>/path</em> if present is a slash-separated series +of symbolic elements, and <em>?searchpart</em> if present is the +query for an ISINDEX search or the content of a FORM with +METHOD="GET". The <em>#fragment</em> field if present indicates a +location in the document to seek for display, based on a NAME-ed +anchor or an ID attribute within the document, and is technically +an instruction rather than part of the URL. 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. + + <p>The https URL has the same format, but the default port is + <em>:443</em>.</p> + <hr> + + <h2><a name="telnet_url">The <em>telnet</em>, <em>tn3270</em>, + and <em>rlogin</em> URLs:</a></h2> + + <p>A <em>telnet</em> URL generally results in Lynx spawning a + telnet session. Lynx implements the complete telnet URL scheme, + i.e.:</p> + <pre> + <em>telnet://user:password@host:port</em> +</pre> + + <p>The <em>user</em> and/or <em>:password</em> fields may be + omitted, and the <em>@</em> should be omitted if neither is + present. The port defaults to <em>:23</em> when omitted in the + URL.</p> + + <p>A <em>tn3270</em> or <em>rlogin</em> URL is specified + equivalently, and similarly spawns a tn3270 or rlogin session. + The actual behavior is dependent on the TCP-IP software installed + on the local and target hosts.</p> + + <p>It is unwise to include the <em>:password</em> field except + for URLs which point to anonymous or other public access + accounts, and for most TCP-IP software you will be prompted for a + password whether or not one was included in the URL.</p> + <hr> + + <h2><a name="gopher_url">The <em>gopher</em> URL:</a></h2> + + <p>The gopher URL takes the form:</p> + <pre> + <em>gopher://host:port/gopher-path</em> +</pre>where <em>:port</em> is optional and defaults to +<em>:70</em>, and the <em>/gopher-path</em> is opaque (not fully +equivalent to the slash-separated series of symbolic elements of +http paths) as explained in RFC1738. Typically, the gopher-path +consists of a <a href= +"keystrokes/gopher_types_help.html"><em>gophertype</em></a> +indicating the file or service type (e.g., <em>0</em> or <em>I</em> +for plain text or an image, respectively, <em>7</em> for a search, +or <em>1</em> for a directory), followed by a platform-specific +<em>selector</em>. Any reserved characters in the selector should +be hex escaped (<em>%hh</em>), including slashes, although hex +escaping of slashes is not required by Lynx in gopher URLs. + + <p>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 <em>?</em> rather than + hex-escaped tab (<em>%09</em>) as the separator for the + <em>searchpart</em> in the <em>selector</em>, e.g.:<br> + <em>gopher://gopher.wfbr.edu/77/_shell/search.shell%20/_shell/walker?lynx*</em> + Lynx will handle the <em>%09</em> if you use that instead of + <em>?</em>, but other WWW clients may mishandle it.</p> + + <p>For the <em>gophertype</em> which signifies HTML (<em>h</em>), + if the <em>selector</em> begins with <em>GET%20/</em> Lynx will + convert the gopher URL to an http URL, e.g.:<br></p> + <pre> +<em>gopher://www.wfbr.edu:80/hGET%20/</em> +</pre>will become:<br> + <pre> +<em>http://www.wfbr.edu/</em> +</pre>The port field will be retained if it is not <em>:80</em>, +and will default to <em>:70</em> if it was defaulted originally. +These conventions were adopted during development of the University +of Minnesota gopher software to facilitate the offering of links to +MIME-capable http servers in the listings returned by gopher +servers, but should be considered Lynxisms and UMN Gopherisms. + <hr> + + <h2><a name="file_url">The <em>file</em> URL:</a></h2> + + <p>The file URL is used to retrieve files or generate a directory + listing on the local host. The host field can be + <em>localhost</em> or a domain name for the local host:<br></p> + <pre> +<em>file://localhost/path</em> +</pre>If you do not use <em>localhost</em> or a domain name for the +local host, Lynx will substitute <em>ftp://</em> for +<em>file://</em> and treat it as an ftp URL. + + <p>The <em>/path</em> is treated as originating at the root, + unless you include a tilde (<em>~</em>), e.g.:</p> + <pre> + <em>file://localhost/~/foo</em> will be converted to: + <em>file://localhost/your/login/directory/foo</em> +</pre>The latter feature is a Lynxism, is done homologously on Unix +and VMS, and should be used ONLY in local documents intended for +Lynx. + + <p>On VMS, the first element of the path, if not a tilde, is + assumed to be a device, e.g.:</p> + <pre> + <em>file://localhost/www_root/directory/filename.suffix</em> +</pre>should be used for: +<em>www_root:[directory]filename.suffix</em><br> + If you are unsure how to specify a file URL in local documents on + VMS, invoke Lynx with the desired file or directory as the + <em>startfile</em> using any spec acceptable to DCL, and then use + the <em>showinfo</em> command (<em>=</em>) to see the file URL + which Lynx created for it. + <hr> + + <h2><a name="ftp_url">The <em>ftp</em> URL:</a></h2> + + <p>The ftp URL has the general format:</p> + <pre> + <em>ftp://host:port/path;type=[D,I, or A]</em> + <em>ftp://username@host:port/path;type=[D,I, or A]</em> +</pre> + + <p>The default port is <em>:21</em> and the default + <em>username</em> is <em>anonymous</em>. If <em>username</em> is + included, Lynx will prompt you for the password. For anonymous + ftp, Lynx uses your <em>personal_mail_address</em> (user@host) as + the <em>password</em> if it has been defined via the + '<em>o</em>'ptions menu. Otherwise, Lynx uses the dummy password + <em>WWWUser</em>. (A password can also be embedded in the URL, by + replacing <em>username</em> with <em>username:password</em>. This + is strongly discouraged for 'real' passwords that must be kept + secret, since URLs with the completely unencrypted + <em>password</em> may show up on the screen, in HISTORY and LIST + pages etc., and may even become visible to remote sites for + example through Referer headers.) Do not include the <em>@</em> + if neither <em>username</em> nor <em>:password</em> is + included.</p> + + <p>The <em>;type=</em> parameter can be used with value + <em>D</em>, <em>I</em>, or <em>A</em> to force handling of the + URL as, respectively, a directory listing, binary file, or ASCII + file. The 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.</p> + + <p>The <em>/path</em> is treated according to RFC1738 for VMS and + VM/CMS ftp servers. The lead slash (<em>/</em>) is treated purely + as a separator, not as a designator for the root, and the + <em>path</em> string if present is treated as in or under the + login directory. For VMS ftp servers, if you wish to have the + first element treated as a device rather than file or + subdirectory name, begin it with a hex-escaped slash + (<em>%2f</em>), e.g.:</p> + <pre> + <em>ftp://user@myhost/%2fsys$common/syshlp</em> +</pre>can be used for a listing of sys$common:[syshlp]<br> + Also, on VM/CMS ftp servers, if the <em>path</em> string begins + with <em>vmsysu%3a</em> it receives special handling as an SFS + path, e.g.: + <pre> + <em>ftp://ubvm.cc.buffalo.edu/vmsysu%3alistserv.webshare</em> +</pre> + + <p>For Unix and Unix-emulation ftp servers, RFC1738 is not + respected and the lead slash is treated as the root, i.e., the + <em>/path</em> is handled equivalently to that in file URLs. The + distinction is irrelevant for anonymous ftp, but matters when + using ftp for non-anonymous accounts. If you are using ftp with a + Unix server and do wish to get a listing of the login directory + or have the <em>path</em> string treated as a file or path under + the login directory, include a tilde (<em>~</em>) as for <a href= + "#file_url">file</a> URLs, e.g.:</p> + <pre> + <em>ftp://user@myhost/~</em> +</pre> + <hr> + + <h2><a name="wais_url">The <em>wais</em> URL:</a></h2> + + <p>The wais URL is used to retrieve resources using the Wide Area + Information System protocol. The format is:</p> + <pre> + <em>wais://host:port/database</em> + <em>wais://host:port/database?wais_query</em> + <em>wais://host:port/database/wais_type/wais_path</em> +</pre>where <em>:port</em> defaults to <em>:210</em> + + <p>Direct wais support is built into Lynx for VMS, and can be + compiled into Lynx on Unix.</p> + + <p>If only a <em>database</em> is indicated in the URL, Lynx + returns an ISINDEX cover page for searching that + <em>database</em>, and will submit your search with the + <em>wais_query</em> appended. Lynx will convert the server's + reply into a hit list with URLs that include the + <em>wais_type</em> and <em>wais_path</em> for retrieving items + from the hit list.</p> + <hr> + + <h2><a name="news_url">The <em>news</em>, <em>nntp</em>, and + <em>snews</em> URLs:</a></h2> + + <p>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 <em>only</em> in nntp and snews URLs. If not + included in news URLs, Lynx will use the nntp server pointed to + by the NNTPSERVER environment variable or configuration symbol + (see lynx.cfg), with default port <em>:119</em>. A host field + must be included in nntp URLs, and the port field is optional + with the same default.</p> + + <p>If the URL requires authentication, lynx will prompt you for + the username and password. These are cached during a session, for + reuse on the same host. If $HOME/.newsauth exists, lynx + initializes its cache from this file. The .newsauth file contents + are one line per entry: hostname, password and username (in that + order) separated by a space.</p> + + <p>The formats are:<br></p> + <pre> + <em>news:newsgroup</em> (retrieves list of messages in newsgroup) + <em>news:messageID</em> (retrieves the message) + <em>news:*</em> (retrieves list of all available newsgroups) + <em>nntp://host:port/newsgroup</em> + <em>nntp://host:port/messageID</em> + <em>nntp://host:port/*</em> +</pre>(snews same as nntp, but the default port is <em>:563</em>) + + <p>The <em>messageID</em> is the message's unique identifier, + consisting of an identification string and the host of origin for + the message (<em>ident_string@origin_host</em>).</p> + + <p>Lynx also supports wildcarding via an asterisk for listings of + news hierarchies or sub-hierarchies, e.g.:</p> + <pre> + <em>news:comp.infosystems.*</em> + <em>nntp://host:port/comp.infosystems.*</em> +</pre>(snews same as nntp, but the default port is +<em>:563</em>)<br> + This is not in RFC1738 and may not be supported by all other + clients. + + <p>Lynx allows you both to <em>reply</em> to the author of a news + message via email, and, if news posting has been enabled, to send + a <em>followup</em> message to the newsgroup (see <a href= + "#newspost_url">newspost, newsreply, snewspost, + snewsreply</a>).</p> + + <p>Lynx converts any strings in news messages which appear to be + a URL with a supported scheme into a link for accessing that + URL.</p> + + <p>Lynx also supports the newsgroup and message number URL + scheme:<br></p> + <pre> + <em>news:newsgroup/startNo-endNo</em> (lists message range in newsgroup) + <em>news:newsgroup/messageNo</em> (retrieves the message by number) + <em>nntp://host:port/newsgroup/startNo-endNo</em> + <em>nntp://host:port/newsgroup/messageNo</em> +</pre>(snews same as nntp, but the default port is +<em>:563</em>)<br> + Use of this scheme is not recommended, because the message + numbers are specific to each nntp server, unlike the unique + identifiers for news messages. + <hr> + + <h2><a name="newspost_url">The <em>newspost</em>, + <em>newsreply</em>, <em>snewspost</em>, and <em>snewsreply</em> + URLs:</a></h2> + + <p>When Lynx receives group listings or articles via + <em>news</em>, <em>nntp</em> or <em>snews</em> URLs, it also + checks whether the nntp server supports posting from the Lynx + user's site, and if so, includes links for posting new messages + to that server, or for posting followups (replies) to previously + posted messages. RFC1738, and IETF URL drafts through this + release of Lynx, do not include any schemes for posting to news + groups. Lynx has long supported newspost and newreply URL schemes + for posting new messages or sending followups, respectively, to + standard nntp servers, with default port <em>:119</em>. Lynx now + also supports homologous snewspost and snewsreply URLs for use + with SSL capable nntp servers.</p> + + <p>The formats are:</p> + <pre> + <em>newspost://host:port/newsgroup(s)</em> (post a new message) + <em>newsreply://host:port/newsgroup(s)</em> (post a followup message) +</pre>(snewspost and snewsreply have the same formats, but the +default port is <em>:563</em>) + + <p>If the host field is omitted, it defaults to that pointed to + by the NNTPSERVER configuration or environmental variable. + Inclusion of at least one newsgroup in the URL is required, and + additional groups can be specified as a comma-separated list. + Wildcarding of newsgroup names is not supported for these URLs. + For newsreply and snewsreply URLs, if an external editor has been + defined via the <em>Options Menu</em>, the user is offered an + option to include the currently displayed document, which + presumably is a news article with a <em>followup</em> link that + was activated, and if confirmed, each line of that document is + prefixed with a right-angle-bracket. The user is expected to edit + such an inclusion so that only the passages relevant to the + followup message are retained.</p> + + <p>These URLs can be used as command line startfiles (in which + case, Lynx will exit after posting the message, and the newreply + or snewsreply URLs degrade to newspost or snewpost URLs, + respectively). They also can be used as HREF attribute values in + any HTML document homologously to <a href= + "#mailto_url">mailto</a> URLs, with the qualification that they + presently are supported only by Lynx.</p> + <hr> + + <h2><a name="mailto_url">The <em>mailto</em> URL:</a></h2> + + <p>The mailto URL is used to provide links that when activated + can be used to send a comment or the content of a FORM to an + Internet email address (user@host). The format is:</p> + <pre> + <em>mailto:user@host</em> +</pre> + + <p>The description of the mailto URL in RFC1738 has been + interpreted by some as allowing only a single recipient, but 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.</p> + + <p>For compatibility with Netscape, Lynx parses any + <em>?subject=The%20Subject</em> appended to the URL, trims the + URL at the <em>?</em>, and uses the value as the default Subject: + for the message or FORM content mailing. This is not recommended + practice. The preferred way to indicate the default Subject: for + a LINK or Anchor with a mailto HREF, or a FORM with a mailto + ACTION, is via a TITLE attribute with the subject string as its + value, e.g.:</p> + <pre> + <em><LINK REV="made" + HREF="mailto:me@myhost,her@herhost" TITLE="The Subject"></em> + + <em><A HREF="mailto:user@host" TITLE="The Subject">...</A></em> + + <em><FORM METHOD="post" ENCTYPE="text/plain" + ACTION="mailto:WebMaster@host" TITLE="The Subject"> + ... + </FORM></em> +</pre> + + <p>Note that a TITLE attribute for FORM is now included in the + HTML specifications. Some clients use a SUBJECT attribute for + this purpose in FORM tags, and Lynx recognizes that as a synonym + for TITLE.</p> + + <p>Lynx also will process any <em>to=address(es)</em>, + <em>cc=address(es)</em>, <em>keywords=word_list</em> and/or + <em>body=message</em> fields in <em>?searchpart</em> tack-ons to + mailto URLs. The <em>to</em> and/or <em>cc</em> values can be + single addresses, or comma- or semi-colon-separated lists of + addresses. All addresses, and any <em>body</em> values, will be + offered for approval by the user before proceeding with a + mailing. Any other name=value pairs in the <em>?searchpart</em> + will be ignored. Also, if the mailto URL is the ACTION for a + FORM, any <em>body</em> in a <em>?searchpart</em> tack-on will be + ignored, because the body of the mailing must be constructed + solely from the the FORM's content. Lynx expects multiple + name=value pairs in a <em>?searchpart</em> tack-on to be + separated by ampersands, as in the original Netscape + implementation, and in an equally ill-advised IETF draft of that + implementation (<a href= + "ftp://ftp.isi.edu/internet-drafts/draft-hoffman-mailto-url-03.txt">draft-hoffman-mailto-url-03.txt</a>). + These should be represented as entities (<em>&amp;</em>) in + the HTML markup. This functionality is generally desired, but the + IETF backward compatibility principal normally would lead to a + new scheme being used (e.g., <em>mail:</em>, or <em>smtp:</em>), + rather than breaking <em>mailto:</em> implementations.</p> + + <p>If <em>ENCTYPE="text/plain"</em> is specified for a FORM with + a mailto ACTION, Lynx will not hex escape the name=value pairs of + the FORM's content, and will use physical newlines instead of + '<em>&</em>' or '<em>;</em>' to separate the pairs, so that + the content will be readable directly. Otherwise, Lynx will mail + the content with the default:</p> + <pre> + <em>ENCTYPE="application/x-www-form-urlencoded"</em> ('<em>&</em>' separates pairs) +</pre>or: + <pre> + <em>ENCTYPE="application/sgml-form-urlencoded"</em> ('<em>;</em>' separates pairs) +</pre>if the latter was indicated. + + <p>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 <em>text/plain</em>, any script which decodes + the mailed content should ignore the physical newlines and + recognize only hex escaped newline characters as intended to be + present in the decoded content.</p> + + <p>If the mailto URL is not the ACTION for a FORM, and if an + external editor has been defined via the <em>Options Menu</em>, + the user is offered an option to include the currently displayed + document. If this option is accepted, each line of that document + is prefixed with a right-angle-bracket, and the prefixed + inclusion should be trimmed by the user to just those passages + relevant to the message which will be sent.</p> + <hr> + + <h2><a name="finger_url">The <em>finger</em> URL:</a></h2> + + <p>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:</p> + <pre> + finger://host finger://@host + finger://host/ finger://@host/ + finger://host/%2fw finger://@host/w + finger://host/w finger://host/w/ + finger://host/username[@host] finger://username@host + finger://host/username[@host]/ finger://username@host/ + finger://host/w/username[@host] finger://username@host/w + finger://host/%2fw%20username[@host] finger://host/username[@host]/w + finger://host/w/username +</pre> + + <p>Activating a finger URL will send a request to the finger + server via port 79 on the host specified. You can include + <em>:79</em> in the URL, but no other value is allowed. The + <em>/w</em> or <em>/%2fw</em> is used to request a full report + for finger servers which support it, and is not case sensitive + (i.e., can be <em>/W</em> or <em>/%2fW</em>). Any strings in the + report which appear to be a URL with a supported scheme will be + converted into a link for accessing that URL.</p> + + <p>An alternative way to access finger servers is via gopher URLs + with port 79 and the plain text (<em>0</em>) <em>gophertype</em> + specified:<br> + <em>gopher://host:79/0</em><br> + Lynx will handle such URLs equivalently to overt finger URLs, + including creation of links for any strings which appear to be + supported URLs.</p> + <hr> + + <h2><a name="cso_url">The <em>cso</em> URL:</a></h2> + + <p>The cso URL is intended to provide a gateway to CSO/PH (QI) + servers. The requests are made on port 105 by default + (<em>:105</em>), with the following overt cso URL format:<br></p> + <pre> + <em>cso://host</em> +</pre> + + <p>You also can use a gopher URL format with port 105 and the CSO + (<em>2</em>) <em>gophertype</em> specified:</p> + <pre> + <em>gopher://host:105/2</em> +</pre> + + <p>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.</p> + <hr> + + <h2><a name="bibp_url">The <em>bibp</em> URL:</a></h2> + + <p>Lynx provides built-in support for bibliographic protocol + (BibP). BibP links are links to published works such as books or + journal articles, without a predefined server. BibP links are + intended for resolution by a local bibhost server + (http://bibhost/) if it exists. Otherwise, resolution is + performed by a document-specified server or a known global + server.</p> + + <h2><a name="exec_url">The <em>lynxexec</em> and + <em>lynxprog</em> URLs:</a></h2> + + <p>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.:</p> + <pre> + <em>lynxexec:dir/date/size foo:[blah]</em> (VMS) + <em>lynxexec:ls -l /foo/blah</em> (Unix) + <em>lynxprog:news</em> +</pre>(Note, however, that restrictions on acceptable commands or +utilities may be imposed by the system administrator.) + + <p>You optionally can include <em>//localhost/</em> in the URL, + between the scheme field and the command, but that is always + implied. The lynxexec and lynxprog URLs differ only in that with + lynxexec you are prompted to enter <em>RETURN</em> before 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.</p> + + <p>These are Lynxisms and should be used only in local documents + intended solely for Lynx.</p> + <hr> + + <h2><a name="cgi_url">The <em>lynxcgi</em> URL:</a></h2> + + <p>The lynxcgi URL is implemented only on Unix, can be used as + the ACTION for a FORM, and if enabled in your Lynx image has the + format:</p> + <pre> + <em>lynxcgi://localhost/path_to_CGI_script</em> +</pre>where <em>//localhost</em> is optional and always implied; +the full path should be specified, as `~' is not recognized; if the +script is in the directory Lynx was started from, the simple file +name is adequate. The output of the script should be text/html and +is rendered and displayed by Lynx. Restrictions on use of lynxcgi +and on acceptable paths can be imposed in <em>userdefs.h</em> and +<em>lynx.cfg</em>, qv. + + <p>This is a Lynxism and should be used only in local documents + intended solely for Lynx, or for limited local testing of CGI + scripts without an http server.</p> + <hr> + + <h2><a name="ncftp_url">The <em>NcFTP</em> URL:</a></h2> + + <p>Lynx recognizes the NcFTP-style ftp URL, e.g.,</p> + <pre> + <cite>ftpHost</cite>:<cite>fileSpecification</cite> +</pre>for example + <pre> +<code> + ftp.gnu.org:/pub/gnu +</code> +</pre> + <hr> + + <h2><a name="internal_url">The <em>LYNXfoo</em> internal + URLs:</a></h2> + + <p>Lynx uses a variety of private URL schemes for communication + among its internal modules. They start with uppercase letters + <code>LYNX</code> by convention, although, as input, URL schemes + are recognized in a case-insensitive manner.</p> + + <p>As you discover what they are, and are tempted to use them + externally in documents, you should <em>resist</em> that + temptation:</p> + + <ul> + <li>There already is too much browser-specific markup + around...</li> + + <li>The schemes, or their meanings, may change between Lynx + versions.</li> + + <li>Even if a scheme stays the same, some aspect of its + behavior may be modified without notice, or the context in + which it is allowed may change.</li> + + <li>If it doesn't work as expected when used outside of the + intended purpose, don't expect anyone to "fix" it.</li> + </ul> + + <p>For example, tempting though it might be, do not use + these:</p> + <pre> + <em>Return to your <A HREF="LYNXHIST:0">Startfile</A></em> + <em>Review your <A HREF="LYNXKEYMAP:">Keymap</A></em> +</pre>(No, they won't do any harm. Yes, they work. But don't rely +on it.) + + <p>If you must try one, the second is OK from the command + line:<br></p> + <pre> + <em>lynx LYNXKEYMAP:</em> +</pre>But within Lynx, use the '<em>K</em>' keystroke command. +Sometimes it may be convenient to use a private scheme with +'<em>g</em>'oto, as in: + <pre> + <em>g LYNXMESSAGES:</em> + <em>g LYNXCOMPILEOPTS:</em> + <em>g LYNXCFG:</em> +</pre>But again, there usually is a way in which those special +pages are meant to be reached that is more convenient. +</body> +</html> |