Switch branches/tags
Nothing to show
Find file
Fetching contributors…
Cannot retrieve contributors at this time
3156 lines (2864 sloc) 167 KB
<title>Lynx Users Guide v2.8.6</title>
<link rev="made" href="">
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<h1>Lynx Users Guide v2.8.6</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.,
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>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.
<h2 ID="TOC"><A NAME="Contents"><em>Table of Contents</em></A></h2>
<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="#ColorMouse" NAME="ToC-ColorMouse">Using Color &amp; the Mouse</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>
| <a href="#Images" NAME="ToC-Images">Lynx and HTML Images</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="#Eightbit" NAME="ToC-Eightbit">Lynx and HTML Internationalization: 8bit, UNICODE, etc.</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="#Environment" NAME="ToC-Environments">Environment variables used by Lynx</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>
<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="#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-Help">ToC</A>]
If you want to recall recent status-line messages, you can do so
by entering the `g' command, followed by `LYNXMESSAGES:'.
<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
all be used to display an arbitrary ASCII text or HTML file:
<dd><code>lynx filename</code>
<dd><code>lynx /home/my-dir/filename</code>
<dd><code>lynx ~/filename</code>
<dd><code>lynx filename</code>
<dd><code>lynx dua5:[my-directory]filename</code>
<dd><code>lynx /dua5/my-directory/filename</code>
<dd><code>lynx ~/filename</code>
<dd><code>lynx sys$login:filename</code>
<dd><code>lynx /sys$login/filename</code>
<dd><code>lynx file:///filename</code>
<dd><code>lynx filename</code>
<dd><code>lynx c:/dir/filename</code>
<dd><code>lynx //n/dir/filename</code>
<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>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>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>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>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>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. [<A HREF="#ToC-Local">ToC</A>]
<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-Leaving">ToC</A>]
<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
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><code>PROTOCOL :// HOST / PATH</code>
<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>is the Internet address of the computer system on which the
server is running, and
<dd>is a scheme-specific field which for some schemes may
correspond to a directory path and/or filename.
Here are some sample URLs.
<dt>HTTP (HyperText Transfer Protocol)
<dt>FTP (File Transfer Protocol)
<dt>WAIS (Wide Area Information Service protocol)
<dt>A URL may be specified to Lynx on the command line, as in:
Lynx also will attempt to create a complete URL if you include adequate
portions of it in the startfile argument. For example:<br>
<em>wfbr</em> will be expanded to:
<em></em> and:
<em></em> will be expanded to:
See <a href="lynx_url_support.html">URL Schemes Supported by Lynx</a> for
more detailed information. [<A HREF="#ToC-Remote">ToC</A>]
<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,
<dd><code>export WWW_HOME=</code>
<dd><code>setenv WWW_HOME</code>
<dd><code>define "WWW_HOME" ""</code>
<dd><code>WWW_HOME= [or in registry]</code>
Note that on VMS the double-quoting <em>must</em> be included to preserve
casing. [<A HREF="#ToC-EnVar">ToC</A>]
<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
accomplished with the arrow keys and the numeric keypad.
| TOP | /|\ | Page |
arrow keys | of | | | UP |
| text 7| | 8| 9|
+---------+ +-------+-------+-------+
| SELECT | | | | |
| prev /|\| | &lt;--- | | ---&gt; |
| link | | | 4| 5| 6|
+---------+---------+---------+ +-------+-------+-------+
| BACK | SELECT | DISPLAY | | END | | | Page |
|&lt;-- prev | next | | sel. --&gt;| | of | | | DOWN |
| doc. | link \|/| link | | text 1| \|/ 2| 3|
+---------+---------+---------+ +-------+-------+-------+
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>If you choose a link to a server with active access authorization, Lynx
will automatically prompt for a username and a password. If you give the
correct information, you will then be served the requested information.
Lynx will automatically send your username and password to the same server
if it is needed again. [<A HREF="#ToC-IntraDocNav">ToC</A>]
<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
'<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>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>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>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.
[<A HREF="#ToC-Disposing">ToC</A>]
<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
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>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>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 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:
<dd><code>lynx file://localhost/FULL/PATH/FILENAME</code>
<dd><code>lynx path/filename.html</code>
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. [<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
&lt;!--X-URL: --&gt;<BR>
&lt;BASE href=""&gt;
at the start of the file so that relative URLs in the document
will still work.
Even this modification can be prevented by setting
<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-RemoteSource">ToC</A>]
<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
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>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>).
[<A HREF="#ToC-ReDo">ToC</A>]
<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="#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
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>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
<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>
<em>&lt;ISINDEX PROMPT="Enter WAIS query:"
for submitting a search of the Biologist's Addresses database directly
to the WAIS server. [<A HREF="#ToC-Search">ToC</A>]
<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. It allows you to change options at runtime, if you need to.
Most changes are read from &amp; saved to your .lynxrc file; those which are not
are marked (!) in the form-based menu (as below). Many other options
are stored in the <A HREF="#lynx.cfg">lynx.cfg</A> file.
<p>Lynx supports two styles of Options Menu, key-based &amp; 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.
Options Menu (Lynx Version 2.8.6rel.2)
Accept Changes - Reset Changes Left Arrow cancels changes <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]
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)]
Show images (!) : [as labels]
Verbose images : [OFF..........]
Headers Transferred to Remote Servers
Personal mail address : __________________________________________
Password for anonymous ftp : __________________________________________
Preferred media type (!) : [Accept lynx's internal types]
Preferred encoding (!) : [All_____]
Preferred document character set : _________________________________
Preferred document language : _________________________________
User-Agent header (!) : __________________________________________
Listing and Accessing Files
FTP sort criteria : [By Name]
Local directory sort criteria : [Mixed style......]
Local directory sort order : [By name..........]
Show transfer rate : [Show KiB/sec, ETA]
Show dot files : [ON.]
Execution links : [FOR LOCAL FILES ONLY]
Special Files and Screens
Multi-bookmarks : [ADVANCED]
Review/edit Bookmarks files : Goto multi-bookmark menu
Visited Pages : [As Visit Tree..........]
Check your lynx.cfg here
Accept Changes - Reset Changes Left Arrow cancels changes
<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>.
Options Menu (Lynx Version 2.8.6rel.2)
(E)ditor : emacs
(D)ISPLAY variable :
mu(L)ti-bookmarks: OFF B)ookmark file: lynx_bookmarks.html
(F)TP sort criteria : By Filename
(P)ersonal mail address :
(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 (&amp;) : 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
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
<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
<p>When you are done changing options use the '<em>r</em>' command to
return to Lynx or the '<em>&gt;</em>' command to save the options to a
<em>.lynxrc</em> file and return to Lynx.
<p>The following table describes the options available on the
<em>Options Menu</em>:
<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>Bookmark file
<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. 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. 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. 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>
For Win32, see [???].
<dt>DISPLAY variable
<dd>This option is only relevant to X Window users. The DISPLAY
(Unix) or DECW$DISPLAY (VMS) variable is picked up automatically
from the environment if it has been previously set.
<dt>Display Character set
<dd>This option allows you to set up the default character set for
your specific terminal. The display character set provides a
mapping from the character encodings of viewed documents and
from HTML entities into viewable characters. It should be set
according to your terminal's character set so that characters
other than 7-bit ASCII can be displayed correctly, using
approximations if necessary. You must have the selected
character set installed on your terminal. (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>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.
<dt>Emacs keys
<dd>If set to ON then the CTRL-P, CTRL-N, CTRL-F, and CTRL-B keys
will be mapped to up-arrow, down-arrow, right-arrow, and
left-arrow, respectively. Otherwise, they remain mapped to
their configured bindings (normally UP_TWO lines, DOWN_TWO
lines, NEXT_PAGE, and PREV_PAGE, respectively).
<p>Note: this has no direct effect on the line-editor's key bindings.
<dt>FTP sort criteria
<dd>This option allows you to specify how files will be sorted
within FTP listings. The current options include
"<code>By Filename</code>", "<code>By Size</code>",
"<code>By Type</code>", and "<code>By Date</code>".
<dt>Keypad as arrows, numbered links, numbered fields, or numbered links and form fields
<dd>This option gives the choice among navigating with the arrow
keys, or having every link numbered so that the links may be
selected or made current by numbers as well as using the arrow
keys, or having every link as well as every form field numbered
so that they can be selected or sought by numbers. See the<br>
&nbsp;&nbsp;<a href="keystrokes/follow_help.html"
>Follow link (or page) number:</a> and<br>
>Select option (or page) number:</a><br>
help for more information.
<dt>Line edit style
<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>.
<dt>List directory style
<dd>Applies to Directory Editing. Files and directories can be
presented in the following ways:
<dt>Mixed style
<dd>Files and directories are listed together in alphabetical
<dt>Directories first
<dd>Files and directories are separated into two alphabetical
lists. Directories are listed first.
<dt>Files first
<dd>Files and directories are separated into two alphabetical
lists. Files are listed first.
The Options Form also allows you to sort by the file attributes,
using the <em>Local directory sort order</em>:
<dt>By name
<dd>by filename (the default)
<dt>By size
<dd>by file size, in descending order
<dt>By date
<dd>by file modification time, in descending order
<dt>By mode
<dd>by file protection
<dt>By type
<dd>by filename suffix, e.g., the text beginning with '.'
<dt>By user
<dd>by file owner's user-id
<dt>By group
<dd>by file owner's group-id
<dt>Local execution scripts or links
<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>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:
<dt> Always off
<dd>Local execution scripts will never be executed
<dt>For Local files only
<dd>Local execution scripts will only be executed if the
script to be executed resides on the local machine,
and is referenced by a URL that begins with
<dt>Always on
<dd>All local execution scripts will be executed
<dd>If the users options permit the script to be executed Lynx will
spawn a shell and run the script. If the script cannot be
executed Lynx will show the script within the Lynx window and
inform the user that the script is not allowed to be executed
and will ask the user to check his/her options.
[<A HREF="#ToC-InteractiveOptions">ToC</A>]
<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.
<dt>Password for anonymous ftp
<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.
<dt>Personal mail address
<dd>This mail address will be used to help you send files to
yourself and will be included as the From: address in any mail
or comments that you send. It will also be sent as the From:
field in HTTP or HTTPS requests if inclusion of that header
has been enabled via the NO_FROM_HEADER definition in
<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.
<dt>Popups for select fields
<dd>Lynx normally uses a popup window for the OPTIONs in form
SELECT fields when the field does not have the MULTIPLE
attribute specified, and thus only one OPTION can be selected.
The use of popup windows can be disabled by changing this setting
to OFF, in which case the OPTIONs will be rendered as a list of
radio buttons. Note that if the SELECT field does have the
MULTIPLE attribute specified, the OPTIONs always are rendered
as a list of checkboxes.
<dt>Preferred Document Language
<dd>The language you prefer if multi-language files are available
from servers. Use RFC 1766 abbreviations, e.g., en for English,
fr for French, etc. Can be a comma-separated list, which may
be interpreted by servers as descending order of preferences.
You can also make your order of preference explicit by using
q factors as defined by the HTTP protocol, for servers which
understand it, for example:
<dt>Preferred Document Charset
<dd>The character set you prefer if sets in addition to ISO-8859-1
and US-ASCII are available from servers. Use MIME notation
(e.g., ISO-8859-2) and do not include ISO-8859-1 or US-ASCII,
since those values are always assumed by default. Can be a
comma-separated list, which may be interpreted by servers as
descending order of preferences. You can also make your order
of preference explicit by using q factors as defined by the
HTTP protocol, for servers which understand it, for example:
<dt>Preferred Encoding
<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.
<dt>Preferred Media Type
<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.
<dt>Accept lynx's internal types
<dd>list only the types that are compiled into lynx.
<dt>Also accept lynx.cfg's types
<dd>lists types defined in lynx.cfg, e.g., the VIEWER and
Cern RULE or RULESFILE settings.
<dt>Also accept user's types
<dd>lists types from the PERSONAL_EXTENSION_MAP setting in
<dt>Also accept system's types
<dd>lists types from the GLOBAL_EXTENSION_MAP setting in
<dt>Accept all types
<dd>adds the types that are in lynx's built-in tables for
external programs that may be used to present a
<dt>Raw 8-bit or CJK Mode
<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.
<dt>Show color.
<dd>This option will be present if color support is available.
If set to ON or ALWAYS, color mode will be forced on if possible.
If (n)curses color support is available but cannot be used for
the current terminal type, selecting ON is rejected with a message.
If set to OFF or NEVER, color mode will be turned off.<BR>
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>
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.
<dt>Searching type
<dd>Searching type has two possible values: CASE INSENSITIVE
(default) and CASE SENSITIVE. The searching type effects
inter-document searches only, and determines whether searches
for words within documents will be done in a case-sensitive or
case-insensitive manner.
<dt>Show cursor for current link or option.
<dd>Lynx normally hides the cursor by positioning it to the right
and if possible the very bottom of the screen, so that the
current link or OPTION is indicated solely by its highlighting
or color. If show cursor is set to ON, the cursor will be
positioned at the left of the current link or OPTION. This
is helpful when Lynx is being used with a speech or braille
interface. It also is useful for sighted users when the
terminal cannot distinguish the character attributes used
to distinguish the current link or OPTION from the others in
the screen display.
<dt>Show dot files
<dd>If display/creation of hidden (dot) files/directories is
enabled, you can turn the feature on or off via this setting.
<dt>Use locale-based character set
<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.
<dt>Underline links
<dd>Use underline-attribute rather than bold for links.
<dt>User Agent
<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.6</em>
for access to sites which discriminate against Lynx based on
checks for the presence of &quot;Lynx&quot; 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><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 &quot;Lynx&quot;
or &quot;L_y_n_x&quot;.
<dt>User Mode
<dd>There are three possible choices: Novice, Intermediate, and
<dd>In Novice mode two lines of help are displayed at the
bottom of the screen.
<dd>Intermediate mode turns off the help lines.
<dd>Advanced mode displays the URL of the currently selected
link at the bottom of the screen.
<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>VI keys
<dd>If set to ON then the lowercase h, j, k, and l keys will be
mapped to left, down, up, and right arrow, respectively. The
uppercase H, J, K, and L keys remain mapped to their configured
bindings (normally HELP, JUMP, KEYMAP, and LIST, respectively).
<p>Note: this has no effect on the line-editor's key bindings.
<dt>Visited Pages
<dd>Enable several different views of the visited links:
<dt>By First Visit
<dt>By First Visit Reversed
<dt>As Visit Tree
<dt>By Last Visit
<dt>By Last Visit Reversed
<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
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, <pre>
&lt;LINK REV="made" HREF=""&gt;
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">mailto:</a> links will also allow
you to send mail to other people. Using the mail features within Lynx is
<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>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.[<A HREF="#ToC-Mail">ToC</A>]
<h2 ID="News"><A NAME="News"><em>USENET News posting</em></A></h2>
While reading <a
>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>
<dt>Reply to user@host
<dd>user@host will correspond to the mail address of the
person who posted the news article. Selecting the link will
allow you to send a message to the person who wrote the message
you are currently viewing. You will be given the option of
including the original message in your reply.
<dt>Followup to newsgroup(s)
<dd>Selecting this link will allow you to post back to the
newsgroup that you are currently reading and any newsgroups
to which the message was cross-posted. You will be given
the option of including the original message in your reply.
Once you have typed in your message, you will be asked for
confirmation of whether to proceed with the posting, and
whether to append your signature file if one was defined in
<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>]
See also <a
href="">RFC 977</a>.
<h2 ID="Bookmarks"><A NAME="Bookmarks"><em>Lynx bookmarks</em></A></h2>
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>.
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:
Save D)ocument or L)ink to bookmark file or C)ancel? (d,l,c):
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>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>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>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 ID="Jumps"><A NAME="Jumps"><em>Jump Command</em></a></h2>
Similar to the bookmarks file is the jumps file: for an example,
look in the <em>samples</em> subdirectory in the distribution package.
To use the jumps command, create a <em>jumps file</em> with the same format
as the sample file, but containing your own URLs &amp; short-cut names.
Once you have done that, typing '<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>
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>
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>
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> .
[<A HREF="#ToC-Jumps">ToC</A>]
<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
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
<dd>Type '<em>c</em>' to create a new file. New file will be empty.
<dd>Type '<em>d</em>' to download using one of the pre-defined options.
<dd>Type '<em>e</em>' to spawn the editor defined in <em>Options Menu</em>
and load a selected file for editing.
<dt><code>F)ull Menu</code>
<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>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>Type '<em>r</em>' to remove the selected file or directory.
<dd>Type '<em>t</em>' to tag highlighted file. Further operations will be
performed on tagged files instead of highlighted ones.
<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> .
[<A HREF="#ToC-DirEd">ToC</A>]
<h2 ID="ColorMouse"><A NAME="ColorMouse"><em>Using Color &amp; the Mouse</em></A></h2>
A limited range of colors &amp; mouse commands are available, if the user chooses:
see <em>lynx.cfg</em> for details.
[<A HREF="#ToC-ColorMouse">ToC</A>]
<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
'<em>K</em>'. The following describes some of the most commonly used
<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><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><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><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
<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><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>The <em>)</em> command jumps you forward half a page in the
current document.
<dd>The <em>(</em> command jumps you back half a page in the
current document.
<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>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>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>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>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>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
<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>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.
<dt><A NAME="asterisk-key"><em>*</em></A>
<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>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.
<dt><A NAME="lbracket-key"><em>[</em></A>
<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>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><em>Control-K</em> invokes the <a
href="keystrokes/cookie_help.html">Cookie Jar Page</a>
if it contains cookies.
<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>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.
[<A HREF="#ToC-MiscKeys">ToC</A>]
<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
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>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.
<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).
<dt>Checkboxes and Radio buttons
<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.
<dt>Selection Fields
<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.
<dt> Text Entry Fields
<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">"Textfields Need Activation"</A> mode is turned on
(with the <kbd>-tna</kbd> command-line option or in <A HREF="#lynx.cfg"
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">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.
Some flavors of UNIX, shells &amp; terminal settings require
that you enter <em>^V^Ve</em> in order to start the external editor,
as they also use <em>^V</em> as default command-line quote key
(called `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>
&nbsp;&nbsp;stty lnext undef<br>
&nbsp;&nbsp;$HOME/bin/lynx "$@"<br>
&nbsp;&nbsp;stty lnext ^V<br>
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
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,
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
outside of text input fields.
<dt>TEXTAREA Fields
<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.
<dt>Editing TEXTAREA Fields and Special TEXTAREA Functions
<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>
(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>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
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>
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>
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,
(see lynx.cfg for other keystroke codes to use).
<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).
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"><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
<em>&lt;META HTTP-EQUIV="Pragma" CONTENT="no-cache"&gt;</em>
<em>&lt;META HTTP-EQUIV="Cache-Control" CONTENT="no-cache"&gt;</em>
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>Forms which have <em>POST</em> as the METHOD, or a <a
href="lynx_url_support.html#mailto">mailto:</a> URL as the ACTION, are always
resubmitted, even if the content has not changed, when you activate the
<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>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>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
<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>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="">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>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">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>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>&amp;</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;amp;</em> or
<em>&amp;#38;</em>), their being followed by form field NAMEs which might
correspond to SGML entities could lead to corruption of the intended URL.
<p>NOTE, in this regard, that Lynx converts ampersands to <em>&amp;amp;</em>
when creating bookmarks, and thus the bookmark links will not be vulnerable
to such corruptions. Also NOTE that Lynx allows you to save links in your
bookmark file for documents returned by forms with the <em>GET</em> METHOD,
and which thus have the content appended as a <em>?searchpart</em>, but not
if the METHOD was <em>POST</em>, because the content would be lost and the
link thus would be invalid.
<p>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=&quot;file&quot;</em> or <em>TYPE=&quot;range&quot;</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
<p>A <em>Content-Disposition:&nbsp;file;&nbsp;filename=name.suffix</em>
header can be used by CGI scripts to set the suggested filename offered
by Lynx for '<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:
<em>&lt;META HTTP-EQUIV="Content-Disposition"
[<A HREF="#ToC-Forms">ToC</A>]
<h2 ID="Images"><A NAME="Images"><em>Lynx and HTML Images</em></a></h2>
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.
There are 3 choices in <em>lynx.cfg</em>, with 2 corresponding keys:
VERBOSE_IMAGES no corresponding key
You can also use the <em>Options Menu</em>, as outlined below:
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.
In the Form-based Menu, the 3-way `Show images' selection
combines the effects of the `*' &amp; `[' keys, as follows:
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
<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.
<p>Lynx recognizes the TABLE element and all of its associated elements
as described in <a href="">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>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>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:
<li>All data constituting a table row generally has to fit within the
display width without inserting line breaks.
<li>Cell contents have to be simple. In general, only inline markup is
acceptable, no <code>&lt;P&gt;</code>, <code>&lt;BR&gt;</code> etc.
(although <code>&lt;BR&gt;</code> may
be ignored at the beginning of the first cell or at the end of the
last cell of a row).
<li>When tables are nested, only the innermost level is a candidate
for tabular representation.
<li>Most attributes are ignored, including borders, <code>WIDTH</code>,
vertical alignment.
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
<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"><code
>lynxcgi:</code></A> in <em>Supported URLs</em> for information on various
ways for setting this up).
[<A HREF="#ToC-Tables">ToC</A>]
<h2 ID="Tabs"><A NAME="Tabs"><em>Lynx and HTML Tabs</em></a></h2>
Lynx implements the <a
href="">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>Note that this <em>Users Guide</em> and the <a
href="lynx_url_support.html">Supported URLs</a> page include TAB markup in
a manner which <em>degrades gracefully</em> for WWW browsers which do not
support it. Toggle to display of <a href="#LocalSource">source</a> and <a
href="#Search">search</a> for <em>&lt;tab</em> to examine the use of TAB markup
in these documents. [<A HREF="#ToC-Tabs">ToC</A>]
<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,
independently scrolling windows. Such windows have been termed
<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.
[<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 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
links with brief, descriptive link names, analogous to a Windows toolbar.
Such windows have been termed <em>banners</em>.
<p>Lynx recognizes and processes all of the <a
href="">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
<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>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>Lynx also recognizes the <a
href="">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.
[<A HREF="#ToC-Banners">ToC</A>]
<h2 ID="Footnotes"><A NAME="Footnotes"><em>Lynx and HTML Footnotes</em></a></h2>
Lynx implements the <a
href="">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:
See the <em>&lt;A HREF="#fn1"&gt;</em><a href="#an1">footnote</a><em>&lt;/A&gt;</em>.
activating that link will take you to the labeled rendering of:
<em>&lt;FN ID="fn1"&gt;</em>&lt;p&gt;<a name="an1">Lynx does not use popups for FN blocks.</a>&lt;/p&gt;<em>&lt;/FN&gt;</em>
<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.
[<A HREF="#ToC-Footnotes">ToC</A>]
<h2 ID="Notes"><A NAME="Notes"><em>Lynx and HTML Notes</em></a></h2>
Lynx implements the <a
href="">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>
<em>&lt;NOTE CLASS="warning" ID="too-bad"&gt;
&lt;p&gt;The W3C vendors did not retain NOTE in the HTML 3.2 draft.&lt;/p&gt;
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-Notes">ToC</A>]
<h2 ID="Lists"><A NAME="Lists"><em>Lynx and HTML Lists</em></a></h2>
Lynx implements the <a
href="">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
>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="">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>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>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>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>Lynx treats UL, OL, DIR, and MENU blocks as having the COMPACT attribute
by default, i.e., single spaces between LH and LI elements within those
blocks. For DL blocks, double spacing will be used to separate the DT and
DD elements unless the COMPACT attribute has been specified.
[<A HREF="#ToC-Lists">ToC</A>]
<h2 ID="Quotes"><A NAME="Quotes"><em>Lynx and HTML Quotes</em></a></h2>
The <a
href="">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>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>Lynx respects nested Q start and end tags, and will use ASCII double-quotes
(<em>&quot;</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 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 ID="Eightbit"><A NAME="Eightbit"><em>Lynx and HTML Internationalization: 8bit, UNICODE, etc.</em></a></h2>
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>
[<A HREF="#ToC-Eightbit">ToC</A>]
<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
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>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
<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>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>Lynx also recognizes the <a
href="">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>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>.
<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>,
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:
<em>&lt;META HTTP-EQUIV="Refresh" CONTENT="3; URL=http://host/path"&gt;</em>
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.
[<A HREF="#ToC-Refresh">ToC</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="#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>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
<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>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>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>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>.
[<A HREF="#ToC-Cookies">ToC</A>]
<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
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:
<dd><code>lynx [options]</code>
<dd><code>lynx [options] startfile</code>
<dd>is the file or URL that Lynx will load at start-up.
<li>If startfile is not specified, Lynx will use a default
starting file and base directory determined during
<li>If a specified file is local (i.e., not a URL) Lynx
displays that file and uses the directory in which that
file resides as the base directory.
<li>If a URL is specified, the file will be retrieved,
and only the server base directory will be relevant
to further accesses.
<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.
<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).
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.,
Lynx recognizes "1", "+", "on" and "true" for true values, and "0",
"-", "off" and "false" for false values. Other option-values are
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.
Capitalized items in the option summary
indicate that a substitution must be made.
These are the options:
<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 (&quot;-&quot;) 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>accept all cookies.
<dd>apply restrictions appropriate for an anonymous
account, see <em>-restrictions</em> below for some
<dd>charset for documents that don't specify it.
<dd>charset assumed for local files,
i.e., files which lynx creates such as internal pages for
the options menu.
<dd>use this instead of unrecognized charsets.
<dd>set authorization ID and password for protected documents
at startup. Be sure to protect any script files which use
this switch.
<dd>prepend a request URL comment and BASE tag to text/html
outputs for -source dumps.
<dd>specify a local bibp server (default http://bibhost/).
<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>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>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>set the <em>NUMBER</em> of documents cached in memory.
The default is 10.
<dd>Toggle center alignment in HTML TABLE.
<dd>enable case-sensitive string searching.
<dd>specifies a Lynx configuration file other than the default
<A HREF="#lynx.cfg">lynx.cfg</A>.
<dd>exit on left-arrow in startfile, and disable save to disk.
<dd>write keystroke commands and related information to the
specified file.
<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:
<dd>causes the script to stop, and forces lynx to
exit immediately.
<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>followed by a "name=value" allows one to override
values set in the lynx.cfg file.
<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>Sets the connection timeout, where N is given in seconds.
<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>specifies a file to use to store cookies.
If none is specified, the value given by
<code>-cookie_file</code> is used.
<dd>toggles handling of Set-Cookie headers.
<dd>toggles forced core dumps on fatal errors. (Unix only)
<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>toggles the use of curses "pad" feature which supports
left/right scrolling of the display.
<dd>separate incremental display stages with MessageSecs delay
<dd>set the display variable for X rexe-ced programs.
<dd>set the charset for the terminal output.
<dd>inhibit wrapping of text in &lt;pre&gt; when -dump'ing and
-crawl'ing, mark wrapped lines in interactive session.
<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</em>
<dd>enable external editing using the specified
<em>EDITOR</em>. (vi, ed, emacs, etc.)
<dd>enable emacs-like key movement.
<dd>toggles behavior compatible with the scrollback keys in
some communications software (may be incompatible with
some curses packages).
<dd>the status code from the HTTP request is placed in this
<dd>enable local program execution (normally not configured).
<dd>include all versions of files in local VMS directory
<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>force HREF-less 'A' elements to be empty (close them as soon as they are seen).
<dd>forces the first document to be interpreted as HTML.
<dd>toggles forcing of the secure flag for SSL cookies.
<dd>toggles whether the Options Menu is key-based or form-based.
<dd>toggles transmissions of From headers to HTTP or HTTPS
<dd>disable ftp access.
<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>send a HEAD request for the mime headers.
<dd>print this Lynx command syntax usage message.
<dd>control the display of hidden links. Option values are:
<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>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>hidden links do not appear even in listings.
<dd>toggles use of '&gt;' or '--&gt;' as a terminator for
<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>toggles inclusion of links for all images.
<dd>toggles inclusion of ISMAP links when client-side
MAPs are present.
<dd>set the default index file to the specified <em>URL</em>
<dd>do justification of text.
<dd>starting count for lnk#.dat files produced by
<dd>disable URLs that point to remote hosts.
<dd>enable local program execution from local files only
(if lynx was compiled with local execution enabled).
<dd>specify filename containing color-style information.
The default is lynx.lss.
<dd>include mime headers and force source dump.
<dd>toggles minimal versus valid comment parsing. When
minimal, any '--&gt;' 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>toggles nested-tables logic (for debugging).
<dd>number of articles in chunked news listings.
<dd>maximum news articles in listings before chunking.
<dd>disable bold video-attribute.
<dd>disable directory browsing.
<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>force color mode off, overriding terminal capabilities and any
<em>-color</em> flags, <em>COLORTERM</em> variable, and saved .lynxrc settings.
<dd>disable local program execution. (DEFAULT)
<dd>disable transmissions of Referer headers for file URLs.
<dd>disable the link list feature in dumps.
<dd>disable mailing of error messages to document owners.
<dd>disable left/right margins in the default style sheet.
<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
<dd>disable forced pauses for statusline messages.
<dd>disable most print functions.
<dd>don't follow URL redirections
<dd>disable transmissions of Referer headers.
<dd>disable reverse video-attribute.
<dd>disable SOCKS proxy usage by a SOCKSified Lynx.
<dd>disable the retrieval status messages.
<dd>disable title and blank line from top of page.
<dd>disable underline video-attribute.
<dd>force numbering of links as well as form input fields.
<dd>force numbering of links.
<dd>toggles displaying of partial pages while loading.
<dd>number of lines to render before repainting display
with partial-display logic.
<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>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>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>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>do syntax highlighting and hyperlink handling in source
<dd>enable print functions. (default)
<dd>toggles pseudo-ALTs for inline images with no ALT string.
<dd>toggles default setting of 8-bit character translations
or CJK mode for the startup character set.
<dd>restricts access to URLs in the starting realm.
<dd>flushes the cache on a proxy server
(only the first document affected).
<dd>allows a list of services to be disabled
selectively and takes the following form:
<dd><em>lynx -restrictions=[option][,option][,option]...</em>
<dd>The list of recognized options is printed if none
are specified.
<dd>if used alone, lists restrictions in effect.
<dd>restricts all options listed below.
<dd>disallow changing the location of the bookmark
<dd>disallow execution links via the bookmark file.
<dd>disallow changing the eXecute permission on
files (but still allow it for directories) when
local file management is enabled.
<dd>disallow command which changes Lynx's working
<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
<dd>disallow local file management.
<dd>disallow saving to disk in the download and print
<dd>disallow access to, or creation of, hidden (dot)
<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>disallow external editing.
<dd>disable execution scripts.
<dd>disallow the user from changing the local
execution option.
<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>disallow using G)oto, served links or bookmarks
for file: URLs.
<dd>disable the '<em>g</em>' (goto) command.
<dd>disallow ftps for people coming from inside your
<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>disallow rlogins for people coming from inside
your domain.
<dd>disallow telnets for people coming from inside
your domain.
<dd>disable the '<em>j</em>' (jump) command.
<dd>disallow execution of Lynx CGI URLs.
<dd>disallow mailing feature.
<dd>disallow multiple bookmarks.
<dd>disallow USENET News posting,
<dd>disallow saving options in .lynxrc.
<dd>disallow ftps for people coming from outside your
<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>disallow rlogins for people coming from outside
your domain.
<dd>disallow telnets for people coming from
outside your domain.
<dd>disallow most print options.
<dd>disallow shell escapes.
<dd>disallow <em>Control-Z</em> suspends with escape
to shell on Unix.
<dd>disallow specifying a port in telnet G)oto's.
<dd>disallow modifications of the User-Agent header.
<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>disable recognition of rlogin commands.
<dd>toggles showing scrollbar.
<dd>toggles showing arrows at ends of the scrollbar.
<dd>require .www_browsable files to browse directories.
<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.
<dt><code>-show_cursor </code>
<dd>If enabled the cursor will not be hidden in the right hand
corner but will instead be positioned at the start of the
currently selected link. Show cursor is the default for
systems without FANCY_CURSES capabilities. The default
configuration can be changed in userdefs.h or
<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>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>toggles emulation of the old Netscape and Mosaic bug which
treated '<em>&gt;</em>' as a co-terminator for
double-quotes and tags.
<dd>works the same as dump but outputs HTML source instead of
formatted text. For example
lynx -source . >foo.html
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:
lynx -source ./ >foo.html
<dd>disable SIGINT cleanup handler.
<dd>allow non-http startfile and homepage with
<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>read the startfile from standard input
(UNIX only).
<dd>information for syslog call.
<dd>log requested URLs with syslog.
<dd>initialize DTD with "TagSoup" tables,
<A HREF="keystrokes/option_help.html#tagsoup">more details</A>.
<dd>disable recognition of telnet commands.
<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>For win32, sets the network read-timeout, where N is given in seconds.
<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>turns on <A HREF="#tna">"Textfields Need Activation"</A>
<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>turn on optional traces, which may result in very large trace files.
Logically OR the values to combine options:
<dd>SGML character parsing states
<dd>TRST (table layout)
<dd>config (lynx.cfg and .lynxrc contents)
<dd>binary string copy/append, used in form data construction.
<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>trim input text/textarea fields in forms.
<dd>toggles use of _underline_ format in dumps.
<dd>turn on mouse support, if available.
<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>accept only http URLs (meant for validation).
<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>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>toggles [LINK], [IMAGE] and [INLINE] comments
with filenames of these images.
<dd>print version information.
<dd>enable vi-like key movement.
<dd>enable Waterloo tcp/ip packet debug (print to watt
debugfile). This applies only to DOS versions compiled
with WATTCP or WATT-32.
<dd>number of columns for formatting of dumps, default is 80.
<dd>emit backspaces in output if -dumping or -crawling (like
<code>man</code> does).
<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.
[<A HREF="#ToC-Invoking">ToC</A>]
<h2 ID="Environments"><A NAME="Environment"><em>Environment variables used by Lynx</em></A></h2>
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.
[<A HREF="#ToC-Environment">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.
You may visit an index of options:
<a href="">by category</a> or
<a href="">by alphabet</a>.
<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>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 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
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>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
<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>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
<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><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>
<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>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>Contributors have generally been acknowledged in the CHANGES
file. Earlier CHANGES file can be found in the docs/ subdirectory
of this distribution.
<p>Information on obtaining the most current version of Lynx is available
at <a href="">the current distribution page</a>.
<p>[<A HREF="#TOC">ToC</A>]