Options are sorted by name. o 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

Support for this setting was disabled at compile-time.

VI_KEYS_ALWAYS_ON – Keyboard Input

Description

Vi or Emacs movement keys, i.e. familiar hjkl or ^N^P^F^B . These are defaults, which can be changed in the Options Menu or .lynxrc .

Default value

VI_KEYS_ALWAYS_ON:FALSE
EMACS_KEYS_ALWAYS_ON:FALSE

Support for this setting was disabled at compile-time.

WAIS_PROXY – Proxy

Description

Please see the description of HTTP_PROXY

Support for this setting was disabled at compile-time.

WAIT_VIEWER_TERMINATION – External Programs

Description

The WAIT_VIEWER_TERMINATION is used in the Windows environment to tell Lynx to wait until a viewer has terminated.

Default value

WAIT_VIEWER_TERMINATION:FALSE

Support for this setting was disabled at compile-time.

WITH_BACKSPACES – Dump/Crawl

Description

Emit backspaces in output if -dump'ing or -crawl'ing (like 'man' does).

Default value

WITH_BACKSPACES:FALSE

Support for this setting was disabled at compile-time.

XHTML_PARSING – HTML Parsing

Description

XHTML_PARSING - HTML parsing When true, tells lynx that it can ignore certain tags which have no content in an XHTML 1.0 document. For example <p /> <a /> When the option is false, lynx will not treat the tag as an ending.

Default value

XHTML_PARSING:FALSE

Support for this setting was disabled at compile-time.

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 were 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


Unix:
XLOADIMAGE_COMMAND will be used as a default in src/HTInit.c for viewing image content types when the DISPLAY environment variable is set. Make it the full path and name of the xli (also know as xloadimage or xview) command, or other image viewer. It can be anything that will handle GIF, TIFF and other popular image formats (xli does). The freeware distribution of xli is available in the ftp://ftp.x.org/contrib subdirectory. The shareware, xv, also is suitable. You must also have a "%s" for the filename; "&" for background is optional. 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 don't want to disable the built-in default viewer mappings for image types. Note that open is used as the default for NeXT, instead of the XLOADIMAGE_COMMAND definition. If you use xli, you may want to add the -quiet flag.

Default value

XLOADIMAGE_COMMAND:xli %s &

Support for this setting was disabled at compile-time.

ZCAT_PATH – External Programs

Description

This is the path used for DIRED mode to decompress files, writing the result to a pipe as part of a shell command, e.g., the program "zcat".

Support for this setting was disabled at compile-time.

ZIP_PATH – External Programs

Description

This is the path used for DIRED mode to create a zip-archive from one or more files, e.g., the program "unzip".

Support for this setting was disabled at compile-time.

Options are sorted by name.

ACCEPT_ALL_COOKIES – Cookies

Description

If ACCEPT_ALL_COOKIES is set TRUE, Lynx will accept cookies from all domains with no user interaction. This is equivalent to automatically replying to all cookie 'Allow?' prompts with "A"lways. Note that it does not preempt validity checking, which has to be controlled separately (see below). The default is defined in userdefs.h and can be overridden here, or in the .lynxrc file via an o(ptions) screen setting. It may also be toggled via the -accept_all_cookies command line switch.

Default value

ACCEPT_ALL_COOKIES:FALSE

ALERTSECS – Timeouts

Description

Please see the description of INFOSECS

ALT_BLAT_MAIL – Mail-related

Description

BLAT_MAIL is used in the Win32 port. It tells Lynx whether to use the "blat" mailer, or the "blatj" utility. This feature can also be set/reset via the command-line "-altblat" option.

Some users prefer blatj, which can handle Japanese characters. It is available from

http://www.piedey.co.jp/blatj/

(caution - the page is in Japanese).

See also BLAT_MAIL and SYSTEM_MAIL flags.

Default value

ALT_BLAT_MAIL:FALSE

Support for this setting was disabled at compile-time.

ALWAYS_RESUBMIT_POSTS – Internal Behavior

Description

If ALWAYS_RESUBMIT_POSTS is set TRUE, Lynx always will resubmit forms with method POST, dumping any cache from a previous submission of the form, including when the document returned by that form is sought with the PREV_DOC command or via the history list. Lynx always resubmits forms with method POST when a submit button or a submitting text input is activated, but normally retrieves the previously returned document if it had links which you activated, and then go back with the PREV_DOC command or via the history list.

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

Default value

ALWAYS_RESUBMIT_POSTS:FALSE

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

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

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:*

