MIME types and viewers! file extensions may be assigned to MIME types using the SUFFIX: definition. NOTE: It is normally preferable to define new extension mappings in EXTENSION_MAP files (see below) instead of here: Definitions here are overridden by those in EXTENSION_MAP files and even by some built-in defaults in src/HTInit.c. On the other hand, definitions here allow some more fields that are not possible in those files. Extension mappings have an effect mostly for ftp and local files, they are NOT used to determine the type of content for URLs with the http protocol. This is because HTTP servers already specify the MIME type in the Content-Type header. [It may still be necessary to set up an appropriate suffix for some MIME types, even if they are accessed only via the HTTP protocol, if the viewer (see below) for those MIME types requires a certain suffix for the temporary file passed to it.] These settings control the ability of Lynx to invoke various programs for the user. Any of the compiled-in pathnames of external programs can be overridden by specifying the corresponding xxx_PATH variable. If the variable is given as an empty string, lynx will not use the program. For a few cases, there are internal functions which can be used instead.

Here is a list of settings that belong to this category

HTML Parsing

Description

These settings control the way Lynx parses invalid HTML and how it may resolve such issues.

Here is a list of settings that belong to this category

Interaction

Description

These settings control interaction of the user with lynx.

Here is a list of settings that belong to this category

Internal Behavior

Description

These settings control internal lynx behavior - the way it interacts with the operating system and Internet. Modifying these settings will not change the rendition of documents that you browse with lynx, but can change various delays and resource utilization.

Here is a list of settings that belong to this category

Keyboard Input

Description

These settings control the way Lynx interprets user input.

Here is a list of settings that belong to this category

Support for all settings suffixed with '*' was disabled at compile time.