Description of settings in lynx configuration file

Options are in the same order as lynx.cfg.

`INCLUDE` - Auxiliary Facilities

Description

Starting with Lynx 2.8.1, the lynx.cfg file has a crude "include" facility. This means that you can take advantage of the global lynx.cfg while also supplying your own tweaks.

You can use a command-line argument (-cfg /where/is/lynx.cfg) or an environment variable (LYNX_CFG=/where/is/lynx.cfg). For instance, put in your .profile or .login:

LYNX_CFG=~/lynx.cfg; export LYNX_CFG # in .profile for sh/ksh/bash/etc. setenv LYNX_CFG ~/lynx.cfg # in .login for [t]csh

Then in ~/lynx.cfg:

INCLUDE:/usr/local/lib/lynx.cfg
^^^^^^^^^^^^^^^^^^^^^^^ or whatever is appropriate on your system
and now your own tweaks.

Starting with Lynx 2.8.2, the INCLUDE facility is yet more powerful. You can suppress all but specific settings that will be read from included files. This allows sysadmins to provide users the ability to customize lynx with options that normally do not affect security, such as COLOR, VIEWER, KEYMAP.

The syntax is

INCLUDE:filename for <space-separated-list-of-allowed-settings>

sample:

Example:

INCLUDE:~/lynx.cfg for COLOR VIEWER KEYMAP

only one space character should surround the word 'for'. On Unix systems ":" is also accepted as separator. In that case, the example can be written as

Example:

INCLUDE:~/lynx.cfg:COLOR VIEWER KEYMAP

In the example, only the settings COLOR, VIEWER and KEYMAP are accepted by lynx. Other settings are ignored. Note: INCLUDE is also treated as a setting, so to allow an included file to include other files, put INCLUDE in the list of allowed settings.

If you allow an included file to include other files, and if a list of allowed settings is specified for that file with the INCLUDE command, nested files are only allowed to include the list of settings that is the set AND of settings allowed for the included file and settings allowed by nested INCLUDE commands. In short, there is no security hole introduced by including a user-defined configuration file if the original list of allowed settings is secure.

`STARTFILE` - Auxiliary Facilities

Description

STARTFILE is the default starting URL if none is specified
on the command line or via a WWW_HOME environment variable; Lynx will refuse to start without a starting URL of some kind.
STARTFILE can be remote, e.g. http://www.w3.org/default.html ,
or local, e.g. file://localhost/PATH_TO/FILENAME ,
where PATH_TO is replaced with the complete path to FILENAME using Unix shell syntax and including the device on VMS.

Normally we expect you will connect to a remote site, e.g., the Lynx starting site:

Default value

STARTFILE:http://lynx.isc.org/

As an alternative, you may want to use a local URL. A good choice for this is the user's home directory:

Example:

STARTFILE:file://localhost/~/

Your choice of STARTFILE should reflect your site's needs, and be a URL that you can connect to reliably. Otherwise users will become confused and think that they cannot run Lynx.

Default value

STARTFILE:file://localhost/usr/share/xubuntu-docs/about/xubuntu-index.html

`HELPFILE` - Auxiliary Facilities

Description

HELPFILE must be defined as a URL and must have a complete path if local: file://localhost/PATH_TO/lynx_help/lynx_help_main.html
Replace PATH_TO with the path to the lynx_help subdirectory for this distribution (use SHELL syntax including the device on VMS systems).
The default HELPFILE is: http://lynx.isc.org/release/lynx2-8-6/lynx_help/lynx_help_main.html
This should be changed to the local path.
This definition will be overridden if the "LYNX_HELPFILE" environment variable has been set.

Default value

`JUMPFILE` - Auxiliary Facilities

Description

JUMPFILE is the local file checked for short-cut names for URLs when the user presses the "j" (JUMP) key. The user will be prompted to enter a short-cut name for an URL, which Lynx will then follow in a similar manner to "g"oto; alternatively, s/he can enter "?" to view the full JUMPFILE list of short-cuts with associated URLs. There is an example jumps file in the samples subdirectory. If not defined here or in userdefs.h, the JUMP command will invoke the NO_JUMPFILE statusline message (see LYMessages_en.h ).

To allow "?" to work, include in the JUMPFILE a short-cut to the JUMPFILE itself, e.g. <dt>?<dd><a href="file://localhost/path/jumps.html">This Shortcut List</a>

On VMS, use Unix SHELL syntax (including a lead slash) to define it.

Alternate jumps files can be defined and mapped to keys here. If the keys have already been mapped, then those mappings will be replaced, but you should leave at least one key mapped to the default jumps file. You optionally may include a statusline prompt string for the mapping. You must map upper and lowercase keys separately (beware of mappings to keys which the user can further remap via the "o"ptions menu). The format is:

JUMPFILE:path:key[:prompt]

where path should begin with a "/" (i.e., not include file://localhost). Any white space following a prompt string will be trimmed, and a single space will be added by Lynx.

In the following line, include the actual full local path to JUMPFILE, but do not include 'file://localhost' in the line.

Default value

`SESSION_FILE` - Session support

Description

SESSION_FILE defines the file name where lynx will store user sessions. This setting is used only when AUTO_SESSION is true. Note: the default setting will store/resume each session in a different folder under same file name (if that is allowed by operating system) when lynx is invoked from different directories. (The current working directory may be changed inside lynx)

If you do not want this feature, leave the setting commented. Users can still customize SESSION_FILE and AUTO_SESSION via their .lynxrc file.

Default value

SESSION_FILE:lynx_session
SESSION_FILE:/home/moi/.lynx/session

`SESSION_LIMIT` - Session support

Description

SESSION_LIMIT defines maximum number of: searched strings, goto URLs, visited links and history entries which will be saved in session file. The minimum allowed is 1, the maximum is 10000.

For instance, if SESSION_LIMIT is 250, a per-session limit of 250 entries of searched strings, goto URLs, visited links and history entries will be saved in the session file.

There is no fixed limit on the number of entries which can be restored; It is limited only by available memory.

Default value

SESSION_LIMIT:250
SESSION_LIMIT:255

`CHARACTER_SET` - Character sets

Description

CHARACTER_SET defines the display character set, i.e., assumed to be installed on the user's terminal. It determines which characters or strings will be used to represent 8-bit character entities within HTML. New character sets may be defined as explained in the README files of the src/chrtrans directory in the Lynx source code distribution. For Asian (CJK) character sets, it also determines how Kanji code will be handled. The default is defined in userdefs.h and can be changed here or via the "o"ptions menu. The "o"ptions menu setting will be stored in the user's RC file whenever those settings are saved, and thereafter will be used as the default. For Lynx a "character set" has two names: a MIME name (for recognizing properly labeled charset parameters in HTTP headers etc.), and a human-readable string for the "O"ptions Menu (so you may find info about language or group of languages besides MIME name). Not all 'human-readable' names correspond to exactly one valid MIME charset (example is "Chinese"); in that case an appropriate valid (and more specific) MIME name should be used where required. Well-known synonyms are also processed in the code.

Raw (CJK) mode

Lynx normally translates characters from a document's charset to display charset, using ASSUME_CHARSET value (see below) if the document's charset is not specified explicitly. Raw (CJK) mode is OFF for this case. When the document charset is specified explicitly, that charset overrides any assumption like ASSUME_CHARSET or raw (CJK) mode.

For the Asian (CJK) display character sets, the corresponding charset is assumed in documents, i.e., raw (CJK) mode is ON by default. In raw CJK mode, 8-bit characters are not reverse translated in relation to the entity conversion arrays, i.e., they are assumed to be appropriate for the display character set. The mode should be toggled OFF when an Asian (CJK) display character set is selected but the document is not CJK and its charset not specified explicitly.

Raw (CJK) mode may be toggled by user via "@" (LYK_RAW_TOGGLE) key, the -raw command line switch or from the "o"ptions menu.

Raw (CJK) mode effectively changes the charset assumption about unlabeled documents. You can toggle raw mode ON if you believe the document has a charset which does correspond to your Display Character Set. On the other hand, if you set ASSUME_CHARSET the same as Display Character Set you get raw mode ON by default (but you get assume_charset=iso-8859-1 if you try raw mode OFF after it).

Note that "raw" does not mean that every byte will be passed to the screen. HTML character entities may get expanded and translated, inappropriate control characters filtered out, etc. There is a "Transparent" pseudo character set for more "rawness".

Since Lynx now supports a wide range of platforms it may be useful to note the cpXXX codepages used by IBM PC compatible computers, and windows-xxxx used by native MS-Windows apps. We also note that cpXXX pages rarely are found on Internet, but are mostly for local needs on DOS.

Recognized character sets include:


    string for "O"ptions Menu          MIME name
    7 bit approximations (US-ASCII)    us-ascii
    Western (ISO-8859-1)               iso-8859-1
    Western (ISO-8859-15)              iso-8859-15
    Western (cp850)                    cp850
    Western (windows-1252)             windows-1252
    IBM PC US codepage (cp437)         cp437
    DEC Multinational                  dec-mcs
    Macintosh (8 bit)                  macintosh
    NeXT character set                 next
    HP Roman8                          hp-roman8
    Chinese                            euc-cn
    Japanese (EUC-JP)                  euc-jp
    Japanese (Shift_JIS)               shift_jis
    Korean                             euc-kr
    Taipei (Big5)                      big5
    Vietnamese (VISCII)                viscii
    Eastern European (ISO-8859-2)      iso-8859-2
    Eastern European (cp852)           cp852
    Eastern European (windows-1250)    windows-1250
    Latin 3 (ISO-8859-3)               iso-8859-3
    Latin 4 (ISO-8859-4)               iso-8859-4
    Baltic Rim (ISO-8859-13)            iso-8859-13
    Baltic Rim (cp775)                 cp775
    Baltic Rim (windows-1257)          windows-1257
    Celtic (ISO-8859-14)                iso-8859-14
    Cyrillic (ISO-8859-5)              iso-8859-5
    Cyrillic (cp866)                   cp866
    Cyrillic (windows-1251)            windows-1251
    Cyrillic (KOI8-R)                  koi8-r
    Arabic (ISO-8859-6)                iso-8859-6
    Arabic (cp864)                     cp864
    Arabic (windows-1256)              windows-1256
    Greek (ISO-8859-7)                 iso-8859-7
    Greek (cp737)                      cp737
    Greek2 (cp869)                     cp869
    Greek (windows-1253)               windows-1253
    Hebrew (ISO-8859-8)                iso-8859-8
    Hebrew (cp862)                     cp862
    Hebrew (windows-1255)              windows-1255
    Turkish (ISO-8859-9)               iso-8859-9
    North European (ISO-8859-10)        iso-8859-10
    Ukrainian Cyrillic (cp866u)        cp866u
    Ukrainian Cyrillic (KOI8-U)        koi8-u
    UNICODE (UTF-8)                    utf-8
    RFC 1345 w/o Intro                 mnemonic+ascii+0
    RFC 1345 Mnemonic                  mnemonic
    Transparent                        x-transparent

The value should be the MIME name of a character set recognized by Lynx (case insensitive). Find RFC 1345 at http://www.ics.uci.edu/pub/ietf/uri/rfc1345.txt .

Default value

CHARACTER_SET:iso-8859-1
CHARACTER_SET:utf-8

`LOCALE_CHARSET` - Character sets

Description

LOCALE_CHARSET overrides CHARACTER_SET if true, using the current locale to lookup a MIME name that corresponds, and use that as the display charset.

Note that while nl_langinfo(CODESET) itself is standardized, the return values and their relationship to the locale value is not. GNU libiconv happens to give useful values, but other implementations are not guaranteed to do this.

Default value

LOCALE_CHARSET:FALSE

`ASSUME_CHARSET` - Character sets

Description

ASSUME_CHARSET 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). When ASSUME_CHARSET is defined here or by an -assume_charset command line flag is in effect, Lynx will treat documents as if they were encoded accordingly. See above on how this interacts with "raw mode" and the Display Character Set. ASSUME_CHARSET can also be changed via the "o"ptions menu but will not be saved as permanent value in user's .lynxrc file to avoid more chaos.