Support for this setting was disabled at compile-time.

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

ASSUME_LOCAL_CHARSET – Character Sets

Description

ASSUME_LOCAL_CHARSET is like ASSUME_CHARSET but only applies to local files. If no setting is given here or by an -assume_local_charset command line option, the value for ASSUME_CHARSET or -assume_charset is used. It works for both text/plain and text/html files. This option will ignore "raw mode" toggling when local files are viewed (it is "stronger" than "assume_charset" or the effective change of the charset assumption caused by changing "raw mode"), so only use when necessary.

Default value

ASSUME_LOCAL_CHARSET:iso-8859-1

ASSUME_UNREC_CHARSET – Character Sets

Description

If Lynx encounters a charset parameter it doesn't recognize, it will replace the value given by ASSUME_UNREC_CHARSET (or a corresponding -assume_unrec_charset command line option) for it. This can be used to deal with charsets unknown to Lynx, if they are "sufficiently similar" to one that Lynx does know about, by forcing the same treatment. There is no default, and you probably should leave this undefined unless necessary.

Default value

ASSUME_UNREC_CHARSET:iso-8859-1

AUTO_SESSION – Session support

Description

If AUTO_SESSION is TRUE lynx will save/restore useful information about your browsing history when closing/starting current lynx session if no command-line session switches override this setting. This setting is useful only if SESSION_FILE is defined here or in the user's .lynxrc file.

Default value

AUTO_SESSION:FALSE

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

BIBP_BIBHOST – Bibliographic Protocol (bibp scheme)

Description

BIBP_BIBHOST is the URL at which local bibp service may be found, if it exists. Defaults to http://bibhost/ for protocol conformance, but may be overridden here or via -bibhost parameter.

Default value

BIBP_BIBHOST:http://bibhost/

BIBP_GLOBAL_SERVER – Bibliographic Protocol (bibp scheme)

Description

BIBP_GLOBAL_SERVER is the default global server for bibp: links, used when a local bibhost or document-specified citehost is unavailable. Set in userdefs.h and can be changed here.

Default value

BIBP_GLOBAL_SERVER:http://usin.org/

Support for this setting was disabled at compile-time.

BLAT_MAIL – Mail-related

Description

BLAT_MAIL is used in the Win32 port. It tells Lynx whether to use the "blat" mailer, or the "sendmail" utility. Normally the "blat" mailer is used for Win32, because the sendmail look-alikes have fewer features. This feature can also be set/reset via the command-line "-noblat" option.

Blat is available from

http://www.blat.net

See also ALT_BLAT_MAIL and SYSTEM_MAIL flags.

Default value

BLAT_MAIL:TRUE

Support for this setting was disabled at compile-time.

BLOCK_MULTI_BOOKMARKS – Auxiliary Facilities

Description

If BLOCK_MULTI_BOOKMARKS is set TRUE, multiple bookmark support will be forced off, and cannot to toggled on via the "o"ptions menu. The compilation setting is normally FALSE, and can be overridden here. It can also be set via the -restrictions=multibook or the -anonymous or -validate command line switches.

Default value

BLOCK_MULTI_BOOKMARKS:FALSE

BOLD_H1 – Appearance

Description

If BOLD_H1 is set to TRUE the HT_BOLD default style will be acted upon for <H1> headers even if BOLD_HEADERS is FALSE. The compilation default is FALSE. On Unix, compilation with -DUNDERLINE_LINKS also will apply to the HT_BOLD style for headers when BOLD_H1 is TRUE.

Default value

BOLD_H1:FALSE

BOLD_HEADERS – Appearance

Description

If BOLD_HEADERS is set to TRUE the HT_BOLD default style will be acted upon for <H1> through <H6> headers. The compilation default is FALSE (only the indentation styles are acted upon, but see BOLD_H1, below). On Unix, compilation with -DUNDERLINE_LINKS also will apply to the HT_BOLD style for headers when BOLD_HEADERS is TRUE.

Default value

BOLD_HEADERS:FALSE

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

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)

BROKEN_FTP_RETR – Internal Behavior

Description

Some ftp servers are known to have a broken implementation of RETR. If asked to retrieve a directory, they get confused and fails subsequent commands such as CWD and LIST. Workaround: reconnect after a failed RETR, which is slow.

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/

BZIP2_PATH – External Programs

Description

This is the path used for DIRED mode and web connections to compress a file to ".bz2", e.g., the Unix command "bzip2".

