diff options
| author | Thomas E. Dickey <dickey@invisible-island.net> | 1998-11-10 19:47:00 -0500 |
|---|---|---|
| committer | Thomas E. Dickey <dickey@invisible-island.net> | 1998-11-10 19:47:00 -0500 |
| commit | d3f9d5478df478427c2aa5db4507ddd0a38f0eb6 (patch) | |
| tree | e27eacd6bbda653dd77f11cc020b9e0a59f7f4fc /lynx_help/Lynx_users_guide.html | |
| parent | 18024037b515bfff83e0230b35151babe6005e18 (diff) | |
| download | lynx-snapshots-d3f9d5478df478427c2aa5db4507ddd0a38f0eb6.tar.gz | |
snapshot of project "lynx", label v2-8-2dev_2
Diffstat (limited to 'lynx_help/Lynx_users_guide.html')
| -rw-r--r-- | lynx_help/Lynx_users_guide.html | 545 |
1 files changed, 355 insertions, 190 deletions
diff --git a/lynx_help/Lynx_users_guide.html b/lynx_help/Lynx_users_guide.html index 49cec8d3..2341e928 100644 --- a/lynx_help/Lynx_users_guide.html +++ b/lynx_help/Lynx_users_guide.html @@ -1,12 +1,12 @@ <!DOCTYPE html public "-//IETF//DTD HTML 3.0//EN"> <html> <head> -<title>Lynx Users Guide v2.8</title> +<title>Lynx Users Guide v2.8.1</title> <link rev="made" href="mailto:lynx-dev@sig.net"> </head> <body> -<h1>Lynx Users Guide v2.8</h1> +<h1>Lynx Users Guide v2.8.1</h1> 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., @@ -18,7 +18,7 @@ well as files on remote systems running <em>http</em>, <em>gopher</em>, <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="#32">Current</a> versions of Lynx run on Unix, VMS, +<a href="#Hist">Current</a> versions of Lynx run on Unix, VMS, Windows95/NT, 386DOS and OS/2 EMX. <p>Lynx can be used to access information on the <em>WWW</em>, or to build @@ -27,57 +27,59 @@ 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. -<h2><A NAME="TOC"><em>Table of Contents</em></A></h2> +<h2 ID="TOC"><A NAME="Contents"><em>Table of Contents</em></A></h2> <ul> -<li><A HREF="#1">Lynx online help</A> -<li><A HREF="#2">Viewing local files with Lynx</A> -<li><A HREF="#3">Leaving Lynx</A> -<li><A HREF="#4">Starting Lynx with a Remote File</A> -<li><A HREF="#5">Starting Lynx with the WWW_HOME environment variable.</A> -<li><A HREF="#6">Navigating hypertext documents with Lynx</A> -<li><A HREF="#7">Printing, Mailing, and Saving rendered files to disk.</A> -<li><A HREF="#8">Viewing the HTML document source and editing documents</A> -<li><A HREF="#9">Downloading and Saving source files.</A> -<li><A HREF="#10">Reloading files and refreshing the display</A> -<li><A HREF="#11">Lynx searching commands</A> -<li><A HREF="#12">Lynx Options Menu</A> -<li><A HREF="#13">Comments and mailto: links</A> -<li><A HREF="#14">USENET News posting</A> -<li><A HREF="#15">Lynx bookmarks</A> -<li><A HREF="#16">Jump command</A> -<li><A HREF="#17">Directory Editing</A> -<li><A HREF="#18">Scrolling and Other useful commands</A> -<li><a href="#19">Lynx and HTML Forms</a> -<li><a href="#20">Lynx and HTML Tables</a> -| <a href="#21">Lynx and HTML Tabs</a> -<li><a href="#22">Lynx and HTML Frames</a> -| <a href="#23">Lynx and HTML Banners</a> -<li><a href="#24">Lynx and HTML Footnotes</a> -| <a href="#25">Lynx and HTML Notes</a> -<li><a href="#26">Lynx and HTML Lists</a> -<li><a href="#27">Lynx and HTML Quotes</a> -<li><a href="#28">Lynx and Client-Side-Image-Maps</a> -<li><a href="#29">Lynx and Client-Side-Pull</a> -<li><a href="#30">Lynx and State Management</a> (Me want <em>cookie</em>!) -<li><A HREF="#31">The Lynx command line</A> -<li><A HREF="#32">Lynx development history</A> +<li><A HREF="#Help" NAME="ToC-Help">Lynx online help</A> +<li><A HREF="#Local" NAME="ToC-Local">Viewing local files with Lynx</A> +<li><A HREF="#Leaving" NAME="ToC-Leaving">Leaving Lynx</A> +<li><A HREF="#Remote" NAME="ToC-Remote">Starting Lynx with a Remote File</A> +<li><A HREF="#EnVar" NAME="ToC-EnVar">Starting Lynx with the WWW_HOME environment variable.</A> +<li><A HREF="#IntraDocNav" NAME="ToC-IntraDocNav">Navigating hypertext documents with Lynx</A> +<li><A HREF="#Disposing" NAME="ToC-Disposing">Printing, Mailing, and Saving rendered files to disk.</A> +<li><A HREF="#LocalSource" NAME="ToC-LocalSource">Viewing the HTML document source and editing documents</A> +<li><A HREF="#RemoteSource" NAME="ToC-RemoteSource">Downloading and Saving source files.</A> +<li><A HREF="#ReDo" NAME="ToC-ReDo">Reloading files and refreshing the display</A> +<li><A HREF="#Search" NAME="ToC-Search">Lynx searching commands</A> +<li><A HREF="#InteractiveOptions" NAME="ToC-InteractiveOptions">Lynx Options Menu</A> +<li><A HREF="#Mail" NAME="ToC-Mail">Comments and mailto: links</A> +<li><A HREF="#News" NAME="ToC-News">USENET News posting</A> +<li><A HREF="#Bookmarks" NAME="ToC-Bookmarks">Lynx bookmarks</A> +<li><A HREF="#Jumps" NAME="ToC-Jumps">Jump command</A> +<li><A HREF="#DirEd" NAME="ToC-DirEd">Directory Editing</A> +<li><A HREF="#MiscKeys" NAME="ToC-MiscKeys">Scrolling and Other useful commands</A> +<li><a href="#Forms" NAME="ToC-Forms">Lynx and HTML Forms</a> +<li><a href="#Tables" NAME="ToC-Tables">Lynx and HTML Tables</a> +| <a href="#Tabs" NAME="ToC-Tabs">Lynx and HTML Tabs</a> +<li><a href="#Frames" NAME="ToC-Frames">Lynx and HTML Frames</a> +| <a href="#Banners" NAME="ToC-Banners">Lynx and HTML Banners</a> +<li><a href="#Footnotes" NAME="ToC-Footnotes">Lynx and HTML Footnotes</a> +| <a href="#Notes" NAME="ToC-Notes">Lynx and HTML Notes</a> +<li><a href="#Lists" NAME="ToC-Lists">Lynx and HTML Lists</a> +<li><a href="#Quotes" NAME="ToC-Quotes">Lynx and HTML Quotes</a> +<li><a href="#USEMAP" NAME="ToC-USEMAP">Lynx and Client-Side-Image-Maps</a> +<li><a href="#Refresh" NAME="ToC-Refresh">Lynx and Client-Side-Pull</a> +<li><a href="#Cookies" NAME="ToC-Cookies">Lynx and State Management</a> (Me want <em>cookie</em>!) +<li><A HREF="#Invoking" NAME="ToC-Invoking">The Lynx command line</A> +<li><A HREF="#lynx.cfg" NAME="ToC-lynx.cfg">Main configuration file lynx.cfg</A> +<li><A HREF="#Hist" NAME="ToC-Hist">Lynx development history</A> </ul> -<h2><A NAME="1"><em>Lynx online help</em></A></h2> +<h2 ID="Help"><A NAME="Help"><em>Lynx online help</em></A></h2> 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="#6">Navigating hypertext documents with Lynx</A> for -information on navigating through the help files. +'<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>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). -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-Help">ToC</A>] -<h2><A NAME="2"><em>Viewing local files with Lynx</em></A></h2> +<h2 ID="Local"><A NAME="Local"><em>Viewing local files with Lynx</em></A></h2> Lynx can be started by entering the Lynx command along with the name of a file to display. For example these commands could @@ -151,18 +153,18 @@ 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. Any number of additional download methods may be defined in the -lynx.cfg file by the system administrator. Programs like kermit, zmodem -and FTP are some possible options. [<A HREF="#TOC">ToC</A>] +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. [<A HREF="#ToC-Local">ToC</A>] -<h2><A NAME="3"><em>Leaving Lynx</em></A></h2> +<h2 ID="Leaving"><A NAME="Leaving"><em>Leaving Lynx</em></A></h2> 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. [<A HREF="#TOC">ToC</A>] +<em>Control-D</em> to quit without verification. [<A HREF="#ToC-Leaving">ToC</A>] -<h2><A NAME="4"><em>Starting Lynx with a Remote File</em></A></h2> +<h2 ID="Remote"><A NAME="Remote"><em>Starting Lynx with a Remote File</em></A></h2> If you wish to view a remote file (that is, a file residing on some computer system other than the one upon which you are running @@ -219,10 +221,9 @@ portions of it in the startfile argument. For example:<br> <tab indent="62">will be expanded to:<br> <tab indent="14"><em>ftp://ftp.more.net/pub</em><br> See <a href="lynx_url_support.html">URL Schemes Supported by Lynx</a> for -more detailed information. [<A HREF="#TOC">ToC</A>] +more detailed information. [<A HREF="#ToC-Remote">ToC</A>] -<h2><A NAME="5" -><em>Starting Lynx with the WWW_HOME environment variable.</em></A></h2> +<h2 ID="EnVar"><A NAME="EnVar"><em>Starting Lynx with the WWW_HOME environment variable.</em></A></h2> You may also specify a starting file for Lynx using the WWW_HOME environment variable, @@ -242,9 +243,9 @@ environment variable, </dl> Note that on VMS the double-quoting <em>must</em> be included to preserve -casing. +casing. [<A HREF="#ToC-EnVar">ToC</A>] -<h2><A NAME="6"><em>Navigating hypertext documents with Lynx</em></A></h2> +<h2 ID="IntraDocNav"><A NAME="IntraDocNav"><em>Navigating hypertext documents with Lynx</em></A></h2> The process of moving within a hypertext web, selecting and displaying links is known as "navigation." With Lynx almost all navigation can be @@ -268,7 +269,7 @@ accomplished with the arrow keys and the numeric keypad. There are also a few other keyboard commands to aid in navigation. The Control and Function keys used for navigation within the current document are described in <A -HREF="#18"><em>Scrolling and Other useful commands</em></A>. Some +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 @@ -297,9 +298,9 @@ program you are using was configured. will automatically prompt for a username and a password. If you give the correct information, you will then be served the requested information. Lynx will automatically send your username and password to the same server -if it is needed again. [<A HREF="#TOC">ToC</A>] +if it is needed again. [<A HREF="#ToC-IntraDocNav">ToC</A>] -<h2><A NAME="7" +<h2 ID="Disposing"><A NAME="Disposing" ><em>Printing, Mailing, and Saving rendered files to disk.</em></A></h2> Rendered HTML documents, and plain text files, may be printed using the @@ -317,8 +318,8 @@ mail files to themselves and print the entire file to the screen. 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. Any number of additional print options may also be -available as configured by your system administrator. +space. Additional print options may also be +available as configured in the <A HREF="#lynx.cfg">lynx.cfg</A> file. <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 @@ -326,10 +327,11 @@ 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>Note that if you want exact copies of text files without any expansions -of TAB characters to spaces you should use the <a href="#9">Download</a> -options. [<A HREF="#TOC">ToC</A>] +of TAB characters to spaces you should use the +<a href="#RemoteSource">Download</a> options. +[<A HREF="#ToC-Disposing">ToC</A>] -<h2><A NAME="8" +<h2 ID="LocalSource"><A NAME="LocalSource" ><em>Viewing the HTML document source and editing documents</em></A></h2> When viewing HTML documents it is possible to retrieve and display the @@ -342,7 +344,7 @@ When viewing unrendered documents you may print them as any normal document. <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="#9">Download</a> the source. +href="#RemoteSource">Download</a> the source. <p>NOTE: When saving an HTML document it is important to name the document with a <em>.html</em> extension, if you want to read it with @@ -366,32 +368,45 @@ 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. [<A HREF="#TOC">ToC</A>] - -<h2><A NAME="9"><em>Downloading and Saving source files.</em></A></h2> - -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 or modification, into a temporary -location and present the user with a list of options, as when a link for a -binary file of a type for which no viewer has been mapped is activated. -As described above, the only default <em>Download option</em> is -<em>Save to disk</em>, which is disabled if Lynx is running in -anonymous mode, and any number of additional download methods such as -kermit and zmodem may be defined in the <em>lynx.cfg</em> file by the -system administrator. Downloading the sources of HTML and plain text -files, instead of toggling to <a href="#8">display the source</a> -('<em>\</em>') and then using <a href="#7">Printing</a> options, ensures -that no modifications of the source (e.g., expansions of TAB characters -to a series of spaces) will occur. +examined. [<A HREF="#ToC-LocalSource">ToC</A>] + +<h2 ID="RemoteSource"><A NAME="RemoteSource"><em>Downloading and Saving source files.</em></A></h2> + +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>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 +<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. -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-RemoteSource">ToC</A>] -<h2><A NAME="10" +<h2 ID="ReDo"><A NAME="ReDo" ><em>Reloading files and refreshing the display</em></A></h2> The RELOAD (<em>Control-R</em>) command will reload and re-render the file @@ -406,17 +421,19 @@ 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="#19"><em>Lynx and HTML Forms</em></A>). [<A HREF="#TOC">ToC</A>] +HREF="#Forms"><em>Lynx and HTML Forms</em></A>). +[<A HREF="#ToC-ReDo">ToC</A>] -<h2><A NAME="11"><em>Lynx searching commands</em></A></h2> +<h2 ID="Search"><A NAME="Search"><em>Lynx searching commands</em></A></h2> Two commands activate searching in Lynx: '<em>/</em>' and '<em>s</em>'. -<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="#12">Options Menu</a>. The search -options are case sensitive and case insensitive. These searches are entirely -local to Lynx. +<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>Some documents are designated <em>index documents</em> by virtue of an ISINDEX element in their HEAD section. These documents can be used to @@ -441,7 +458,7 @@ 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>Although <a href="#19">HTML Forms</a> have largely replaced index +<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 @@ -450,13 +467,68 @@ strings for searching it, and include an element such as:<BR> <tab indent="12"><em><ISINDEX <tab id="idx">PROMPT="Enter WAIS query:"<BR> <tab to="idx">HREF="wais://net.bio.net/biologists-addresses"></em><BR> for submitting a search of the Biologist's Addresses database directly -to the net.bio.net WAIS server. [<A HREF="#TOC">ToC</A>] +to the net.bio.net WAIS server. [<A HREF="#ToC-Search">ToC</A>] -<h2><A NAME="12"><em>Lynx Options Menu</em></A></h2> +<h2 ID="InteractiveOptions"><A NAME="InteractiveOptions"><em>Lynx Options Menu</em></A></h2> The Lynx <em>Options Menu</em> may be accessed by pressing the '<em>o</em>' -key. The current <em>Options Menu</em> contains the following configurable -options. +key. The current Options Menu allows you to change options which are +useful at runtime. Most of these are read/saved from your .lynxrc file. +Other options are stored in the <A HREF="#lynx.cfg">lynx.cfg</A> file. + +<p>Lynx supports two styles of options menu. The new style shown below is an HTML +file generated at runtime: + +<pre> + + Options Menu (Lynx Version 2.8.1pre.2) + + Accept Changes - Reset Changes Left Arrow cancels changes HELP! + + Save options to disk: [_] + + Personal Preferences + Cookies : [ask user..] + Editor : __________________________________________ + Emacs keys : [OFF] + Keypad mode : [Numbers act as arrows.............] + Personal mail address : __________________________________________ + Popups for select fields : [ON.] + Searching type : [Case insensitive] + Show color : [ON....] + Show cursor : [OFF] + User mode : [Novice......] + Verbose images : [OFF] + VI keys : [OFF] + X Display : __________________________________________ + + Bookmark Options + Multi-bookmarks : [OFF.....] + Bookmarks file : __________________________________________ + + Character Set Options + Assumed document character set : [iso-8859-1......] + Display character set : [Western (ISO-8859-1)...........] + Raw 8-bit : [ON.] + + File Management Options + Ftp sort criteria : [By Name] + Local directory sort criteria : [Mixed style......] + + Headers transferred to remote server + Preferred document character set : _________________________________ + Preferred document language : _________________________________ + User-Agent header : __________________________________________ + + Check your lynx.cfg here + + Accept Changes - Reset Changes Left Arrow cancels changes + +</pre> + +<p>The old style of options menu is a fixed form. Normally this will be +compiled into Lynx, and is accessed by setting FORMS_OPTIONS true in your +<A HREF="#lynx.cfg">lynx.cfg</A> file. <pre> Options Menu @@ -476,7 +548,7 @@ options. 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 + U)ser mode : Advanced verbose images (!) : ON user (A)gent : [User-Agent header] local e(X)ecution links : FOR LOCAL FILES ONLY </pre> @@ -494,13 +566,14 @@ to get back to the <em>Command?</em> prompt. to toggle the choices and press the <em>Return</em> key to finish the change. -<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="#19">HTML Forms</a>. The popup windows will be invoked -only if you have popups for select fields set to ON (see below). Otherwise, -your cursor will be positioned at the current choice, and you can press any -key to cycle through the choices, then press the <em>Return</em> key to -finish the change. +<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>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 @@ -542,7 +615,7 @@ return to Lynx or the '<em>></em>' command to save the options to a href="keystrokes/edit_help.html">Line Editor</a>. Bookmark files allow frequently traveled links to be stored in personal easy to access files. Using the '<em>a</em>'dd bookmark - link command (see <a href="#15">Lynx bookmarks</a>) you may save + 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 @@ -571,7 +644,8 @@ return to Lynx or the '<em>></em>' command to save the options to a yourself and will be included as the From: address in any mail or comments that you send. It will also be sent as the From: field in HTTP or HTTPS requests if inclusion of that header - has been enabled via the NO_FROM_HEADER definition in lynx.cfg + 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. @@ -611,24 +685,41 @@ return to Lynx or the '<em>></em>' command to save the options to a 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. + 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.) <dt>Raw 8-bit or CJK Mode <dd>Whether 8-bit characters are assumed to correspond with the - selected character set and therefore are processed without + display character set and therefore are processed without translation via the chartrans conversion tables. Should be ON - by default when the selected character set is one of the Asian - (CJK) sets and the 8-bit characters are Kanji multibytes. - Should be OFF for the other character sets, but can be turned ON + 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. The setting also can be toggled via the RAW_TOGGLE + 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. + <dt>Assumed document character set + <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. + <dt>Show color. <dd>This option will be present if color support is available. If set to ON or ALWAYS, color mode will be forced on if possible. @@ -709,9 +800,9 @@ return to Lynx or the '<em>></em>' command to save the options to a 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" + <a href="keystrokes/follow_help.html" >Follow link (or page) number:</a> and<br> -  <a + <a href="keystrokes/follow_help.html#select-option" >Select option (or page) number:</a><br> help for more information. @@ -751,23 +842,31 @@ return to Lynx or the '<em>></em>' command to save the options to a link at the bottom of the screen. </dl> + <dt>Verbose Images + <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. + <dt>User Agent <dd>The header string which Lynx sends to servers to indicate the User-Agent is displayed here. Changes may be disallowed via the <em>-restrictions</em> switch. Otherwise, the header can be - changed temporarily to a string such as <em>L_y_n_x/2.8</em> + changed temporarily to a string such as <em>L_y_n_x/2.8.1</em> 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 - <em>Options Menu</em>. Whenever the User-Agent header is + Options Menu. Whenever the User-Agent header is changed, the current document is reloaded, with the no-cache - flags set, on exit from the <em>Options Menu</em>. Changes of + flags set, on exit from the Options Menu. Changes of the header are not saved in the RC file. <dd><em>NOTE</em> that Netscape Communications Corp. has claimed that false transmissions of "Mozilla" as the User-Agent are a copyright infringement, which will be prosecuted. <em>DO NOT</em> - misrepresent Lynx as Mozilla. The <em>Options Menu</em> issues + 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". @@ -796,10 +895,10 @@ return to Lynx or the '<em>></em>' command to save the options to a executed Lynx will show the script within the Lynx window and inform the user that the script is not allowed to be executed and will ask the user to check his/her options. - [<A HREF="#TOC">ToC</A>] + [<A HREF="#ToC-InteractiveOptions">ToC</A>] </dl> -<h2><A NAME="13"><em>Comments and mailto: links</em></A></h2> +<h2 ID="Mail"><A NAME="Mail"><em>Comments and mailto: links</em></A></h2> 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 @@ -825,12 +924,13 @@ scheme will allow you to enter your message. 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 lynx.cfg and is accessible, +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.[<A HREF="#TOC">ToC</A>] +also will cancel the mailing.[<A HREF="#ToC-Mail">ToC</A>] -<h2><A NAME="14"><em>USENET News posting</em></A></h2> +<h2 ID="News"><A NAME="News"><em>USENET News posting</em></A></h2> While reading <a href="http://www.w3.org/hypertext/DataSources/News/Groups/Overview.html" @@ -855,14 +955,14 @@ received the article supports posting from your site, a link that says Once you have typed in your message, you will be asked for confirmation of whether to proceed with the posting, and whether to append your signature file if one was defined in - lynx.cfg and is accessible. See <a + <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">ToC</A>] + [<A HREF="#ToC-News">ToC</A>] </dl> -<h2><A NAME="15"><em>Lynx bookmarks</em></A></h2> +<h2 ID="Bookmarks"><A NAME="Bookmarks"><em>Lynx bookmarks</em></A></h2> It is often useful to place a bookmark to aid in returning quickly to a document. To use the bookmark feature you must first use the @@ -910,16 +1010,17 @@ 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>When multi-bookmarks (see <a href="#12">Options Menu</a>) is OFF, -you will always view or add links to the default bookmark file. When -it is STANDARD, a menu of up to 26 bookmark files will be invoked, -and you select the bookmark file by entering its letter token. When -it is ADVANCED, you will be prompted for the letter token, but can -enter '<em>=</em>' to invoke the STANDARD selection menu, or -<em>RETURN</em> for the default bookmark file. -[<A HREF="#TOC">ToC</A>] +<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>] -<h2><A NAME="16"><em>Jump Command</em></a></h2> +<h2 ID="Jumps"><A NAME="Jumps"><em>Jump Command</em></a></h2> A feature similar to the Lynx bookmarks is the jump command. The jump command allows you to enter a shortcut name to access a URL. If the jump @@ -931,11 +1032,12 @@ of shortcut names available. 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>Note to System Administrators: Read the <em>lynx.cfg</em> file on how +<p>Note to System Administrators: +Read the <A HREF="#lynx.cfg">lynx.cfg</A> file on how to set up the jump command for your system and how to define shortcut names. -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-Jumps">ToC</A>] -<h2><A NAME="17"><em>Directory Editing</em></a></h2> +<h2 ID="DirEd"><A NAME="DirEd"><em>Directory Editing</em></a></h2> Lynx offers extended DIRED support on Unix (on VMS the more powerful CSwing program is recommended for character cell terminals, and can be @@ -979,9 +1081,9 @@ on your local system. The commands available in DIRED mode are <dd>Type '<em>u</em>' to upload a file to the present directory. Upload methods are defined by your system administrator. </dl> -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-DirEd">ToC</A>] -<h2><A NAME="18"><em>Scrolling and Other useful commands</em></A></h2> +<h2 ID="MiscKeys"><A NAME="MiscKeys"><em>Scrolling and Other useful commands</em></A></h2> 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 @@ -1008,7 +1110,8 @@ commands. 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="#12">Lynx Options Menu</A>). + enabled (see <A HREF="#InteractiveOptions">Lynx + Options Menu</A>). <dt><em>^F</em> <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 @@ -1096,7 +1199,7 @@ commands. document's author. <dt><em>;</em> <dd>The <em>;</em> command shows the <em>Lynx Trace Log</em> - (<em>lynx.trace</em> in the home directory) if one has been + (<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 and other stderr messages will be sent to the screen (and will disturb the normal display) unless the system supports @@ -1155,10 +1258,10 @@ commands. href="keystrokes/follow_help.html#select-option" >Select option (or page) number:</a><br> prompts. - [<A HREF="#TOC">ToC</A>] + [<A HREF="#ToC-MiscKeys">ToC</A>] </dl> -<h2><A NAME="19"><em>Lynx and HTML Forms</em></a></h2> +<h2 ID="Forms"><A NAME="Forms"><em>Lynx and HTML Forms</em></a></h2> This section describes the Lynx Forms Interface. HTML gives document providers the ability to create on-line forms which may be filled out @@ -1195,10 +1298,11 @@ options from a list, and fields for entering text. <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="#11">searching</a> commands for navigating to options which + <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="#12">Options Menu</a>, in which case the selection + 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. @@ -1271,7 +1375,7 @@ 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 <em>lynx.cfg</em>, and toggled via the +can be changed via <A HREF="#lynx.cfg">lynx.cfg</A>, and toggled via the <em>-resubmit_posts</em> command line switch. <p>If the form has one <em>text entry</em> field and no other fields except, @@ -1290,7 +1394,7 @@ content. <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="#28">image maps</a>, and the x,y coordinates of +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 @@ -1385,9 +1489,9 @@ any document: <tab indent="12" ><em><META <tab id="cdis">HTTP-EQUIV="Content-Disposition"<BR> <tab to="cdis">CONTENT="file; filename=name.suffix"></em><BR> -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-Forms">ToC</A>] -<h2><A NAME="20"><em>Lynx and HTML Tables</em></a></h2> +<h2 ID="Tables"><A NAME="Tables"><em>Lynx and HTML Tables</em></a></h2> HTML includes markup for creating <em>tables</em> structured as arrays of cells aligned by columns and rows on the displayed page. @@ -1407,11 +1511,11 @@ alignments intended for the <em>table</em> will be missed. <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="#21">HTML Tabs</a>. An example <em>table</em> using <em>TAB</em> +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. -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-Tables">ToC</A>] -<h2><A NAME="21"><em>Lynx and HTML Tabs</em></a></h2> +<h2 ID="Tabs"><A NAME="Tabs"><em>Lynx and HTML Tabs</em></a></h2> Lynx implements the <a href="http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> @@ -1429,11 +1533,11 @@ distribution as a model for using this functionality. <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="#8">source</a> and <a -href="#11">search</a> for <em><tab</em> to examine the use of TAB markup -in these documents. [<A HREF="#TOC">ToC</A>] +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. [<A HREF="#ToC-Tabs">ToC</A>] -<h2><A NAME="22"><em>Lynx and HTML Frames</em></a></h2> +<h2 ID="Frames"><A NAME="Frames"><em>Lynx and HTML Frames</em></a></h2> Some implementations of HTML include markup, primarily designed for graphic clients, that is intended to create an array of simultaneously displayed, @@ -1451,14 +1555,14 @@ 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. -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-Frames">ToC</A>] <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. -<h2><A NAME="23"><em>Lynx and HTML Banners</em></a></h2> +<h2 ID="Banners"><A NAME="Banners"><em>Lynx and HTML Banners</em></a></h2> Some implementations of HTML markup include provisions for creating a non-scrolling window to be positioned at the top of each page, containing @@ -1523,9 +1627,9 @@ 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. -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-Banners">ToC</A>] -<h2><A NAME="24"><em>Lynx and HTML Footnotes</em></a></h2> +<h2 ID="Footnotes"><A NAME="Footnotes"><em>Lynx and HTML Footnotes</em></a></h2> Lynx implements the <a href="http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> @@ -1547,9 +1651,9 @@ does not use popups for FN blocks.</a></p><em></FN></em> 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. -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-Footnotes">ToC</A>] -<h2><A NAME="25"><em>Lynx and HTML Notes</em></a></h2> +<h2 ID="Notes"><A NAME="Notes"><em>Lynx and HTML Notes</em></a></h2> Lynx implements the <a href="http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> @@ -1562,7 +1666,8 @@ 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="#24">HTML Footnotes</a>, but the NOTE block need not be placed +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> <tab indent="12"><em><NOTE CLASS="warning" ID="too-bad"><BR> @@ -1571,9 +1676,9 @@ NOTE in the HTML 3.2 draft.</p><BR> <tab indent="12"></NOTE></em><BR> 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. -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-Notes">ToC</A>] -<h2><A NAME="26"><em>Lynx and HTML Lists</em></a></h2> +<h2 ID="Lists"><A NAME="Lists"><em>Lynx and HTML Lists</em></a></h2> Lynx implements the <a href="http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> @@ -1631,9 +1736,9 @@ nesting levels. by default, i.e., single spaces between LH and LI elements within those blocks. For DL blocks, double spacing will be used to separate the DT and DD elements unless the COMPACT attribute has been specified. -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-Lists">ToC</A>] -<h2><A NAME="27"><em>Lynx and HTML Quotes</em></a></h2> +<h2 ID="Quotes"><A NAME="Quotes"><em>Lynx and HTML Quotes</em></a></h2> The <a href="http://www.w3.org/MarkUp/html3/Contents.html">HTML 3.0</a> and @@ -1656,10 +1761,11 @@ its first line. (<em>"</em>) versus grave accent (<em>`</em>) and apostrophe (<em>'</em>), respectively, for even versus odd depths in the nest. -<p>Any ID attributes in BLOCKQUOTE, BQ or Q elements will be treated as -named <em>A</em>nchors. [<A HREF="#TOC">ToC</A>] +<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. [<A HREF="#ToC-Quotes">ToC</A>] -<h2><A NAME="28"><em>Lynx and Client-Side-Image-Maps</em></a></h2> +<h2 ID="USEMAP"><A NAME="USEMAP"><em>Lynx and Client-Side-Image-Maps</em></a></h2> HTML includes markup, designed primarily for graphic clients, that treats inlined images as maps, such that areas of the image within which a mouse @@ -1707,7 +1813,8 @@ map can be accessed, and their nature indicated via ALT attributes, Lynx-friendly sites can map 0,0 such that the server returns a for-text-client document homologous to the content of FIG elements (see below). Inclusion of such a link for submissions to the server can be -disabled by default via the configuration file (lynx.cfg), and the +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>Lynx also recognizes the <a @@ -1725,9 +1832,9 @@ 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>. -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-USEMAP">ToC</A>] -<h2><A NAME="29"><em>Lynx and Client-Side-Pull</em></a></h2> +<h2 ID="Refresh"><A NAME="Refresh"><em>Lynx and Client-Side-Pull</em></a></h2> HTML includes provision for passing instructions to clients via directives in META elements, and one such instruction, via the token <em>Refresh</em>, @@ -1754,16 +1861,16 @@ is not critical and you can activate the link whenever you like. If it is long (e.g., 60 seconds), a server process may be generating new documents or images at that interval, and you would be wasting bandwidth by activating the link at a shorter interval. -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-Refresh">ToC</A>] -<h2><A NAME="30"><em>Lynx State Management</em></A> +<h2 ID="Cookies"><A NAME="Cookies"><em>Lynx State Management</em></A> (Me want <em>cookie</em>!)</h2> HTTP provides a means to carry state information across successive connections between a browser and an http server. Normally, http servers respond to each browser request without relating that request to previous or subsequent requests. Though the inclusion of INPUT fields with -TYPE="hidden" can be used as a sort of state management by <a href="#19" +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 @@ -1777,9 +1884,20 @@ 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 (<em>lynx.cfg</em>) +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>When cookie support is enabled, <em>Set-Cookie</em> MIME headers received from an http server invoke confirmation prompts with possible @@ -1792,9 +1910,10 @@ prompts, or ne'<em>V</em>'er to never allow cookies from that 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>. The -<em>Cookie Jar</em>, and any '<em>A</em>'lways or ne'<em>V</em>'er -'allow' settings, do not presently outlast the Lynx session. +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>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 @@ -1815,9 +1934,9 @@ 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>. -[<A HREF="#TOC">ToC</A>] +[<A HREF="#ToC-Cookies">ToC</A>] -<h2><A NAME="31"><em>The Lynx command line</em></A></h2> +<h2 ID="Invoking"><A NAME="Invoking"><em>The Lynx command line</em></A></h2> 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 @@ -1864,6 +1983,8 @@ where 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, [???]. + <dt><code>-accept_all_cookies</code> + <dd>accept all cookies. <dt><code>-anonymous</code> <dd>used to specify the anonymous account. <dt><code>-assume_charset=MIMEname</code> @@ -1902,7 +2023,7 @@ where <dd>enable case-sensitive string searching. <dt><code>-cfg=FILENAME</code> <dd>specifies a Lynx configuration file other than the default - lynx.cfg. + <A HREF="#lynx.cfg">lynx.cfg</A>. <dt><code>-child</code> <dd>exit on left-arrow in startfile, and disable save to disk. <dt><code>-color</code> @@ -2027,6 +2148,8 @@ where <dd>disable the retrieval status messages. <dt><code>-number_links</code> <dd>force numbering of links. + <dt><code>-partial</code> + <dd>display partial pages while downloading. <dt><code>-pauth=ID:PW</code> <dd>set authorization ID and password for a protected proxy server at startup. Be sure to protect any script files @@ -2034,7 +2157,8 @@ where <dt><code>-popup</code> <dd>toggles handling of single-choice SELECT options via popup windows or as lists of radio buttons. The default - configuration can be changed in userdefs.h or lynx.cfg. + 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. <dt><code>-post_data</code> @@ -2161,7 +2285,8 @@ where corner but will instead be positioned at the start of the currently selected link. Show cursor is the default for systems without FANCY_CURSES capabilities. The default - configuration can be changed in userdefs.h or lynx.cfg. + 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. <dt><code>-soft_dquotes</code> @@ -2174,6 +2299,8 @@ where <dt><code>-startfile_ok</code> <dd>allow non-http startfile and homepage with <em>-validate</em>. + <dt><code>-tagsoup</code> + <dd>initialize DTD with "TagSoup" tables. <dt><code>-telnet</code> <dd>disable recognition of telnet commands. <dt><code>-term=TERM</code> @@ -2183,7 +2310,7 @@ where a script that, in turn, starts another Lynx process.) <dt><code>-tlog</code> <dd>toggles use of a <em>Lynx Trace Log</em> for the current - session. The log is named <em>lynx.trace</em> and is + 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 TOGGLE_TRACE (<em>Control-T</em>) @@ -2194,7 +2321,7 @@ where keystroke command. <dt><code>-trace</code> <dd>turns on Lynx trace mode. If a Lynx Trace Log - (<em>lynx.trace</em> in the home directory) has + (<em>Lynx.trace</em> in the home directory) has been started for the current session, all trace and other stderr messages are written to that log, and can be examined during the session via the TRACE_LOG @@ -2211,8 +2338,11 @@ where <dt><code>-validate</code> <dd>accept only http URLs (for validation). Complete security restrictions also are implemented. + <dt><code>-verbose</code> + <dd>toggles [LINK], [IMAGE] and [INLINE] comments + with filenames of these images. <dt><code>-version</code> - <dd>print version information + <dd>print version information. <dt><code>-vikeys</code> <dd>enable vi-like key movement. <dt><code>-width=NUMBER</code> @@ -2222,9 +2352,43 @@ where <p>No options are required, nor is a startfile argument required. White space may be substituted for any equal sign ('<em>=</em>') -appearing in the option list above. [<A HREF="#TOC">ToC</A>] +appearing in the option list above. [<A HREF="#ToC-Invoking">ToC</A>] + + +<h2 ID="lynx.cfg"><A NAME="lynx.cfg"><em>Main configuration file lynx.cfg</em></A></h2> + +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>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. + +<p>To see the current lynx.cfg state you may press <em>'='</em> key +for <em>Lynx Information Page</em> and follow <em>your lynx.cfg</em> link +from there near the top. + +<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. + + +[<A HREF="#ToC-lynx.cfg">ToC</A>] -<h2><A NAME="32"><em>Lynx development history</em></A></h2> +<h2 ID="Hist"><A NAME="Hist"><em>Lynx development history</em></A></h2> Lynx grew out of efforts to build a campus-wide information system at The University of Kansas. The earliest versions of Lynx provided a @@ -2275,6 +2439,7 @@ The Lynx2-6FM code set was released as v2.7 in February 1997. The v2-7FM code set was released as v2.7.1 in April 1997. The v2-7-1FM code set was released as v2.7.2 in January 1998. The 2.7.1 development set was released as v2.8 in March 1998. +The 2.8 development set was released as v2.8.1 in October 1998. <p>Since early 1997, the Lynx code has expanded into autoconfigure and PC versions. The branching of the Lynx source base from a single |