Default value

ASSUME_CHARSET:iso-8859-1

`ASSUMED_DOC_CHARSET_CHOICE` - Character sets

Description

It is possible to reduce the number of charset choices in the "O"ptions menu for "display charset" and "assumed document charset" fields via DISPLAY_CHARSET_CHOICE and ASSUMED_DOC_CHARSET_CHOICE settings correspondingly. Each of these settings can be used several times to define the set of possible choices for corresponding field. The syntax for the values is

string | prefix* | *

where

'string' is either the MIME name of charset or it's full name (listed
either in the left or in the right column of table of recognized charsets), case-insensitive - e.g. 'Koi8-R' or 'Cyrillic (KOI8-R)' (both without quotes),

'prefix' is any string, and such value will select all charsets having
the name with prefix matching given (case insensitive), i.e., for the charsets listed in the table of recognized charsets,

Example:

ASSUMED_DOC_CHARSET_CHOICE:cyrillic*

will be equal to specifying

Examples:

ASSUMED_DOC_CHARSET_CHOICE:cp866

ASSUMED_DOC_CHARSET_CHOICE:windows-1251

ASSUMED_DOC_CHARSET_CHOICE:koi8-r

ASSUMED_DOC_CHARSET_CHOICE:iso-8859-5

or lines with full names of charsets.

literal string "*" (without quotes) will enable all charset choices
in corresponding field. This is useful for overriding site defaults in private pieces of lynx.cfg included via INCLUDE directive.

Default values for both settings are "*", but any occurrence of settings with values that denote any charsets will make only listed choices available for corresponding field.

Default value

ASSUMED_DOC_CHARSET_CHOICE:*
DISPLAY_CHARSET_CHOICE:*

`DISPLAY_CHARSET_CHOICE` - Character sets

Lynx expects the glyphs for the charset CHARSET with character cell size HHHxWWW to be stored in a file HHHxWWW/CHARSET.fnt inside the directory specified by CHARSETS_DIRECTORY. E.g., the font for koi8-r sized 14x9 should be in the file 14x9/koi8-r.fnt.

Default value

CHARSETS_DIRECTORY:none

`CHARSET_SWITCH_RULES` - Character sets

Description

CHARSET_SWITCH_RULES hints lynx on how to choose the best display font given the document encoding. This string is a sequence of chunks, each chunk having the following form:

IN_CHARSET1 IN_CHARSET2 ... IN_CHARSET5 :OUT_CHARSET

For readability, one may insert arbitrary additional punctuation (anything but : is ignored). E.g., if lynx is able to switch only to display charsets cp866, cp850, cp852, and cp862, then the following setting may be useful (split for readability):

CHARSET_SWITCH_RULES: koi8-r ISO-8859-5 windows-1251 cp866u KOI8-U :cp866,
iso-8859-1 windows-1252 ISO-8859-15 :cp850, ISO-8859-2 windows-1250 :cp852, ISO-8859-8 windows-1255 :cp862

Default value

CHARSET_SWITCH_RULES:none

`URL_DOMAIN_PREFIXES` - Interaction

Description