CASE_SENSITIVE_ALWAYS_ON – Keyboard Input

Description

The default search type. This is a default that can be overridden by the user!

Default value

CASE_SENSITIVE_ALWAYS_ON:FALSE

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://tools.ietf.org/html/rfc1345

Default value

CHARACTER_SET:iso-8859-1

CHARSETS_DIRECTORY – Character Sets

Description

CHARSETS_DIRECTORY specifies the directory with the fonts (glyph data) used by Lynx to switch the display-font to a font best suited for the given document. The font should be in a format understood by the platforms TTY-display-font-switching API. Currently supported on OS/2 only.

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

Support for this setting was disabled at compile-time.

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

Support for this setting was disabled at compile-time.

CHECKMAIL – Internal Behavior

Description

If CHECKMAIL is set to TRUE, the user will be informed (via a statusline message) about the existence of any unread mail at startup of Lynx, and will get statusline messages if subsequent new mail arrives. If a jumps file with a lynxprog URL for invoking mail is available, or your html pages include an mail launch file URL, the user thereby can access mail and read the messages. The checks and statusline reports will not be performed if Lynx has been invoked with the -restrictions=mail switch.


VMS USERS !!!
New mail is normally broadcast as it arrives, via "unsolicited screen broadcasts", which can be "wiped" from the Lynx display via the Ctrl-W command. You may prefer to disable the broadcasts and use CHECKMAIL instead (e.g., in a public account which will be used by people who are ignorant about VMS).

Default value

CHECKMAIL:FALSE

CHMOD_PATH – External Programs

Description

This is the path used for DIRED mode to change file protection, e.g., the Unix command "chmod".

Setting this to an empty string will let lynx use a built-in version.

COLLAPSE_BR_TAGS – HTML Parsing

Description

If COLLAPSE_BR_TAGS is set FALSE, Lynx will not collapse serial BR tags. If set TRUE, two or more concurrent BRs will be collapsed into a single line break. Note that the valid way to insert extra blank lines in HTML is via a PRE block with only newlines in the block.

Default value

COLLAPSE_BR_TAGS:TRUE

COLOR – Appearance

Description

COLORS are only available if compiled with SVr4 curses or slang. This is the old color configuration. The COLOR_STYLE configuration is compiled-in and can simulate this if the ".lss" filename is empty.

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 first compiled-in value (which as noted, may be empty).

At startup, lynx remembers the name of the color-style file which was used, and together with each file specified, provides those as choices in the O)ptions menu.

Default value

COLOR_STYLE: lynx.lss
COLOR_STYLE: blue-background.lss
COLOR_STYLE: bright-blue.lss
COLOR_STYLE: midnight.lss
COLOR_STYLE: mild-colors.lss
COLOR_STYLE: opaque.lss

COMPRESS_PATH – External Programs

Description

This is the path used for DIRED mode and web connections to compress a file to ".Z", e.g., the Unix command "compress".

CONNECT_TIMEOUT – Timeouts

Description

Specifies (in seconds) connect timeout. Default value is rather huge.

Default value

CONNECT_TIMEOUT:18000

CONV_JISX0201KANA – Character Sets

Description

If CONV_JISX0201KANA is set, Lynx will convert JIS X0201 Kana to JIS X0208 Kana, i.e., convert half-width kana to full-width.

Default value

CONV_JISX0201KANA:TRUE

COOKIE_ACCEPT_DOMAINS – Cookies

Description

COOKIE_ACCEPT_DOMAINS and COOKIE_REJECT_DOMAINS are comma-delimited lists of domains from which Lynx should automatically accept or reject cookies without asking for confirmation. If the same domain is specified in both lists, rejection will take precedence. 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.

Default value

COOKIE_ACCEPT_DOMAINS:none
COOKIE_REJECT_DOMAINS:none

COOKIE_FILE – Cookies

Description

COOKIE_FILE is the default file from which persistent cookies are read at startup (if the file exists), if Lynx was compiled with USE_PERSISTENT_COOKIES and the PERSISTENT_COOKIES option is enabled. The cookie file can also be specified in .lynxrc or on the command line.

Default value

COOKIE_FILE:~/.lynx_cookies

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 RFC 2109 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_QUERY_INVALID_DOMAINS – Cookies

Description

Please see the description of COOKIE_LOOSE_INVALID_DOMAINS

COOKIE_REJECT_DOMAINS – Cookies

Description

Please see the description of COOKIE_ACCEPT_DOMAINS

COOKIE_SAVE_FILE – Cookies

Description

COOKIE_SAVE_FILE is the default file in which persistent cookies are stored at exit, if Lynx was compiled with USE_PERSISTENT_COOKIES and the PERSISTENT_COOKIES option is enabled. The cookie save file can also be specified on the command line.

With an interactive Lynx session, COOKIE_SAVE_FILE will default to COOKIE_FILE if it is not set. With a non-interactive Lynx session (e.g., -dump), cookies will only be saved to file if COOKIE_SAVE_FILE is set.

Default value

COOKIE_SAVE_FILE:~/.lynx_cookies

COOKIE_STRICT_INVALID_DOMAINS – Cookies

Description

Please see the description of COOKIE_LOOSE_INVALID_DOMAINS

COOKIE_VERSION – Cookies

Description

Select the RFC cookie version using the RFC number. Most users will not need to change this, but because RFC 6265 makes incompatible changes versus the older RFCs, it is interesting to compare behavior.

For reference:

http://tools.ietf.org/html/rfc6265

http://tools.ietf.org/html/rfc2965

http://tools.ietf.org/html/rfc2109

Default value

COOKIE_VERSION:RFC-6265

COPY_PATH – External Programs

Description

This is the path used for DIRED mode to copy a file, e.g., the Unix command "cp".

Setting this to an empty string will let lynx use a built-in version.

CSO_PROXY – Proxy

Description

Please see the description of HTTP_PROXY

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 were 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

Support for this setting was disabled at compile-time.

DEBUGSECS – Timeouts

Description

Set DEBUGSECS to a nonzero value to slow down progress messages (see "-delay" option).

Default value

DEBUGSECS:0

Support for this setting was disabled at compile-time.

DEFAULT_BOOKMARK_FILE – Auxiliary Facilities

Description

DEFAULT_BOOKMARK_FILE is the filename used for storing personal bookmarks. It will be prepended by the user's home directory. NOTE that a file ending in .html or other suffix mapped to text/html should be used to ensure its treatment as HTML. The built-in default is lynx_bookmarks.html. On both Unix and VMS, if a subdirectory off of the HOME directory is desired, the path should begin with "./" (e.g., ./BM/lynx_bookmarks.html), but the subdirectory must already exist. Lynx will create the bookmark file, if it does not already exist, on the first ADD_BOOKMARK attempt if the HOME directory is indicated (i.e., if the definition is just filename.html without any slashes), but requires a pre-existing subdirectory to create the file there. The user can re-define the default bookmark file, as well as a set of sub-bookmark files if multiple bookmark file support is enabled (see below), via the "o"ptions menu, and can save those definitions in the .lynxrc file.

Default value

DEFAULT_BOOKMARK_FILE:lynx_bookmarks.html

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_COLORS – 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.

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

DEFAULT_EDITOR – External Programs

Description

If DEFAULT_EDITOR is defined, users may edit local documents with it & it will also be used for sending mail messages. If no editor is defined here or by the user, the user will not be able to edit local documents and a primitive line-oriented mail-input mode will be used.

For sysadmins: do not define a default editor unless you know EVERY user will know how to use it; users can easily define their own editor in the Options Menu.

Default value

DEFAULT_EDITOR:none

DEFAULT_INDEX_FILE – Auxiliary Facilities

Description

DEFAULT_INDEX_FILE is the default file retrieved when the user presses the "I" key when viewing any document. An index to your CWIS can be placed here or a document containing pointers to lots of interesting places on the web.

Default value

DEFAULT_INDEX_FILE:http://scout.wisc.edu/

DEFAULT_KEYPAD_MODE – Keyboard Input

Description

DEFAULT_KEYPAD_MODE may be set to NUMBERS_AS_ARROWS or LINKS_ARE_NOT_NUMBERED (the same) or LINKS_ARE_NUMBERED or LINKS_AND_FIELDS_ARE_NUMBERED or FIELDS_ARE_NUMBERED to specify whether numbers (e.g. [10]) appear next to all links, allowing immediate access by entering the number on the keyboard, or numbers on the numeric key-pad work like arrows; the "FIELDS" options cause form fields also to be numbered. This may be overridden by the keypad_mode setting in .lynxrc, and can also be changed via the Options Menu.

Default value

DEFAULT_KEYPAD_MODE:NUMBERS_AS_ARROWS

DEFAULT_KEYPAD_MODE_IS_NUMBERS_AS_ARROWS – Keyboard Input

Description