URL_DOMAIN_PREFIXES and URL_DOMAIN_SUFFIXES are strings which will be prepended (together with a scheme://) and appended to the first element of command line or "g"oto arguments which are not complete URLs and cannot be opened as a local file (file://localhost/string). Both can be comma-separated lists. Each prefix must end with a dot, each suffix must begin with a dot, and either may contain other dots (e.g., .com.jp). The default lists are defined in userdefs.h and can be replaced here. Each prefix will be used with each suffix, in order, until a valid Internet host is created, based on a successful DNS lookup (e.g., foo will be tested as www.foo.com and then www.foo.edu etc.). The first element can include a :port and/or /path which will be restored with the expanded host (e.g., wfbr:8002/dir/lynx will become http://www.wfbr.edu:8002/dir/lynx). The prefixes will not be used if the first element ends in a dot (or has a dot before the :port or /path), and similarly the suffixes will not be used if the the first element begins with a dot (e.g., .nyu.edu will become http://www.nyu.edu without testing www.nyu.com). Lynx will try to guess the scheme based on the first field of the expanded host name, and use "http://" as the default (e.g., gopher.wfbr.edu or gopher.wfbr. will be made gopher://gopher.wfbr.edu).

Default value

URL_DOMAIN_PREFIXES:www.
URL_DOMAIN_SUFFIXES:.com,.edu,.net,.org
URL_DOMAIN_PREFIXES:www.,web.,search.,home.,user.,users.,ftp.
URL_DOMAIN_SUFFIXES:.net,.org,.com,.co,.ca,.edu,.ac,.gov,.mil

`URL_DOMAIN_SUFFIXES` - Interaction

BOLD_H1:FALSE BOLD_H1:TRUE

`BOLD_NAME_ANCHORS` - Appearance

Description

If BOLD_NAME_ANCHORS is set to TRUE the content of anchors without an HREF attribute, (i.e., anchors with a NAME or ID attribute) will have the HT_BOLD default style. The compilation default is FALSE. On Unix, compilation with -DUNDERLINE_LINKS also will apply to the HT_BOLD style for NAME (ID) anchors when BOLD_NAME_ANCHORS is TRUE.

Default value

BOLD_NAME_ANCHORS:FALSE

`DEFAULT_CACHE_SIZE` - Internal Behavior

Description

The DEFAULT_CACHE_SIZE specifies the number of WWW documents to be cached in memory at one time.

This so-called cache size (actually, number) is defined in userdefs.h and may be modified here and/or with the command line argument -cache=NUMBER The minimum allowed value is 2, for the current document and at least one to fetch, and there is no absolute maximum number of cached documents. On Unix, and VMS not compiled with VAXC, whenever the number is exceeded the least recently displayed document will be removed from memory.

On VMS compiled with VAXC, the DEFAULT_VIRTUAL_MEMORY_SIZE specifies the amount (bytes) of virtual memory that can be allocated and not yet be freed before previous documents are removed from memory. If the values for both the DEFAULT_CACHE_SIZE and DEFAULT_VIRTUAL_MEMORY_SIZE are exceeded, then the least recently displayed documents will be freed until one or the other value is no longer exceeded. The default value is defined in userdefs.h.

The Unix and VMS (but not VAXC) implementations use the C library malloc's and calloc's for memory allocation, but procedures for taking the actual amount of cache into account still need to be developed. They use only the DEFAULT_CACHE_SIZE value, and that specifies the absolute maximum number of documents to cache (rather than the maximum number only if DEFAULT_VIRTUAL_MEMORY_SIZE has been exceeded, as with VAXC/VAX).

Default value

DEFAULT_CACHE_SIZE:10
DEFAULT_VIRTUAL_MEMORY_SIZE:512000
DEFAULT_CACHE_SIZE:666

`DEFAULT_VIRTUAL_MEMORY_SIZE` - Internal Behavior

The default defined here or in userdefs.h can be toggled via the -resubmit_forms command line switch.

Default value

ALWAYS_RESUBMIT_POSTS:FALSE

`TRIM_INPUT_FIELDS` - Internal Behavior

Description

If TRIM_INPUT_FIELDS is set TRUE, Lynx will trim trailing whitespace (e.g., space, tab, carriage return, line feed and form feed) from the text entered into form text and textarea fields. Older versions of Lynx do this trimming unconditionally, but other browsers do not, which would yield different behavior for CGI scripts.

Default value

TRIM_INPUT_FIELDS:FALSE

`NO_ISMAP_IF_USEMAP` - HTML Parsing

`LOCAL_EXECUTION_LINKS_ALWAYS_ON` - CGI scripts

Description

Local execution links and scripts are by default completely disabled, unless a change is made to the userdefs.h file to enable them or the configure script is used with the corresponding options (--enable-exec-links and --enable-exec-scripts). See the Lynx source code distribution and the userdefs.h file for more detail on enabling execution links and scripts.

If you have enabled execution links or scripts the following two variables control Lynx's action when an execution link or script is encountered.

If LOCAL_EXECUTION_LINKS_ALWAYS_ON is set to TRUE any execution link or script will be executed no matter where it came from. This is EXTREMELY dangerous. Since Lynx can access files from anywhere in the world, you may encounter links or scripts that will cause damage or compromise the security of your system.

If LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE is set to TRUE only links or scripts that reside on the local machine and are referenced with a URL beginning with "file://localhost/" or meet TRUSTED_EXEC or ALWAYS_TRUSTED_EXEC rules (see below) will be executed. This is much less dangerous than enabling all execution links, but can still be dangerous.

Default value

LOCAL_EXECUTION_LINKS_ALWAYS_ON:FALSE
LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:FALSE
LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:TRUE

`LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE` - CGI scripts

Description

Please see the description of LOCAL_EXECUTION_LINKS_ALWAYS_ON

`TRUSTED_EXEC` - CGI scripts

Description

If LOCAL_EXECUTION_LINK_ON_BUT_NOT_REMOTE is TRUE, and no TRUSTED_EXEC rule is defined, it defaults to "file://localhost/" and any lynxexec or lynxprog command will be permitted if it was referenced from within a document whose URL begins with that string. If you wish to restrict the referencing URLs further, you can extend the string to include a trusted path. You also can specify a trusted directory for http URLs, which will then be treated as if they were local rather than remote. For example:

TRUSTED_EXEC:file://localhost/trusted/ TRUSTED_EXEC:http://www.wfbr.edu/trusted/

If you also wish to restrict the commands which can be executed, create a series of rules with the path (Unix) or command name (VMS) following the string, separated by a tab. For example:

Unix:

TRUSTED_EXEC:file://localhost/<tab>/bin/cp TRUSTED_EXEC:file://localhost/<tab>/bin/rm

VMS:

TRUSTED_EXEC:file://localhost/<tab>copy TRUSTED_EXEC:file://localhost/<tab>delete

Once you specify a TRUSTED_EXEC referencing string, the default is replaced, and all the referencing strings you desire must be specified as a series. Similarly, if you associate a command with the referencing string, you must specify all of the allowable commands as a series of TRUSTED_EXEC rules for that string. If you specify ALWAYS_TRUSTED_EXEC rules below, you need not repeat them as TRUSTED_EXEC rules.

If EXEC_LINKS and JUMPFILE have been defined, any lynxexec or lynxprog URLs in that file will be permitted, regardless of other settings. If you also set LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:TRUE and a single TRUSTED_EXEC rule that will always fail (e.g., "none"), then *ONLY* the lynxexec or lynxprog URLs in JUMPFILE (and any ALWAYS_TRUSTED_EXEC rules, see below) will be allowed. Note, however, that if Lynx was compiled with CAN_ANONYMOUS_JUMP set to FALSE (default is TRUE), or -restrictions=jump is included with the -anonymous switch at run time, then users of an anonymous account will not be able to access the jumps file or enter "j"ump shortcuts, and this selective execution feature will be overridden as well (i.e., they will only be able to access lynxexec or lynxprog URLs which meet any ALWAYS_TRUSTED_EXEC rules).

Default value

TRUSTED_EXEC:none

`ALWAYS_TRUSTED_EXEC` - CGI scripts

Description

If EXEC_LINKS was defined, any lynxexec or lynxprog URL can be made always enabled by an ALWAYS_TRUSTED_EXEC rule for it. This is useful for anonymous accounts in which you have disabled execution links generally, and may also have disabled jumps file links, but still want to allow execution of particular utility scripts or programs. The format is like that for TRUSTED_EXEC. For example:

Unix:

ALWAYS_TRUSTED_EXEC:file://localhost/<tab>/usr/local/kinetic/bin/usertime ALWAYS_TRUSTED_EXEC:http://www.more.net/<tab>/usr/local/kinetic/bin/who.sh

VMS:

ALWAYS_TRUSTED_EXEC:file://localhost/<tab>usertime ALWAYS_TRUSTED_EXEC:http://www.more.net/<tab>show users

The default ALWAYS_TRUSTED_EXEC rule is "none".

Default value

ALWAYS_TRUSTED_EXEC:none

`TRUSTED_LYNXCGI` - CGI scripts

`FORCE_SSL_COOKIES_SECURE` - Cookies

Description

If FORCE_SSL_COOKIES_SECURE is set to TRUE, then SSL encrypted cookies received from https servers never will be sent unencrypted to http servers. The compilation default is to impose this block only if the https server included a secure attribute for the cookie. The normal default or that defined here can be toggled via the -force_secure command line switch.

Default value

FORCE_SSL_COOKIES_SECURE:FALSE
FORCE_SSL_COOKIES_SECURE:TRUE

`MAIL_SYSTEM_ERROR_LOGGING` - Internal Behavior

Description

MAIL_SYSTEM_ERROR_LOGGING will send a message to the owner of the information, or ALERTMAIL if there is no owner, every time that a document cannot be accessed!

NOTE: This can generate A LOT of mail, be warned.

Default value

MAIL_SYSTEM_ERROR_LOGGING:FALSE

`CHECKMAIL` - Internal Behavior

`NEWS_MAX_CHUNK` - News-groups

Please see the description of COOKIE_ACCEPT_DOMAINS

`COOKIE_LOOSE_INVALID_DOMAINS` - Cookies

Description

COOKIE_LOOSE_INVALID_DOMAINS, COOKIE_STRICT_INVALID_DOMAINS, and COOKIE_QUERY_INVALID_DOMAINS are comma-delimited lists of domains. They control the degree of validity checking that is applied to cookies for the specified domains. Note that in order to match cookies, domains have to be spelled out exactly in the form in which they would appear on the Cookie Jar page (case is insignificant). They are not wildcards. Domains that apply to more than one host have a leading ".", but have to match *the cookie's* domain exactly. If a domain is set to strict checking, strict conformance to RFC2109 will be applied. A domain with loose checking will be allowed to set cookies with an invalid path or domain attribute. All domains will default to asking the user for confirmation in case of an invalid path or domain. Cookie validity checking takes place as a separate step before the final decision to accept or reject (see previous options), therefore a cookie that passes validity checking may still be automatically rejected or cause another prompt.

Default value

COOKIE_LOOSE_INVALID_DOMAINS:none
COOKIE_STRICT_INVALID_DOMAINS:none
COOKIE_QUERY_INVALID_DOMAINS:none
COOKIE_LOOSE_INVALID_DOMAINS:www.BeautyDestroyed.com

`COOKIE_STRICT_INVALID_DOMAINS` - Cookies

Description

Please see the description of COOKIE_LOOSE_INVALID_DOMAINS

`COOKIE_QUERY_INVALID_DOMAINS` - Cookies

Description

Please see the description of COOKIE_LOOSE_INVALID_DOMAINS

`MAX_COOKIES_DOMAIN` - Cookies

Description

MAX_COOKIES_DOMAIN, MAX_COOKIES_GLOBAL and MAX_COOKIES_BUFFER are limits on the total number of cookies for each domain, globally, and the per-cookie buffer size. These limits are by default large enough for reasonable usage; if they are very high, some sites may present undue performance waste.

max_cookies_domain:50 max_cookies_global:500 max_cookies_buffer:4096

`MAX_COOKIES_GLOBAL` - Cookies

Description

Please see the description of MAX_COOKIES_DOMAIN

`MAX_COOKIES_BUFFER` - Cookies

Examples:

SYSTEM_MAIL:/usr/lib/sendmail

SYSTEM_MAIL_FLAGS:-t -oi

`SYSTEM_MAIL_FLAGS` - Mail-related

PRINTER, DOWNLOADER & UPLOADER DEFINITIONS: Lynx has 4 pre-defined print options & 1 pre-defined download option, which are called up on-screen when `p' or `d' are entered; any number of options can be added by the user, as explained below. Uploaders can be defined only for UNIX with DIRED_SUPPORT: see the Makefile in the top directory & the header of src/LYUpload.c .

For `p' pre-defined options are: `Save to local file', `E-mail the file', `Print to screen' and `Print to local printer attached to vt100'. `Print to screen' allows file transfers in the absence of alternatives and is often the only option allowed here for anonymous users; the 3rd & 4th options are not pre-defined for DOS/WINDOWS versions of Lynx. For `d' the pre-defined option is: `Download to local file'.

To define your own print or download option use the following formats:

PRINTER:<name>:<command>:<option>:<lines/page>[:<environment>]

DOWNLOADER:<name>:<command>:<option>[:<environment>]

<name> is what you will see on the print/download screen.

<command> is the command your system will execute:
the 1st %s in the command will be replaced by the temporary filename used by Lynx; a 2nd %s will be replaced by a filename of your choice, for which Lynx will prompt, offering a suggestion. On Unix, which has pipes, you may use a "|" as the first character of the command, and Lynx will open a pipe to the command. If the command format of your printer/downloader requires a different layout, you will need to use a script (see the last 2 download examples below).

<option> TRUE : the printer/downloader will always be ENABLED,
except that downloading is disabled when -validate is used; FALSE : both will be DISABLED for anonymous users and printing will be disabled when -noprint is used.

<lines/page> (printers: optional) the number of lines/page (default 66):
used to compute the approximate output size and prompt if the document is > 4 printer pages; it uses current screen length for the computation when `Print to screen' is selected.

[:<environment>]
optional, if XWINDOWS then printer/downloader will be enabled if DISPLAY environment variable IS defined and disabled otherwise, if environment is NON_XWINDOWS then printer/downloader will be enabled if DISPLAY environment variable IS NOT defined and disabled otherwise, for anything else or if environment is not specified printer/downloader is always enabled.

You must put the whole definition on one line; if you use a colon, precede it with a backslash.

`Printer' can be any file-handling program you find useful, even if it does not physically print anything.

Usually, down/up-loading involves the use of (e.g.) Ckermit or ZModem to transfer files to a user's local machine over a serial link, but download options do not have to be download-protocol programs.

Printer examples:

Examples:

PRINTER:Computer Center printer:lpr -Pccprt %s:FALSE

PRINTER:Office printer:lpr -POffprt %s:TRUE

PRINTER:VMS printer:print /queue=cc$print %s:FALSE:58

If you have a very busy VMS print queue and Lynx deletes the temporary files before they have been queued, use the VMSPrint.com included in the distribution:

Example:

PRINTER:Busy VMS printer:@Lynx_Dir\:VMSPrint sys$print %s:FALSE:58

To specify a print option at run-time: NBB if you have ANONYMOUS users, DO NOT allow this option!

Example:

PRINTER:Specify at run-time:echo -n "Enter a print command\: "; read word; sh -c "$word %s":FALSE

To pass to a sophisticated file viewer: -k suppresses invocation of hex display mode if 8-bit or control characters are present; +s invokes secure mode (see ftp://space.mit.edu/pub/davis/most):

Example:

PRINTER:Use Most to view:most -k +s %s:TRUE:23

Downloader examples: in Kermit, -s %s is the filename sent, -a %s the filename on arrival (if they are given in reverse order here, the command will fail):

Example:

DOWNLOADER:Use Kermit to download to the terminal:kermit -i -s %s -a %s:TRUE

NB don't use -k with Most, so that binaries will invoke hexadecimal mode:

Example:

DOWNLOADER:Use Most to view:most +s %s:TRUE

The following example gives wrong filenames (`sz' doesn't support a suggested filename parameter):

Example:

DOWNLOADER:Use Zmodem to download to the local terminal:sz %s:TRUE

The following example returns correct filenames by using a script to make a subdirectory in /tmp, but may conflict with very strong security or permissions restrictions:

Example:

DOWNLOADER:Use Zmodem to download to the local terminal:set %s %s;td=/tmp/Lsz$$;mkdir $td;ln -s $1 $td/"$2";sz $td/"$2";rm -r $td:TRUE

Examples:

UPLOADER:Use Kermit to upload from your computer: kermit -i -r -a %s:TRUE

UPLOADER:Use Zmodem to upload from your computer: rz %s:TRUE

Note for OS/390: /* S/390 -- gil -- 1464 */ The following is strongly recommended to undo ASCII->EBCDIC conversion.

Example:

DOWNLOADER:Save OS/390 binary file: iconv -f IBM-1047 -t ISO8859-1 %s >%s:FALSE

Default value

DOWNLOADER:<BR> Open in GUI [generic `open this' command]:thunar %s:TRUE

`DOWNLOADER` - External Programs

Description

Please see the description of PRINTER

`UPLOADER` - External Programs

Description

If QUIT_DEFAULT_YES is TRUE then when the QUIT command is entered, any response other than n or N will confirm. It should be FALSE if you prefer the more conservative action of requiring an explicit Y or y to confirm. The default defined here will override that in userdefs.h.

Default value

QUIT_DEFAULT_YES:TRUE

`HISTORICAL_COMMENTS` - HTML Parsing

Description

If HISTORICAL_COMMENTS is TRUE, Lynx will revert to the "Historical" behavior of treating any '>' as a terminator for comments, instead of seeking a valid '-->' terminator (note that white space can be present between the '--' and '>' in valid terminators). The compilation default is FALSE.

The compilation default, or default defined here, can be toggled via a "-historical" command line switch, and via the LYK_HISTORICAL command key.

Default value

HISTORICAL_COMMENTS:FALSE

`MINIMAL_COMMENTS` - HTML Parsing

Description

If MINIMAL_COMMENTS is TRUE, Lynx will not use Valid comment parsing of '--' pairs as serial comments within an overall comment element, and instead will seek only a '-->' terminator for the overall comment element. This emulates the Netscape v2.0 comment parsing bug, and will help Lynx cope with the use of dashes as "decorations", which consequently has become common in so-called "Enhanced for Netscape" pages. Note that setting Historical comments on will override the Minimal or Valid setting.

The compilation default for MINIMAL_COMMENTS is FALSE, but we'll set it TRUE here, until Netscape gets its comment parsing right, and "decorative" dashes cease to be so common.

The compilation default, or default defined here, can be toggled via a "-minimal" command line switch, and via the LYK_MINIMAL command key.

Default value

MINIMAL_COMMENTS:TRUE
MINIMAL_COMMENTS:TRUE

Description

If SCAN_FOR_BURIED_NEWS_REFS is set to TRUE, Lynx will scan the bodies of news articles for buried article and URL references and convert them to links. The compilation default is TRUE, but some email addresses enclosed in angle brackets ("<user@address>") might be converted to false news links, and uuencoded messages might be corrupted. The conversion is not done when the display is toggled to source or when "d"ownloading, so uuencoded articles can be saved intact regardless of these settings.

The default setting can be toggled via a "-buried_news" command line switch.

Default value

SCAN_FOR_BURIED_NEWS_REFS:TRUE

`PREPEND_BASE_TO_SOURCE` - Appearance

Description

If PREPEND_BASE_TO_SOURCE is set to FALSE, Lynx will not prepend a Request URL comment and BASE element to text/html source files when they are retrieved for "d"ownloading or passed to "p"rint functions. The compilation default is TRUE. Note that this prepending is not done for -source dumps, unless the -base switch also was included on the command line, and the latter switch overrides the setting of the PREPEND_BASE_TO_SOURCE configuration variable.

Default value

PREPEND_BASE_TO_SOURCE:TRUE

`GLOBAL_EXTENSION_MAP` - External Programs

`SUFFIX_ORDER` - External Programs

Description

With SUFFIX_ORDER the precedence of suffix mappings can be changed. Two kinds of settings are recognized:

PRECEDENCE_OTHER or PRECEDENCE_HERE
Suffix mappings can come from four sources: (1) SUFFIX rules given here - see below, (2) builtin defaults (HTInit.c), and the (3) GLOBAL_EXTENSION_MAP and (4) PERSONAL_EXTENSION_MAP files. The order of precedence is normally as listed: (1) has the *lowest*, (4) has the *highest* precedence if there are conflicts. In other words, SUFFIX mappings here are overridden by conflicting ones elsewhere. This default ordering is called PRECEDENCE_OTHER. With PRECEDENCE_HERE, the order becomes (2) (3) (4) (1), i.e. mappings here override others made elsewhere.

NO_BUILTIN
This disables all builtin default rules. In other words, (2) in the list above is skipped. Some recognition for compressed files (".gz", ".Z") is still hardwired. A mapping for some basic types, at least for text/html is probably necessary to get a usable configuration, it can be given in a SUFFIX rule below or an extension map file.
Both kinds of settings can be combined, separated by comma as in
SUFFIX_ORDER:PRECEDENCE_HERE,NO_BUILTIN
Note: Using PRECEDENCE_HERE has only an effect on SUFFIX rules that follow. Moreover, if GLOBAL_EXTENSION_MAP or PERSONAL_EXTENSION_MAP directives are used, they should come *before* a SUFFIX_ORDER:PRECEDENCE_HERE.

Default value

SUFFIX_ORDER:PRECEDENCE_OTHER

`SUFFIX` - External Programs

Description

The SUFFIX definition takes the form of:

SUFFIX:<file extension>:<mime type>:<encoding>:<quality>:<description>

All fields after <mime type> are optional (including the separators if no more fields follow).

<file extension> trailing end of file name. This need not strictly
be a file extension as understood by the OS, a dot has to be given explicitly if it is indented, for some uses one could even match full filenames here. In addition, two forms are special: "*.*" and "*" refer to the defaults for otherwise unmatched files (the first for filenames with a dot somewhere in the name, the second without), these are currently mapped to text/plain in the (HTInit.c) builtin code.

<mime type> a MIME content type. It can also contain a charset
parameter, see example below. This should be given in all lowercase, use <description> for more fancy labels. It can be left empty if an HTTP style encoding is given.

Fields in addition to the usual ones are

<encoding> either a mail style trivial encoding (7bit, 8bit, binary)
which could be used on some systems to determine how to open local files (currently it isn't), and is used to determine transfer mode for some FTP URLs; or a HTTP style content encoding (gzip (equivalent to x-gzip), compress)

<quality> a floating point quality factor, usually between 0.0 and 1.0
currently unused in most situations.

<description> text that can appear in FTP directory listings, and in
local directory listings (see LIST_FORMAT, code %t)

For instance the following definition maps the extension ".gif" to the mime type "image/gif"

Example:

SUFFIX:.gif:image/gif

The following can be used if you have a convention to label HTML files in some character set that differs from your local default (see also ASSUME_LOCAL_CHARSET) with a different extension, here ".html-u8". It also demonstrates use of the description field, note extra separators for omitted fields:

Example:

SUFFIX:.html-u8:text/html;charset=utf-8:::UTF-8 HTML

The following shows how a suffix can indicate a combination of MIME type and compression method. (The ending ".ps.gz" should already be recognized by default; the form below could be used on systems that don't allow more than one dot in filenames.)

Example:

SUFFIX:.ps_gz:application/postscript:gzip::gzip'd Postscript

The following is meant to match a full filename (but can match any file ending in "core", so be careful):

Example:

SUFFIX:core:application/x-core-file

file suffixes are case INsensitive!

The suffix definitions listed here in the default lynx.cfg file are similar to those normally established via src/HTInit.c. You can change the defaults by editing that file or disable them, or via the global or personal mime.types files at run time (except for the additional fields). Assignments made here are overridden by entries in those files unless preceded with a SUFFIX_ORDER:PRECEDENCE_HERE.

Examples:

SUFFIX:.ps:application/postscript

SUFFIX:.eps:application/postscript

SUFFIX:.ai:application/postscript

SUFFIX:.rtf:application/rtf

SUFFIX:.snd:audio/basic

SUFFIX:.gif:image/gif

SUFFIX:.rgb:image/x-rgb

SUFFIX:.png:image/png

SUFFIX:.xbm:image/x-xbitmap

SUFFIX:.tiff:image/tiff

SUFFIX:.jpg:image/jpeg

SUFFIX:.jpeg:image/jpeg

SUFFIX:.mpg:video/mpeg

SUFFIX:.mpeg:video/mpeg

SUFFIX:.mov:video/quicktime

SUFFIX:.hqx:application/mac-binhex40

SUFFIX:.bin:application/octet-stream

SUFFIX:.exe:application/octet-stream

SUFFIX:.tar:application/x-tar

SUFFIX:.tgz:application/x-tar:gzip

SUFFIX:.Z::compress

SUFFIX:.gz::gzip

SUFFIX:.bz2:application/x-bzip2

SUFFIX:.zip:application/zip

SUFFIX:.lzh:application/x-lzh

SUFFIX:.lha:application/x-lha

SUFFIX:.dms:application/x-dms

SUFFIX:.html:text/html

SUFFIX:.txt:text/plain

`XLOADIMAGE_COMMAND` - External Programs

Description

VMS:
XLOADIMAGE_COMMAND will be used as a default in src/HTInit.c for viewing image content types when the DECW$DISPLAY logical is set. Make it the foreign command for your system's X image viewer (commonly, "xv"). It can be anything that will handle GIF, TIFF and other popular image formats. Freeware ports of xv for VMS are available in the ftp://ftp.wku.edu/vms/unsupported and http://www.openvms.digital.com/cd/XV310A/ subdirectories. You must also have a "%s" for the filename. The default is defined in userdefs.h and can be overridden here, or via the global or personal mailcap files (see below).

Make this empty (but not commented out) if you don't have such a viewer or want to disable the built-in default viewer mappings for image types.

Default value

XLOADIMAGE_COMMAND:xv %s

`VIEWER` - External Programs

Description

MIME types may be assigned to external viewers using the VIEWER definition.

NOTE: if you do not define a viewer to a new MIME type
that you assigned above then it will be saved to disk by default. It is normally preferable to define new viewers in MAILCAP files (see below) instead of here: Definitions here are overridden by those in MAILCAP files and even by some built-in defaults in src/HTInit.c.

The VIEWER definition takes the form of:
VIEWER:<mime type>:<viewer command>[:<environment>]
where -mime type is the MIME content type of the file
-viewer command is a system command that can be used to display the file where %s is replaced within the command with the physical filename (e.g., "ghostview %s" becomes "ghostview /tmp/temppsfile")
-environment is optional. The only valid keywords
are currently XWINDOWS and NON_XWINDOWS. If the XWINDOWS environment is specified then the viewer will only be defined when the user has the environment variable DISPLAY (DECW$DISPLAY on VMS) defined. If the NON_XWINDOWS environment is specified the specified viewer will only be defined when the user DOES NOT have the environment variable DISPLAY defined.
examples:
VIEWER:image/gif:xli %s:XWINDOWS
VIEWER:image/gif:ascii-view %s:NON_XWINDOWS VIEWER:application/start-elm:elm

You must put the whole definition on one line.

If you must use a colon in the viewer command, precede it with a backslash!

The MIME_type:viewer:XWINDOWS definitions listed here in the lynx.cfg file are among those established via src/HTInit.c. For the image types, HTInit.c uses the XLOADIMAGE_COMMAND definition in userdefs.h or above (open is used for NeXT). You can change any of these defaults via the global or personal mailcap files. Assignments made here will be overridden by entries in those files.

Examples:

VIEWER:application/postscript:ghostview %s&:XWINDOWS

VIEWER:image/gif:xli %s&:XWINDOWS

VIEWER:image/x-xbm:xli %s&:XWINDOWS

VIEWER:image/png:xli %s&:XWINDOWS

VIEWER:image/tiff:xli %s&:XWINDOWS

VIEWER:image/jpeg:xli %s&:XWINDOWS

VIEWER:video/mpeg:mpeg_play %s &:XWINDOWS

`GLOBAL_MAILCAP` - External Programs

Description

The global and personal MAILCAP files allow you to specify external viewers to be spawned when Lynx encounters different MIME types, which will override any of the suffix maps in this (lynx.cfg) configuration file, or in src/HTInit.c. See http://www.internic.net/rfc/rfc1524.txt and the example mailcap file in the samples subdirectory.

Unix:

Default value

GLOBAL_MAILCAP:/usr/local/lib/mosaic/mailcap

VMS:

Default value

GLOBAL_MAILCAP:Lynx_Dir:mailcap

Sought in user's home (Unix) or sys$login (VMS) directory.

Description

If your terminal (or terminal emulator, or operating system) does not support 8-bit input (at all or in easy way), you can use Lynx to generate 8-bit characters from 7-bit ones output by terminal.

Currently available keyboard layouts:
ROT13'd keyboard layout JCUKEN Cyrillic, for AT 101-key kbd YAWERTY Cyrillic, for DEC LK201 kbd

This feature is ifdef'd with EXP_KEYBOARD_LAYOUT.

Default value

KEYBOARD_LAYOUT:JCUKEN Cyrillic, for AT 101-key kbd

`KEYMAP` - Keyboard Input

Description

Key remapping definitions!

You may redefine the keymapping of any function in Lynx by using the KEYMAP option. The basic form of KEYMAP is:
KEYMAP:<KEYSTROKE>:<LYNX FUNCTION>
(See below for an extended format.)

You must map upper and lowercase keys separately.

A representative list of functions mapped to their default keys is provided below. All of the mappings are commented out by default since they just repeat the default mappings, except for TOGGLE_HELP (see below). See LYKeymap.c for the complete key mapping. Use the "K"eymap command when running Lynx for a list of the _current_ keymappings.

(However, in contrast to the output of "K" command, "H"elp (lynx_help/*.html and lynx_help/keystrokes/*.html files) shows the default mapping unless you change that files manually, so you are responsible for possible deviations when you are changing any KEYMAP below).


 Keystrokes for special keys are represented by the following codes:
         Up Arrow: 0x100
       Down Arrow: 0x101
      Right Arrow: 0x102
       Left Arrow: 0x103
        Page Down: 0x104
          Page Up: 0x105
      Keypad Home: 0x106 (see also 0x10A)
       Keypad End: 0x107 (see also 0x10B)
   Function key 1: 0x108
 vt100   Help Key: 0x108
 vt100     Do Key: 0x109
 vt100   Find Key: 0x10A (The key with label "Home" may be treated as Find)
 vt100 Select Key: 0x10B (The key with label "End" may be treated as Select)
       Insert Key: 0x10C
 Remove (Del) Key: 0x10D
      ignored key  0x10E (reserved for internal use, DO_NOTHING)
 Back (Shift) Tab: 0x10F
    reserved code  0x11D (reserved for internal use with -use_mouse)
    reserved code  0x290 (reserved for internal use with -use_mouse)

Other codes not listed above may be available for additional keys, depending on operating system and libraries used to compile Lynx. On some systems, if compiled with recent versions of slang or ncurses (if macro USE_KEYMAPS was in effect during compilation), an additional level of key mapping is supported via an external ".lynx-keymaps" file. This file, if found in the home directory at startup, will always be used under those conditions; see lynx-keymaps distributed in the samples subdirectory for further explanation. Note that mapping via .lynx-keymaps, if applicable, is a step that logically comes before the mappings done here: KEYMAP maps the result of that step (which still represents a key) to a function (which represents an action that Lynx should perform).

KEYMAP:0x5C:SOURCE              # Toggle source viewing mode (show HTML source)
KEYMAP:^R:RELOAD                # Reload the current document and redisplay
KEYMAP:^U:NEXT_DOC              # Undo PREV_DOC)
KEYMAP:q:QUIT                   # Ask the user to quit
KEYMAP:Q:ABORT                  # Quit without verification
KEYMAP:0x20:NEXT_PAGE           # Move down to next page
KEYMAP:-:PREV_PAGE              # Move up to previous page
KEYMAP:^P:UP_TWO                # Move display up two lines
KEYMAP:0x10C:UP_TWO             # Function key Insert - Move display up two lines
KEYMAP:^N:DOWN_TWO              # Move display down two lines
KEYMAP:0x10D:DOWN_TWO           # Function key Remove - Move display down two lines
KEYMAP:(:UP_HALF                # Move display up half a page
KEYMAP:):DOWN_HALF              # Move display down half a page
KEYMAP:^W:REFRESH               # Refresh the screen
KEYMAP:^A:HOME                  # Go to top of current document
KEYMAP:0x106:HOME               # Keypad Home - Go to top of current document
KEYMAP:0x10A:HOME               # Function key Find - Go to top of current document
KEYMAP:^E:END                   # Go to bottom of current document
KEYMAP:0x107:END                # Keypad End - Go to bottom of current document
KEYMAP:0x10B:END                # Function key Select - Go to bottom of current document
KEYMAP:0x100:PREV_LINK          # Move to the previous link or page
KEYMAP:0x101:NEXT_LINK          # Move to the next link or page
KEYMAP:0x10F:FASTBACKW_LINK     # Back Tab - Move to previous link or text area
KEYMAP:^I:FASTFORW_LINK         # Tab key - Move always to next link or text area
KEYMAP:^:FIRST_LINK             # Move to the first link on line
KEYMAP:$:LAST_LINK              # Move to the last link on line
KEYMAP:<:UP_LINK                # Move to the link above
KEYMAP:>:DOWN_LINK              # Move to the link below
KEYMAP:0x7F:HISTORY             # Show the history list
KEYMAP:0x08:HISTORY             # Show the history list
KEYMAP:0x103:PREV_DOC           # Return to the previous document in history stack
KEYMAP:0x102:ACTIVATE           # Select the current link
KEYMAP:0x109:ACTIVATE           # Function key Do - Select the current link
KEYMAP:g:GOTO                   # Goto a random URL
KEYMAP:G:ECGOTO                 # Edit the current document's URL and go to it
KEYMAP:H:HELP                   # Show default help screen
KEYMAP:0x108:DWIMHELP           # Function key Help - Show a help screen
KEYMAP:i:INDEX                  # Show default index
*** Edit FORM_LINK_* messages in LYMessages_en.h if you change NOCACHE ***
KEYMAP:x:NOCACHE                # Force submission of form or link with no-cache
*** Do not change INTERRUPT from "z" & "Z" ***
KEYMAP:z:INTERRUPT              # Interrupt network transmission
KEYMAP:m:MAIN_MENU              # Return to the main menu
KEYMAP:o:OPTIONS                # Show the options menu
KEYMAP:i:INDEX_SEARCH           # Search a server based index
KEYMAP:/:WHEREIS                # Find a string within the current document
KEYMAP:n:NEXT                   # Find next occurrence of string within document
KEYMAP:c:COMMENT                # Comment to the author of the current document
KEYMAP:C:CHDIR                  # Change current directory
KEYMAP:e:EDIT                   # Edit current document or form's textarea (call: ^Ve)
KEYMAP:E:ELGOTO                 # Edit the current link's URL or ACTION and go to it
KEYMAP:=:INFO                   # Show info about current document
KEYMAP:p:PRINT                  # Show print options
KEYMAP:a:ADD_BOOKMARK           # Add current document to bookmark list
KEYMAP:v:VIEW_BOOKMARK          # View the bookmark list
KEYMAP:V:VLINKS                 # List links visited during the current Lynx session
KEYMAP:!:SHELL                  # Spawn default shell
KEYMAP:d:DOWNLOAD               # Download current link
KEYMAP:j:JUMP                   # Jump to a predefined target
KEYMAP:k:KEYMAP                 # Display the current key map
KEYMAP:l:LIST                   # List the references (links) in the current document
KEYMAP:#:TOOLBAR                # Go to the Toolbar or Banner in the current document
KEYMAP:^T:TRACE_TOGGLE          # Toggle detailed tracing for debugging
KEYMAP:;:TRACE_LOG              # View trace log if available for the current session
KEYMAP:*:IMAGE_TOGGLE           # Toggle inclusion of links for all images
KEYMAP:[:INLINE_TOGGLE          # Toggle pseudo-ALTs for inlines with no ALT string
KEYMAP:]:HEAD                   # Send a HEAD request for current document or link
*** Must be compiled with USE_EXTERNALS to enable EXTERN_LINK, EXTERN_PAGE ***
KEYMAP:,:EXTERN_PAGE            # Run external program with current page
KEYMAP:.:EXTERN_LINK            # Run external program with current link
*** Escaping from text input fields with ^V is independent from this: ***
KEYMAP:^V:SWITCH_DTD            # Toggle between SortaSGML and TagSoup HTML parsing
KEYMAP:0x00:DO_NOTHING          # Does nothing (ignore this key)
KEYMAP:0x10E:DO_NOTHING         # Does nothing (ignore this key)
KEYMAP:{:SHIFT_LEFT             # shift the screen left
KEYMAP:}:SHIFT_RIGHT            # shift the screen right
KEYMAP:|:LINEWRAP_TOGGLE        # toggle linewrap on/off, for shift-commands
KEYMAP:~:NESTED_TABLES          # toggle nested-tables parsing on/off

In addition to the bindings available by default, the following functions are not directly mapped to any keys by default, although some of them may be mapped in specific line-editor bindings (effective while in text input fields):


KEYMAP:???:RIGHT_LINK           # Move to the link to the right
KEYMAP:???:LEFT_LINK            # Move to the link to the left
KEYMAP:???:LPOS_PREV_LINK       # Like PREV_LINK, last column pos if form input
KEYMAP:???:LPOS_NEXT_LINK       # Like NEXT_LINK, last column pos if form input
*** Only useful in form text fields , need PASS or prefixing with ^V: ***
KEYMAP:???:DWIMHELP             # Display help page that may depend on context
KEYMAP:???:DWIMEDIT             # Use external editor for context-dependent purpose
*** Only useful in a form textarea, need PASS or prefixing with ^V: ***
KEYMAP:???:EDITTEXTAREA         # use external editor to edit a form textarea
KEYMAP:???:GROWTEXTAREA         # Add some blank lines to bottom of textarea
KEYMAP:???:INSERTFILE           # Insert file into a textarea (just above cursor)
*** Only useful with dired support and OK_INSTALL: ***
KEYMAP:???:INSTALL              # install (i.e. copy) local files to new location

If TOGGLE_HELP is mapped, in novice mode the second help menu line can be toggled among NOVICE_LINE_TWO_A, _B, and _C, as defined in LYMessages_en.h Otherwise, it will be NOVICE_LINE_TWO.

Default value

KEYMAP:O:TOGGLE_HELP # Show other commands in the novice help menu

KEYMAP lines can have one or two additional fields. The extended format is
KEYMAP:<KEYSTROKE>:[<MAIN LYNX FUNCTION>]:<OTHER BINDING>[:<SELECT>]

If the additional field OTHER BINDING specifies DIRED, then the function is mapped in the override table used only in DIRED mode. This is only valid if lynx was compiled with dired support and OK_OVERRIDE defined. A MAIN LYNX FUNCTION must be given (it should of course be one that makes sense in Dired mode), and SELECT is meaningless. Default built-in override mappings are

Default value

KEYMAP:^U:NEXT_DOC:DIRED # Undo going back to the previous document
KEYMAP:.:TAG_LINK:DIRED # Tag a file or directory for later action
KEYMAP:c:CREATE:DIRED # Create a new file or directory
KEYMAP:C:CHDIR:DIRED # change current directory
KEYMAP:f:DIRED_MENU:DIRED # Display a menu of file operations
KEYMAP:m:MODIFY:DIRED # Modify name or location of a file or directory
KEYMAP:r:REMOVE:DIRED # Remove files or directories
KEYMAP:t:TAG_LINK:DIRED # Tag a file or directory for later action
KEYMAP:u:UPLOAD:DIRED # Show menu of "Upload Options"

If the OTHER BINDING field does not specify DIRED, then it is taken as a line-editor action. It is possible to keep the MAIN LYNX FUNCTION field empty in that case, for changing only the line-editing behavior. If alternative line edit styles are compiled in, and modifying a key's line-editor binding on a per style basis is possible, then SELECT can be used to specify which styles are affected. By default, or if SELECT is 0, all line edit styles are affected. If SELECT is a positive integer number, only the binding for the numbered style is changed (numbering is in the order in which styles are shown in the Options Menu, starting with 1 for the Default style). If SELECT is negative (-n), all styles except n are affected.


  NOP           # Do Nothing
  ABORT         # Input cancelled

  BOL           # Go to begin of line
  EOL           # Go to end   of line
  FORW          # Cursor forwards
  FORW_RL       # Cursor forwards or right link
  BACK          # Cursor backwards
  FORWW         # Word forward
  BACKW         # Word back
  BACK_LL       # Cursor backwards or left link

  DELN          # Delete next/curr char
  DELP          # Delete prev      char
  DELNW         # Delete next word
  DELPW         # Delete prev word
  DELBL         # Delete back to BOL
  DELEL         # Delete thru EOL
  ERASE         # Erase the line
  LOWER         # Lower case the line
  UPPER         # Upper case the line

  LKCMD         # In fields: Invoke key command prompt (default for ^V)
  PASS          # In fields: handle as non-lineedit key; in prompts: ignore

Modify following key (prefixing only works within line-editing, edit actions of some resulting prefixed keys are built-in, see Line Editor help pages)
SETM1 # Set modifier 1 flag (default for ^X - key prefix) SETM2 # Set modifier 2 flag (another key prefix - same effect)

May not always be compiled in:


  TPOS          # Transpose characters
  SETMARK       # emacs-like set-mark-command
  XPMARK        # emacs-like exchange-point-and-mark
  KILLREG       # emacs-like kill-region
  YANK          # emacs-like yank
  SWMAP         # Switch input keymap
  PASTE         # ClipBoard to Lynx - Windows Extension

May work differently from expected if not bound to their expected keys:


  CHAR          # Insert printable char (default for all ASCII printable)
  ENTER         # Input complete, return char/lynxkeycode (for RETURN/ENTER)
  TAB           # Input complete, return TAB (for ASCII TAB char ^I)

Internal use, probably not useful for binding, listed for completeness:


  UNMOD         # Fall back to no-modifier command
  AIX           # Hex 97
  C1CHAR        # Insert C1 char if printable

If OTHER BINDING specifies PASS, then if the key is pressed in a text input field it is passed by the built-in line-editor to normal KEYMAP handling, i.e. this flag acts like an implied ^V escape (always overrides line-editor behavior of the key). For example,

Default value

KEYMAP:0x10C:UP_TWO:PASS # Function key Insert - Move display up two lines

Other examples (repeating built-in bindings)

Default value

KEYMAP:^V::LKCMD # set (only) line-edit action for ^V
KEYMAP:^V:SWITCH_DTD:LKCMD # set main lynxaction and line-edit action for ^V
KEYMAP:^U::ERASE:1 # set line-edit binding for ^U, for default style
KEYMAP:^[::SETM2:3 # use escape key as modifier - works only sometimes
KEYMAP:v:SOURCE
KEYMAP:0x10C:UP_TWO
KEYMAP:0x10D:DOWN_TWO
KEYMAP:_:UP_HALF
KEYMAP:-:DOWN_HALF
KEYMAP:b:VIEW_BOOKMARK

`CSWING_PATH` - External Programs

Description

VMS ONLY:
On VMS, CSwing (an XTree emulation for VTxxx terminals) is intended for use as the Directory/File Manager (sources, objects, or executables are available from ftp://narnia.memst.edu/). CSWING_PATH should be defined here or in userdefs.h to your foreign command for CSwing, with any regulatory switches you want included. If not defined, or defined as a zero-length string ("") or "none" (case-insensitive), the support will be disabled. It will also be disabled if the -nobrowse or -selective switches are used, or if the file_url restriction is set.

When enabled, the DIRED_MENU command (normally "f" or "F") will invoke CSwing, normally with the current default directory as an argument to position the user on that node of the directory tree. However, if the current document is a local directory listing, or a local file and not one of the temporary menu or list files, the associated directory will be passed as an argument, to position the user on that node of the tree.

Default value

CSWING_PATH:swing

`AUTO_UNCACHE_DIRLISTS` - Internal Behavior

Description

AUTO_UNCACHE_DIRLISTS determines when local file directory listings are automatically regenerated (by re-reading the actual directory from disk). Set the value to 0 to avoid automatic regeneration in most cases. This is useful for browsing large directories that take some time to read and format. An update can still always be forced with the RELOAD key, and specific DIRED actions may cause a refresh anyway. Set the value to 1 to force regeneration after commands that usually change the directory or some files and would make the displayed info stale, like EDIT and REMOVE. Set it to 2 (the default) or greater to force regeneration even after leaving the displayed directory listing by some action that usually causes no change, like GOTO or entering a file with the ACTIVATE key. This option is only honored in DIRED mode (i.e. when lynx is compiled with DIRED_SUPPORT and it is not disabled with a -restriction). Local directories displayed without DIRED normally act as if AUTO_UNCACHE_DIRLISTS:0 was in effect.

Default value

AUTO_UNCACHE_DIRLISTS:2

`LIST_FORMAT` - Appearance

Description

Unix ONLY:
LIST_FORMAT defines the display for local files when Lynx has been compiled with LONG_LIST defined in the Makefile. The default is set in userdefs.h, normally to "ls -l" format, and can be changed here by uncommenting the indicated lines, or adding a definition with a modified parameter list.

The percent items in the list are interpreted as follows:


        %p      Unix-style permission bits
        %l      link count
        %o      owner of file
        %g      group of file
        %d      date of last modification
        %a      anchor pointing to file or directory
        %A      as above but don't show symbolic links
        %t      type of file (description derived from MIME type)
        %T      MIME type as known by Lynx (from mime.types or default)
        %k      size of file in Kilobytes
        %K      as above but omit size for directories
        %s      size of file in bytes

Anything between the percent and the letter is passed on to sprintf. A double percent yields a literal percent on output. Other characters are passed through literally.

If you want only the filename:

Example:

LIST_FORMAT: %a

If you want a brief output:

Example:

LIST_FORMAT: %4K %-12.12d %a

If you want the Unix "ls -l" format:

Example:

LIST_FORMAT: %p %4l %-8.8o %-8.8g %7s %-12.12d %a

`DIRED_MENU` - External Programs

Description

Unix ONLY:
DIRED_MENU items are used to compose the F)ull menu list in DIRED mode The behavior of the default configuration given here is much the same as it was when this menu was hard-coded but these items can now be adjusted to suit local needs. In particular, many of the LYNXDIRED actions can be replaced with lynxexec, lynxprog and lynxcgi script references.

NOTE that defining even one DIRED_MENU line overrides all the built-in definitions, so a complete set must then be defined here.

Each line consists of the following fields:


        DIRED_MENU:type:suffix:link text:extra text:action

        type: TAG:   list only when one or more files are tagged
              FILE:  list only when the current selection is a regular file
              DIR:   list only when the current selection is a directory
              LINK:  list only when the current selection is a symbolic link

        suffix:  list only if the current selection ends in this pattern

        link text:  the displayed text of the link

        extra text:  the text displayed following the link

        action:  the URL to be followed upon selection

        link text and action are scanned for % sequences that are expanded
        at display time as follows:

                %p  path of current selection
                %f  filename (last component) of current selection
                %t  tagged list (full paths)
                %l  list of tagged file names
                %d  the current directory

Following depends on OK_ZIP

Default value

DIRED_MENU:DIR::Package and compress:(using zip):LYNXDIRED://ZIP%p

Default value

DIRED_MENU:FILE::Compress:(using Unix compress):LYNXDIRED://COMPRESS%p

Some systems only:
Lynx tries to detect window size changes with a signal handler for SIGWINCH if supported. If NONRESTARTING_SIGWINCH is set to TRUE, and the sigaction interface is available on the system, the handler is installed as 'non-restarting'. On some systems (depending on the library used for handling keyboard input, e.g. ncurses), this allows more immediate notification of window size change events. If the value is set to FALSE, the signal() interface is used; this normally makes the handler 'restarting', with the effect that lynx can react to size changes only after some key is pressed. The value can also be set to XWINDOWS; this is equivalent to TRUE when the user has the environment variable DISPLAY defined *at program start*, and equivalent to FALSE otherwise. The non-restarting behavior can also be changed to TRUE or FALSE with the -nonrestarting_sigwinch switch, which overrides the value in this file.

Note that Lynx never re-parses document text purely as a result of a window size change, so text lines may appear truncated after narrowing the window, until the document is reloaded with ^R or a similar key or until a different text is loaded.

The default is FALSE since there is a possibility that non-restarting interrupts may be mis-interpreted as fatal input errors in some configurations (leading to an abrupt program exit), and since this option is useful mostly only for users running Lynx under xterm or a similar X terminal emulator. On systems where the preconditions don't apply this option is ignored.

Default value

NONRESTARTING_SIGWINCH:FALSE
NONRESTARTING_SIGWINCH:TRUE

`NO_FORCED_CORE_DUMP` - Internal Behavior

Description

Unix ONLY:
If NO_FORCED_CORE_DUMP is set to TRUE, Lynx will not force core dumps via abort() calls on fatal errors or assert() calls to check potentially fatal errors. The compilation default normally is FALSE, and can be changed here. The compilation or configuration default can be toggled via the -core command line switch. Note that this setting cannot be used to prevent core dumps with certainty. If this is important, means provided by the operating system or kernel should be used.

Default value

NO_FORCED_CORE_DUMP:FALSE

`COLOR` - Appearance

Description

COLORS (only available if compiled with SVr4 curses or slang)

The line must be of the form:

COLOR:Integer:Foreground:Background


 The Integer value is interpreted as follows:
   0 - normal                      - normal text
   1 - bold                        - hyperlinks, see also BOLD_* options above
   2 - reverse                     - statusline
   3 - bold + reverse              (not used)
   4 - underline                   - text emphasis (EM, I, B tags etc.)
   5 - bold + underline            - hyperlinks within text emphasis
   6 - reverse + underline         - currently selected hyperlink
   7 - reverse + underline + bold  - WHEREIS search hits

 Each Foreground and Background value must be one of:
   black         red            green         brown
   blue          magenta        cyan          lightgray
   gray          brightred      brightgreen   yellow
   brightblue    brightmagenta  brightcyan    white

or (if you have configured using --enable-default-colors with ncurses or slang), "default" may be used for foreground and background.

Note that in most cases a white background is really "lightgray", since terminals generally do not implement bright backgrounds.

Uncomment and change any of the compilation defaults.

Default value

COLOR:0:black:white
COLOR:1:blue:white
COLOR:2:yellow:blue
COLOR:3:green:white
COLOR:4:magenta:white
COLOR:5:blue:white
COLOR:6:red:white
COLOR:6:brightred:black
COLOR:7:magenta:cyan

`COLOR_STYLE` - Appearance

Description

Also known as "lss" (lynx style-sheet), the color-style file assigns color combination to tags and combinations of tags. Normally a non-empty value is compiled into lynx, and the user can override that using the -lss command-line option. The configure script allows one to compile in an empty string. If lynx finds no value for this setting, it simulates the non-color-style assignments using the COLOR settings.

If neither the command-line "-lss" or this COLOR_STYLE setting are given, lynx tries the environment variables "LYNX_LSS" and "lynx_lss". If neither is set, lynx uses the compiled-in value (which as noted, may be empty).

Default value

COLOR_STYLE: lynx.lss
COLOR_STYLE:/usr/share/doc/lynx/lss/opaque.lss

`NESTED_TABLES` - Appearance

Description

This is an experimental feature for improving table layout. It is enabled by default when the COLOR_STYLE configuration is used, and false otherwise.

Default value

NESTED_TABLES: true
NESTED_TABLES:TRUE

`ASSUMED_COLOR` - Appearance

Description

If built with a library that recognizes default colors (usually ncurses or slang), and if the corresponding option is compiled into lynx, lynx initializes it to assume the corresponding foreground and background colors. Default colors are those that the terminal (emulator) itself is initialized to. For instance, you might have an xterm running with black text on a white background, and want lynx to display colored text on the white background, but leave the possibility of using the same configuration to draw colored text on a different xterm, this time using its background set to black.

If built with conventional SVr3/SVr4 curses, tells lynx to use color pair 0 when the given colors match this setting. That gives a similar effect, though not as flexible. You will get the best results by setting the terminal's default colors to match the prevailing text and background colors that you have setup with lynx, and then alter the ASSUMED_COLOR setting to match that. If you do not alter the ASSUMED_COLOR setting, curses assumes color pair 0's background is black, which implies that its foreground (text) is white.

The first value given is the foreground, the second is the background.

Default value

ASSUMED_COLOR:default:default

`DEFAULT_COLORS` - Appearance

Description

Use this feature to disable the default-colors feature at runtime. This is useful for constructing scripts which use the non-color-style scheme, e.g., the oldlynx script.

This should precede ASSUMED_COLOR settings.

Default value

DEFAULT_COLORS:true

`EXTERNAL` - External Programs

Description

External application support. This feature allows Lynx to pass a given URL to an external program. It was written for three reasons.

1) To overcome the deficiency of Lynx_386 not supporting ftp and news.
External programs can be used instead by passing the URL.

2) To allow for background transfers in multitasking systems.
I use wget for http and ftp transfers via the external command.

3) To allow for new URLs to be used through Lynx.
URLs can be made up such as mymail: to spawn desired applications via the external command.

Restrictions can be imposed using -restrictions=externals at the Lynx command line. This will disallow all EXTERNAL lines in lynx.cfg that have FALSE in the 3rd field (not counting the name of the setting). TRUE lines will still function.

The lynx.cfg line is as follows:

EXTERNAL:<url>:<command> %s:<norestriction>:<allow_for_activate>[:environment]

<url> Any given URL. This can be normal ones like ftp or http or it can be one made up like mymail.

<command> The command to run with %s being the URL that will be passed. In Linux I use "wget -q %s &" (no quotes) to spawn a copy of wget for downloading http and ftp files in the background. In Win95 I use "start ncftp %s" to spawn ncftp in a new window.

<norestriction> This complements the -restrictions=externals feature to allow for certain externals to be enabled while restricting others. TRUE means a command will still function while Lynx is restricted. WB

<allow_for_activate> Setting this to TRUE allows the use of this command not only when EXTERN key is pressed, but also when ACTIVATE command is invoked (i.e., activating the link with the given prefix will be equivalent to pressing EXTERN key on it). If this component of the line is absent, then FALSE is assumed.

[:environment] Optional, if XWINDOWS then command is allowed only if $DISPLAY environment variable is set, else if NON_XWINDOWS then command is allowed only if $DISPLAY environment variable is not set, if absent or anything else command is always allowed.

For invoking the command use the EXTERN_LINK or EXTERN_PAGE key. By default EXTERN_LINK is mapped to ".", and EXTERN_PAGE to "," (if the feature is enabled), see the KEYMAP section above.

Default value

EXTERNAL:ftp:wget %s &:TRUE
EXTERNAL:file:thunar %s &:TRUE
EXTERNAL:file:mousepad %s &:TRUE
EXTERNAL:ftp:wget %s &:TRUE
EXTERNAL:ftp:gftp %s &:TRUE
EXTERNAL:http:wget %s &:TRUE
EXTERNAL:http:dillo %s &:TRUE
EXTERNAL:http:opera %s &:TRUE
EXTERNAL:https:wget %s &:TRUE
EXTERNAL:https:dillo %s &:TRUE
EXTERNAL:https:opera %s &:TRUE
EXTERNAL:mailto:sylpheed-claws %s &:TRUE

`RULE` - Internal Behavior

Description

CERN-style rules, EXPERIMENTAL - URL-specific rules

A CERN-style rules file can be given with RULESFILE. Use the system's native format for filenames, on Unix "~" is also recognized. If a filename is given, the file must exist.

Single CERN-style rules can be specified with RULES.

Both options can be repeated, rules accumulate in the order given, they will be applied in first-to-last order. See cernrules.txt in the samples subdirectory for further explanation.

Examples:

RULESFILE:/etc/lynx/cernrules

RULE:Fail gopher:* # reject by scheme

RULE:Pass finger://*@localhost/ # allow this,

RULE:Fail finger:* # but not others

RULE:Redirect http://old.server/* http://new.server/*

`RULESFILE` - Internal Behavior

Description

Please see the description of RULE

`PRETTYSRC` - Appearance

Description

Enable pretty source view

Default value

PRETTYSRC:FALSE
PRETTYSRC:TRUE

`PRETTYSRC_SPEC` - Appearance

Description

Pretty source view settings. These settings are in effect when -prettysrc is specified. The following lexical elements (lexemes) are recognized: comment, tag, attribute, attribute value, generalized angle brackets ( '<' '>' '</' ), entity, hyperlink destination, entire file, bad sequence, bad tag, bad attribute, sgml special.
The following group of option tells which styles will surround each
lexeme. The syntax of option in this group is:

Default value

PRETTYSRC_SPEC:<LEXEMENAME>:<TAGSPEC>:<TAGSPEC>

The first <TAGSPEC> specifies what tags will precede lexemes of that class in the internal html markup. The second - what will be placed (internally) after it. TAGSPEC has the following syntax: <TAGSPEC>:= [ (<TAGOPEN> | <TAGCLOSE>) <SPACE>+ ]* <TAGOPEN>:= tagname[.classname] <TAGCLOSE>:= !tagname

The following table gives correspondence between lexeme and lexeme name


 Lexeme                   LEXEMENAME  FURTHER EXPLANATION
 comment                  COMM
 tag                      TAG         recognized tag name only
 attribute                ATTRIB
 attribute value          ATTRVAL
 generalized brackets     ABRACKET    <  >  </
 entity                   ENTITY
 hyperlink destination    HREF
 entire file              ENTIRE
 bad sequence             BADSEQ      bad entity or invalid construct at text
                                      level.
 bad tag                  BADTAG      Unrecognized construct in generalized
                                      brackets.
 bad attribute            BADATTR     The name of the attribute unknown to lynx
                                      of the tag known to lynx. (i.e.,
                                      attributes of unknown tags will have
                                      markup of  ATTRIB)
 sgml special             SGMLSPECIAL doctype, sgmlelt, sgmlele,
                                      sgmlattlist, marked section, identifier

Notes:

1) The markup for HTML_ENTIRE will be emitted only once - it will surround
entire file source.

2) The tagnames specified by TAGSPEC should be valid html tag names.

3) If the tag/class combination given by TAGOPEN is not assigned a color
style in lss file (for lynx compiled with lss support), that tag/class combination will be emitted anyway during internal html markup. Such combinations will be also reported to the trace log.

4) Lexeme 'tag' means tag name only

5) Angle brackets of html specials won't be surrounded by markup for ABRACKET

Example:

PRETTYSRC_SPEC:COMM:B I:!I !B

HTML comments will be surrounded by <b><i> and </i></b> in the internal html markup

Example:

PRETTYSRC_SPEC:ATTRVAL: span.attrval : !span

Values of the attributes will be surrounded by the <SPAN class=attrval> </SPAN>

Example:

PRETTYSRC_SPEC:HREF::

No special html markup will surround hyperlink destinations ( this means that only default color style for hrefs will be applied to them)

For lynx compiled with lss support, the following settings are the default:

Default value

PRETTYSRC_SPEC:COMM:span.htmlsrc_comment:!span
PRETTYSRC_SPEC:TAG:span.htmlsrc_tag:!span
PRETTYSRC_SPEC:ATTRIB:span.htmlsrc_attrib:!span
PRETTYSRC_SPEC:ATTRVAL:span.htmlsrc_attrval:!span
PRETTYSRC_SPEC:ABRACKET:span.htmlsrc_abracket:!span
PRETTYSRC_SPEC:ENTITY:span.htmlsrc_entity:!span
PRETTYSRC_SPEC:HREF:span.htmlsrc_href:!span
PRETTYSRC_SPEC:ENTIRE:span.htmlsrc_entire:!span
PRETTYSRC_SPEC:BADSEQ:span.htmlsrc_badseq:!span
PRETTYSRC_SPEC:BADTAG:span.htmlsrc_badtag:!span
PRETTYSRC_SPEC:BADATTR:span.htmlsrc_badattr:!span
PRETTYSRC_SPEC:SGMLSPECIAL:span.htmlsrc_sgmlspecial:!span

the styles corresponding to them are present in sample .lss file. For lynx compiled without lss support, the following settings are the default:

Default value

PRETTYSRC_SPEC:COMM:b:!b
PRETTYSRC_SPEC:TAG:b:!b
PRETTYSRC_SPEC:ATTRIB:b:!b
PRETTYSRC_SPEC:ATTRVAL::none
PRETTYSRC_SPEC:ABRACKET:b:!b
PRETTYSRC_SPEC:ENTITY:b:!b
PRETTYSRC_SPEC:HREF::none
PRETTYSRC_SPEC:ENTIRE::none
PRETTYSRC_SPEC:BADSEQ:b:!b
PRETTYSRC_SPEC:BADTAG::none
PRETTYSRC_SPEC:BADATTR::none
PRETTYSRC_SPEC:SGMLSPECIAL:b:!b

`HTMLSRC_ATTRNAME_XFORM` - Appearance

Description

Options HTMLSRC_TAGNAME_XFORM and HTMLSRC_ATTRNAME_XFORM control the way the names of tags and names of attributes are transformed correspondingly. Possible values: 0 - lowercase, 1 - leave as is, 2 - uppercase.

Default value

HTMLSRC_TAGNAME_XFORM:2
HTMLSRC_ATTRNAME_XFORM:2
HTMLSRC_ATTRNAME_XFORM:2
HTMLSRC_TAGNAME_XFORM:2

`HTMLSRC_TAGNAME_XFORM` - Appearance

Description

Please see the description of HTMLSRC_ATTRNAME_XFORM

`PRETTYSRC_VIEW_NO_ANCHOR_NUMBERING` - Appearance

Description

PRETTYSRC_VIEW_NO_ANCHOR_NUMBERING - pretty source view setting If "keypad mode" in "O"ptions screen is "Links are numbered" or "Links and form fields are numbered", and PRETTYSRC_VIEW_NO_ANCHOR_NUMBERING is TRUE, then links won't be numbered in psrc view and will be numbered otherwise. Set this setting to TRUE if you prefer numbered links, but wish to get valid HTML source when printing or mailing when in psrc view. Default is FALSE.

Default value

PRETTYSRC_VIEW_NO_ANCHOR_NUMBERING:FALSE
PRETTYSRC_VIEW_NO_ANCHOR_NUMBERING:TRUE

`FORCE_EMPTY_HREFLESS_A` - HTML Parsing

Description

FORCE_EMPTY_HREFLESS_A - HTML parsing This option mirrors command-line option with the same name. Default is FALSE. If true, then any "A" element without HREF will be closed immediately. This is useful when viewing documentation produced by broken translator that doesn't emit balanced A elements. If lynx was compiled with color styles, setting this option to TRUE will make lynx screen much more reasonable (otherwise all text will probably have color corresponding to the A element).

Default value

FORCE_EMPTY_HREFLESS_A:FALSE
FORCE_EMPTY_HREFLESS_A:TRUE

`HIDDEN_LINK_MARKER` - HTML Parsing

Description

HIDDEN_LINK_MARKER - HTML parsing This option defines the string that will be used as title of hidden link (a link that otherwise will have no label associated with it). Using an empty string as the value will cause lynx to behave in the old way - hidden links will be handled according to other settings (mostly the parameter of --hiddenlinks command-line switch). If the value is non-empty string, hidden link becomes non-hidden so it won't be handled as hidden link, e.g., listed among hidden links on "l"isting page.

Default value

HIDDEN_LINK_MARKER:none
HIDDEN_LINK_MARKER:[EMPTY_HREF]

`JUSTIFY` - Appearance

`ENABLE_LYNXRC` - Internal Behavior

Description

The forms-based O'ptions menu shows a (!) marker beside items which are not saved to ~/.lynxrc -- the reason for disabling some of these items is that they are likely to cause confusion if they are read from the .lynxrc file for each session. However, they can be enabled or disabled using the ENABLE_LYNXRC settings. The default (compiled-in) settings are shown below. The second column is the name by which a setting is saved to .lynxrc (which is chosen where possible to correspond with lynx.cfg). Use "OFF" to disable writing a setting, "ON" to enable it. Settings are read from .lynxrc after the corresponding data from lynx.cfg, so they override lynx.cfg, which is probably what users expect.

Note that a few settings (Cookies and Show images) are comprised of more than one lynx.cfg setting.

ENABLE_LYNXRC:accept_all_cookies:ON
ENABLE_LYNXRC:assume_charset:OFF
ENABLE_LYNXRC:auto_session:OFF
ENABLE_LYNXRC:bookmark_file:ON
ENABLE_LYNXRC:case_sensitive_searching:ON
ENABLE_LYNXRC:character_set:ON
ENABLE_LYNXRC:cookie_accept_domains:ON
ENABLE_LYNXRC:cookie_file:ON
ENABLE_LYNXRC:cookie_loose_invalid_domains:ON
ENABLE_LYNXRC:cookie_query_invalid_domains:ON
ENABLE_LYNXRC:cookie_reject_domains:ON
ENABLE_LYNXRC:cookie_strict_invalid_domains:ON
ENABLE_LYNXRC:dir_list_style:ON
ENABLE_LYNXRC:display:OFF
ENABLE_LYNXRC:emacs_keys:ON
ENABLE_LYNXRC:file_editor:ON
ENABLE_LYNXRC:file_sorting_method:ON
ENABLE_LYNXRC:force_cookie_prompt:OFF
ENABLE_LYNXRC:force_ssl_prompt:OFF
ENABLE_LYNXRC:ftp_passive:OFF
ENABLE_LYNXRC:kblayout:ON
ENABLE_LYNXRC:keypad_mode:ON
ENABLE_LYNXRC:lineedit_mode:ON
ENABLE_LYNXRC:locale_charset:ON
ENABLE_LYNXRC:make_links_for_all_images:OFF
ENABLE_LYNXRC:make_pseudo_alts_for_inlines:OFF
ENABLE_LYNXRC:multi_bookmark:ON
ENABLE_LYNXRC:personal_mail_address:ON
ENABLE_LYNXRC:preferred_charset:ON
ENABLE_LYNXRC:preferred_encoding:OFF
ENABLE_LYNXRC:preferred_language:ON
ENABLE_LYNXRC:preferred_media_types:OFF
ENABLE_LYNXRC:raw_mode:OFF
ENABLE_LYNXRC:run_all_execution_links:ON
ENABLE_LYNXRC:run_execution_links_on_local_files:ON
ENABLE_LYNXRC:scrollbar:OFF
ENABLE_LYNXRC:select_popups:ON
ENABLE_LYNXRC:session_file:OFF
ENABLE_LYNXRC:set_cookies:OFF
ENABLE_LYNXRC:show_color:ON
ENABLE_LYNXRC:show_cursor:ON
ENABLE_LYNXRC:show_dotfiles:ON
ENABLE_LYNXRC:show_kb_rate:OFF
ENABLE_LYNXRC:sub_bookmarks:ON
ENABLE_LYNXRC:tagsoup:OFF
ENABLE_LYNXRC:underline_links:OFF
ENABLE_LYNXRC:user_mode:ON
ENABLE_LYNXRC:useragent:OFF
ENABLE_LYNXRC:verbose_images:ON
ENABLE_LYNXRC:vi_keys:ON
ENABLE_LYNXRC:visited_links:ON

Default value

ENABLE_LYNXRC:assume_charset:ON
ENABLE_LYNXRC:force_cookie_prompt:ON
ENABLE_LYNXRC:force_ssl_prompt:ON
ENABLE_LYNXRC:make_links_for_all_images:ON
ENABLE_LYNXRC:make_pseudo_alts_for_inlines:ON
ENABLE_LYNXRC:preferred_encoding:ON
ENABLE_LYNXRC:preferred_language:ON
ENABLE_LYNXRC:preferred_media_types:ON
ENABLE_LYNXRC:raw_mode:ON
ENABLE_LYNXRC:scrollbar:ON
ENABLE_LYNXRC:set_cookies:ON
ENABLE_LYNXRC:show_kb_rate:ON
ENABLE_LYNXRC:tagsoup:ON
ENABLE_LYNXRC:underline_links:ON
ENABLE_LYNXRC:auto_session:ON
ENABLE_LYNXRC:session_file:ON

`[PROGRAM]_PATH` - External Programs

Each BROKEN_FTP_RETR gives a string match for the reported FTP server version

Default value

BROKEN_FTP_RETR:ProFTPD 1.2.5
BROKEN_FTP_RETR:spftp/

`BROKEN_FTP_EPSV` - Internal Behavior

Description

Some ftp servers are known to have a broken implementation of EPSV. The server will hang for a long time when we attempt to connect after issuing this command. Workaround: do not use EPSV, just use PASV.

Each BROKEN_FTP_EPSV gives a string match for the reported FTP server version

Default value

BROKEN_FTP_EPSV:(Version wu-2.6.2-12)

INCLUDE - Auxiliary Facilities

Description

Example:

Example:

STARTFILE - Auxiliary Facilities

Description

Default value

Example:

Default value

HELPFILE - Auxiliary Facilities

Description

Default value

Example:

Default value

DEFAULT_INDEX_FILE - Auxiliary Facilities

Description

Default value

GOTOBUFFER - Interaction

Description

Default value

JUMP_PROMPT - Interaction

Description

Default value

JUMPFILE - Auxiliary Facilities

Description

Default value

Example:

Default value

JUMPBUFFER - Auxiliary Facilities

Description

Default value

SAVE_SPACE - Internal Behavior

Description

Default value

REUSE_TEMPFILES - Internal Behavior

Description

Default value

LYNX_HOST_NAME - Internal Behavior

Description

Default value

LOCALHOST_ALIAS - Internal Behavior

Description

Examples:

LOCAL_DOMAIN - Internal Behavior

Description

Default value

AUTO_SESSION - Session support

Description

Default value

SESSION_FILE - Session support

Description

Default value

SESSION_LIMIT - Session support

Description

Default value

CHARACTER_SET - Character sets

Description

Default value

LOCALE_CHARSET - Character sets

Description

Default value

ASSUME_CHARSET - Character sets

Description

Default value

ASSUMED_DOC_CHARSET_CHOICE - Character sets

Description

Example:

Examples:

Default value

DISPLAY_CHARSET_CHOICE - Character sets

Description

ASSUME_LOCAL_CHARSET - Character sets

Description

Default value

PREPEND_CHARSET_TO_SOURCE - Character sets

Description

Default value

NCR_IN_BOOKMARKS - Character sets

Description

Default value

`INCLUDE` - Auxiliary Facilities

`STARTFILE` - Auxiliary Facilities

`HELPFILE` - Auxiliary Facilities

`DEFAULT_INDEX_FILE` - Auxiliary Facilities

`GOTOBUFFER` - Interaction

`JUMP_PROMPT` - Interaction

`JUMPFILE` - Auxiliary Facilities

`JUMPBUFFER` - Auxiliary Facilities

`SAVE_SPACE` - Internal Behavior

`REUSE_TEMPFILES` - Internal Behavior

`LYNX_HOST_NAME` - Internal Behavior

`LOCALHOST_ALIAS` - Internal Behavior

`LOCAL_DOMAIN` - Internal Behavior

`AUTO_SESSION` - Session support

`SESSION_FILE` - Session support

`SESSION_LIMIT` - Session support

`CHARACTER_SET` - Character sets

`LOCALE_CHARSET` - Character sets

`ASSUME_CHARSET` - Character sets

`ASSUMED_DOC_CHARSET_CHOICE` - Character sets

`DISPLAY_CHARSET_CHOICE` - Character sets

`ASSUME_LOCAL_CHARSET` - Character sets

`PREPEND_CHARSET_TO_SOURCE` - Character sets

`NCR_IN_BOOKMARKS` - Character sets

`FORCE_8BIT_TOUPPER` - Character sets

`OUTGOING_MAIL_CHARSET` - Character sets

`ASSUME_UNREC_CHARSET` - Character sets

`PREFERRED_LANGUAGE` - Character sets

`PREFERRED_CHARSET` - Character sets

`CHARSETS_DIRECTORY` - Character sets

`CHARSET_SWITCH_RULES` - Character sets

`URL_DOMAIN_PREFIXES` - Interaction

`URL_DOMAIN_SUFFIXES` - Interaction

`FORMS_OPTIONS` - Interaction

`PARTIAL` - Interaction

`PARTIAL_THRES` - Interaction

`SHOW_KB_RATE` - Interaction

`SHOW_KB_NAME` - Interaction

`INFOSECS` - Timeouts

`MESSAGESECS` - Timeouts

`ALERTSECS` - Timeouts

`DEBUGSECS` - Timeouts

`REPLAYSECS` - Timeouts

`USE_SELECT_POPUPS` - Appearance

`SHOW_CURSOR` - Appearance

`UNDERLINE_LINKS` - Appearance

`BOLD_HEADERS` - Appearance

`BOLD_H1` - Appearance

`BOLD_NAME_ANCHORS` - Appearance