Obsolete form of DEFAULT_KEYPAD_MODE, numbers work like arrows or numbered links. Set to TRUE, indicates numbers act as arrows, and set to FALSE indicates numbers refer to numbered links on the page. LINKS_AND_FIELDS_ARE_NUMBERED cannot be set by this option because it allows only two values (true and false).

Default value

DEFAULT_KEYPAD_MODE_IS_NUMBERS_AS_ARROWS:TRUE

DEFAULT_USER_MODE – Interaction

Description

DEFAULT_USER_MODE sets the default user mode for Lynx users. NOVICE shows a three line help message at the bottom of the screen. INTERMEDIATE shows normal amount of help (one line). ADVANCED help is replaced by the URL of the current link.

Default value

DEFAULT_USER_MODE:NOVICE

DEFAULT_VIRTUAL_MEMORY_SIZE – Internal Behavior

Description

Please see the description of DEFAULT_CACHE_SIZE

Support for this setting was disabled at compile-time.

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

Default value

DIRED_MENU:::New File:(in current directory):LYNXDIRED://NEW_FILE%d
DIRED_MENU:::New Directory:(in current directory):LYNXDIRED://NEW_FOLDER%d

Following depends on OK_INSTALL

Default value

DIRED_MENU:FILE::Install:selected file to new location:LYNXDIRED://INSTALL_SRC%p
DIRED_MENU:DIR::Install:selected directory to new location:LYNXDIRED://INSTALL_SRC%p

Default value

DIRED_MENU:FILE::Modify File Name:(of current selection):LYNXDIRED://MODIFY_NAME%p
DIRED_MENU:DIR::Modify Directory Name:(of current selection):LYNXDIRED://MODIFY_NAME%p
DIRED_MENU:LINK::Modify Name:(of selected symbolic link):LYNXDIRED://MODIFY_NAME%p

Following depends on OK_PERMIT

Default value

DIRED_MENU:FILE::Modify File Permissions:(of current selection):LYNXDIRED://PERMIT_SRC%p
DIRED_MENU:DIR::Modify Directory Permissions:(of current selection):LYNXDIRED://PERMIT_SRC%p

Default value

DIRED_MENU:FILE::Change Location:(of selected file):LYNXDIRED://MODIFY_LOCATION%p
DIRED_MENU:DIR::Change Location:(of selected directory):LYNXDIRED://MODIFY_LOCATION%p
DIRED_MENU:LINK::Change Location:(of selected symbolic link):LYNXDIRED://MODIFY_LOCATION%p
DIRED_MENU:FILE::Remove File:(current selection):LYNXDIRED://REMOVE_SINGLE%p
DIRED_MENU:DIR::Remove Directory:(current selection):LYNXDIRED://REMOVE_SINGLE%p
DIRED_MENU:LINK::Remove Symbolic Link:(current selection):LYNXDIRED://REMOVE_SINGLE%p

Following depends on OK_UUDECODE and !ARCHIVE_ONLY

Default value

DIRED_MENU:FILE::UUDecode:(current selection):LYNXDIRED://UUDECODE%p

Following depends on OK_TAR and !ARCHIVE_ONLY

Default value

DIRED_MENU:FILE:.tar.Z:Expand:(current selection):LYNXDIRED://UNTAR_Z%p

Following depend on OK_TAR and OK_GZIP and !ARCHIVE_ONLY

Default value

DIRED_MENU:FILE:.tar.gz:Expand:(current selection):LYNXDIRED://UNTAR_GZ%p
DIRED_MENU:FILE:.tgz:Expand:(current selection):LYNXDIRED://UNTAR_GZ%p

Following depends on !ARCHIVE_ONLY

Default value

DIRED_MENU:FILE:.Z:Uncompress:(current selection):LYNXDIRED://DECOMPRESS%p

Following depends on OK_GZIP and !ARCHIVE_ONLY

Default value

DIRED_MENU:FILE:.gz:Uncompress:(current selection):LYNXDIRED://UNGZIP%p

Following depends on OK_ZIP and !ARCHIVE_ONLY

Default value

DIRED_MENU:FILE:.zip:Uncompress:(current selection):LYNXDIRED://UNZIP%p

Following depends on OK_TAR and !ARCHIVE_ONLY

Default value

DIRED_MENU:FILE:.tar:UnTar:(current selection):LYNXDIRED://UNTAR%p

Following depends on OK_TAR

Default value

DIRED_MENU:DIR::Tar:(current selection):LYNXDIRED://TAR%p

Following depends on OK_TAR and OK_GZIP

Default value

DIRED_MENU:DIR::Tar and compress:(using GNU gzip):LYNXDIRED://TAR_GZ%p

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

Following depends on OK_GZIP

Default value

DIRED_MENU:FILE::Compress:(using gzip):LYNXDIRED://GZIP%p

Following depends on OK_ZIP

Default value

DIRED_MENU:FILE::Compress:(using zip):LYNXDIRED://ZIP%p

Default value

DIRED_MENU:TAG::Move all tagged items to another location.::LYNXDIRED://MOVE_TAGGED%d

Following depends on OK_INSTALL

Default value

DIRED_MENU:TAG::Install tagged files into another directory.::LYNXDIRED://INSTALL_SRC%00

Default value

DIRED_MENU:TAG::Remove all tagged files and directories.::LYNXDIRED://REMOVE_TAGGED
DIRED_MENU:TAG::Untag all tagged items.::LYNXDIRED://CLEAR_TAGGED

DISPLAY_CHARSET_CHOICE – Character Sets

Description

Please see the description of ASSUMED_DOC_CHARSET_CHOICE

Support for this setting was disabled at compile-time.

DONT_WRAP_PRE – HTML Parsing

Description

Inhibit wrapping of text when -dump'ing and -crawl'ing, mark wrapped lines of <pre> in interactive session.

Default value

DONT_WRAP_PRE:FALSE

DOWNLOADER – External Programs

Description

Please see the description of PRINTER

EMACS_KEYS_ALWAYS_ON – Keyboard Input

Description

Please see the description of VI_KEYS_ALWAYS_ON

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:COLLAPSE_BR_TAGS: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_DOMAIN: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:HTML5_CHARSETS:OFF
ENABLE_LYNXRC:HTTP_PROTOCOL:1.0
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:NO_PAUSE:OFF
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_LOCAL:ON
ENABLE_LYNXRC:SCROLLBAR:OFF
ENABLE_LYNXRC:SELECT_POPUPS:ON
ENABLE_LYNXRC:SEND_USERAGENT:OFF
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

ENABLE_SCROLLBACK – Appearance

Description

If ENABLE_SCROLLBACK is TRUE, Lynx will clear the entire screen before displaying each new screenful of text. Though less efficient for normal use, this allows programs that maintain a buffer of previously-displayed text to recognize the continuity of what has been displayed, so that previous screenfuls can be reviewed by whatever method the program uses to scroll back through previous text. For example, the PC comm program QModem has a key that can be pressed to scroll back; if ENABLE_SCROLLBACK is TRUE, pressing the scrollback key will access previous screenfuls which will have been stored on the local PC and will therefore be displayed instantaneously, instead of needing to be retransmitted by Lynx at the speed of the comm connection (but Lynx will not know about the change, so you must restore the last screen before resuming with Lynx commands).

The default compilation or configuration setting can be toggled via an "-enable_scrollback" command line switch.

Default value

ENABLE_SCROLLBACK:FALSE

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_MENU – External Programs

Description

Like EXTERNAL, but allows customizing the menu name. Here is the syntax:

Example:

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

FINGER_PROXY – Proxy

Description

Please see the description of HTTP_PROXY

FORCE_8BIT_TOUPPER – Character Sets

Description

FORCE_8BIT_TOUPPER overrides locale settings and uses internal 8-bit case-conversion mechanism for case-insensitive searches in non-ASCII display character sets. It is FALSE by default and should not be changed unless you encounter problems with case-insensitive searches.

Default value

FORCE_8BIT_TOUPPER:FALSE

FORCE_COOKIE_PROMPT – Interaction

Description

If FORCE_COOKIE_PROMPT is set to "yes", then questionable conditions, such as cookies with invalid syntax will be ignored. If set to "no", these will be reported, but not attempted. The default "prompt" permits the user to make this choice on a case-by-case basis.

Default value

FORCE_COOKIE_PROMPT:PROMPT

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_HTML – HTML Parsing

Description

When true, this forces the first document specified on the command-line to be interpreted as HTML.

Default value

FORCE_HTML:FALSE

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_PROMPT – Interaction

Description

If FORCE_SSL_PROMPT is set to "yes", then questionable conditions, such as self-signed certificates will be ignored. If set to "no", these will be reported, but not attempted. The default "prompt" permits the user to make this choice on a case-by-case basis.

Default value

FORCE_SSL_PROMPT:PROMPT

FORMS_OPTIONS – Interaction

Description

Toggle whether the Options Menu is key-based or form-based; the key-based version is available only if specified at compile time.

Default value

FORMS_OPTIONS:TRUE

FTP_FORMAT – Appearance

Description

FTP_FORMAT defines the display for remote files. It uses the same "%" codes as LIST_FORMAT.

Default value

FTP_FORMAT:%d %-16.16t %a %K

FTP_PASSIVE – Internal Behavior

Description

Set FTP_PASSIVE to TRUE if you want to use passive mode ftp transfers. You might have to do this if you're behind a restrictive firewall.

Default value

FTP_PASSIVE:TRUE

FTP_PROXY – Proxy

Description

Please see the description of HTTP_PROXY

GLOBAL_EXTENSION_MAP – External Programs

Description

The global and personal EXTENSION_MAP files allow you to assign extensions to MIME types which will override any of the suffix maps in this (lynx.cfg) configuration file, or in src/HTInit.c. See the example mime.types file in the samples subdirectory.


Unix:

Default value

GLOBAL_EXTENSION_MAP:/etc/mime.types

VMS:

Default value

GLOBAL_EXTENSION_MAP:Lynx_Dir:mime.types

Unix (sought in user's home directory):

Default value

PERSONAL_EXTENSION_MAP:.mime.types
VMS (sought in user's sys$login directory):

Default value

PERSONAL_EXTENSION_MAP:mime.types

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://tools.ietf.org/html/rfc1524

and the example mailcap file in the samples subdirectory.


Unix:

Default value

GLOBAL_MAILCAP:/etc/mailcap

VMS:

Default value

GLOBAL_MAILCAP:Lynx_Dir:mailcap

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

Default value

PERSONAL_MAILCAP:.mailcap

GOPHER_PROXY – Proxy

Description

Please see the description of HTTP_PROXY

GOTOBUFFER – Interaction

Description

Set GOTOBUFFER to TRUE if you want to have the previous goto URL, if any, offered for reuse or editing when using the "g"oto command. The default is defined in userdefs.h. If left FALSE, the circular buffer of previously entered goto URLs can still be invoked via the Up-Arrow or Down-Arrow keys after entering the "g"oto command.

Default value

GOTOBUFFER:FALSE

GUESS_SCHEME – Internal Behavior

Description

When true, Lynx may fill in a missing "scheme" for URIs which you provide. This is different from URL_DOMAIN_PREFIXES and URL_DOMAIN_SUFFIXES.

If no "scheme" (such as "http:", "ftp:") is given in a URI, Lynx first checks if there is a corresponding local file which can be accessed directly. Failing that, Lynx may inspect the URI to see if it begins with a prefix which implies a scheme.

Lynx uses these schemes for the corresponding prefixes:

cso: "cso." "ns." "ph." ftp: "ftp." gopher: "gopher." http: "www". news: "news." nntp: "nntp." wais: "wais."

The default value FALSE disables this guess, telling Lynx to just assume that "http:" was intended.

Default value

GUESS_SCHEME:FALSE

GZIP_PATH – External Programs

Description

This is the path used for DIRED mode and web connections to compress a file to ".gz", e.g., the Unix command "gzip".

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.gz 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:

https://lynx.invisible-island.net/lynx_help/lynx_help_main.html.gz

This should be changed to the local path. This definition will be overridden if the "LYNX_HELPFILE" environment variable has been set.

Default value

HELPFILE:https://lynx.invisible-island.net/lynx_help/lynx_help_main.html.gz

Example:

#HELPFILE:file://localhost/PATH_TO/lynx_help/lynx_help_main.html.gz

Default value

HELPFILE:file://localhost/usr/share/doc/lynx-common/lynx_help/lynx_help_main.html.gz

HIDDENLINKS – HTML Parsing

Description

Control the display of hidden links, using one of the following names:

MERGE hidden links show up as bracketed numbers and are numbered together with other links in the sequence of their occurrence in the document.

LISTONLY hidden links are shown only on L)ist screens and listings generated by -dump or from the P)rint menu, but appear separately at the end of those lists. This is the default behavior.

IGNORE hidden links do not appear even in listings.

Default value

HIDDENLINKS:LISTONLY

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

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

HTML5_CHARSETS – Character Sets

Description

HTML5_CHARSETS is an alternative to ASSUME_CHARSET and ASSUME_LOCAL_CHARSET. Those assume by default that the character set of an HTML document is (as is standard in HTML4) ISO-8859-1, in the absence of locale information.

HTML5 introduces a "compatibility" (sic) feature which assumes that the default is Windows 1252. In the same way, it equates ISO-8859-4 and Windows 1254. Finally, it also makes recommendations which selectively reinterpret the locale encoding.

This option currently implements only the equating of ISO-8859-1 and Windows 1252.

Default value

HTML5_CHARSETS:FALSE

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_TAGNAME_XFORM – Appearance

Description

Please see the description of HTMLSRC_ATTRNAME_XFORM

HTTPS_PROXY – Proxy

Description

Please see the description of HTTP_PROXY

HTTP_PROTOCOL – Internal Behavior

Description

Normally Lynx negotiates HTTP/1.0, because it does not support chunked transfer (a requirement for all HTTP/1.1 clients), although it supports several other features of HTTP/1.1. You may encounter a server which does not support HTTP/1.0 which can be used by switching to the later protocol.

Default value

HTTP_PROTOCOL:1.0

HTTP_PROXY – Proxy

Description

Lynx version 2.2 and beyond supports the use of proxy servers that can act as firewall gateways and caching servers. They are preferable to the older gateway servers. Each protocol used by Lynx can be mapped separately using PROTOCOL_proxy environment variables (see Lynx Users Guide). If you have not set them externally, you can set them at run time via this configuration file. They will not override external settings. The no_proxy variable can be used to inhibit proxying to selected regions of the Web (see below). Note that on VMS these proxy variables are set as process logicals rather than symbols, to preserve lowercasing, and will outlive the Lynx image.

Examples:

http_proxy:http://some.server.dom:port/

https_proxy:http://some.server.dom:port/

ftp_proxy:http://some.server.dom:port/

gopher_proxy:http://some.server.dom:port/

news_proxy:http://some.server.dom:port/

newspost_proxy:http://some.server.dom:port/

newsreply_proxy:http://some.server.dom:port/

snews_proxy:http://some.server.dom:port/

snewspost_proxy:http://some.server.dom:port/

snewsreply_proxy:http://some.server.dom:port/

nntp_proxy:http://some.server.dom:port/

wais_proxy:http://some.server.dom:port/

finger_proxy:http://some.server.dom:port/

cso_proxy:http://some.server.dom:port/

no_proxy:host.domain.dom

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. If you omit the directory name, e.g.,

INCLUDE:lynx.cfg

then lynx first checks if it is in any of the directories listed in the environment variable LYNX_CFG_PATH, then tries the directory of the default config-file.

You can also 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.

INFLATE_PATH – External Programs

Description

This is the path used for web connections to compress a file using "inflate" compression.

INFOSECS – Timeouts

Description

The following definitions set the number of seconds for pauses following statusline messages that would otherwise be replaced immediately, and are more important than the unpaused progress messages. Those set by INFOSECS are also basically progress messages (e.g., that a prompted input has been canceled) and should have the shortest pause. Those set by MESSAGESECS are informational (e.g., that a function is disabled) and should have a pause of intermediate duration. Those set by ALERTSECS typically report a serious problem and should be paused long enough to read whenever they appear (typically unexpectedly). The default values are defined in userdefs.h, and can be modified here should longer pauses be desired for braille-based access to Lynx.

SVr4-curses implementations support time delays in milliseconds, hence the value may be given shorter, e.g., 0.5

Use the NO_PAUSE option (like the command-line -nopause) to override all of the delay times.

Default value

INFOSECS:1
MESSAGESECS:2
ALERTSECS:3
NO_PAUSE:FALSE

INSTALL_PATH – External Programs

Description

This is the path used for DIRED mode to install files, e.g., the Unix command "install".

JUMPBUFFER – Auxiliary Facilities

Description

Set JUMPBUFFER to TRUE if you want to have the previous jump target, if any, offered for reuse or editing when using the "J"ump command. The default is defined in userdefs.h. If left FALSE, the circular buffer of previously entered targets (shortcuts) can still be invoked via the Up-Arrow or Down-Arrow keys after entering the "J"ump command. If multiple jumps files are installed, the recalls of shortcuts will be specific to each file. If Lynx was built with PERMIT_GOTO_FROM_JUMP defined, any random URLs used instead of shortcuts will be stored in the goto URL buffer, not in the shortcuts buffer(s), and the single character ":" can be used as a target to invoke the goto URL buffer (as if "g"oto followed by Up-Arrow had been entered).

Default value

JUMPBUFFER:FALSE