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.
ACCEPT_ALL_COOKIES:FALSE
The default defined here or in userdefs.h can be toggled via
the -resubmit_forms command line switch.
ALWAYS_RESUBMIT_POSTS:FALSE
If built with a library that recognizes default colors (usually ncurses or
slang), 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.
ASSUMED_COLOR:default:defaultASSUME_CHARSET:iso-8859-1ASSUME_LOCAL_CHARSET:iso-8859-1
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.
ASSUME_UNREC_CHARSET:iso-8859-1
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.
AUTO_UNCACHE_DIRLISTS:2BIBP_BIBHOST:http://bibhost/
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.
BLOCK_MULTI_BOOKMARKS:FALSE
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.
BOLD_H1:FALSE
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.
BOLD_HEADERS:FALSEBOLD_NAME_ANCHORS:FALSE
The default search type.
This is a default that can be overridden by the user!
CASE_SENSITIVE_ALWAYS_ON:FALSE
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 (cp775) cp775 Baltic Rim (windows-1257) windows-1257 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 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 .
CHARACTER_SET:iso-8859-1
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).
CHECKMAIL:FALSECOLLAPSE_BR_TAGS:TRUE
Specifies (in seconds) connect timeout. Default value is rather huge.
CONNECT_TIMEOUT:18000
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.
COOKIE_ACCEPT_DOMAINS:noneCOOKIE_REJECT_DOMAINS:none
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.
COOKIE_FILE:~/.lynx_cookies
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.
COOKIE_LOOSE_INVALID_DOMAINS:noneCOOKIE_STRICT_INVALID_DOMAINS:noneCOOKIE_QUERY_INVALID_DOMAINS:none
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.
COOKIE_SAVE_FILE:~/.lynx_cookies
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_BOOKMARK_FILE:lynx_bookmarks.html
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_CACHE_SIZE:10DEFAULT_VIRTUAL_MEMORY_SIZE:512000
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_EDITOR:none
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_INDEX_FILE:http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.htmlDEFAULT_KEYPAD_MODE:NUMBERS_AS_ARROWSDEFAULT_KEYPAD_MODE_IS_NUMBERS_AS_ARROWS:TRUE
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_USER_MODE:NOVICE
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
DIRED_MENU:::New File:(in current directory):LYNXDIRED://NEW_FILE%dDIRED_MENU:::New Directory:(in current directory):LYNXDIRED://NEW_FOLDER%dNote that a few settings (Cookies and Show images) are comprised of more than one lynx.cfg setting.
ENABLE_LYNXRC:accept_all_cookies:ONENABLE_LYNXRC:assume_charset:OFFENABLE_LYNXRC:bookmark_file:ONENABLE_LYNXRC:case_sensitive_searching:ONENABLE_LYNXRC:character_set:ONENABLE_LYNXRC:cookie_accept_domains:ONENABLE_LYNXRC:cookie_file:ONENABLE_LYNXRC:cookie_loose_invalid_domains:ONENABLE_LYNXRC:cookie_query_invalid_domains:ONENABLE_LYNXRC:cookie_reject_domains:ONENABLE_LYNXRC:cookie_strict_invalid_domains:ONENABLE_LYNXRC:dir_list_style:ONENABLE_LYNXRC:display:OFFENABLE_LYNXRC:emacs_keys:ONENABLE_LYNXRC:file_editor:ONENABLE_LYNXRC:file_sorting_method:ONENABLE_LYNXRC:force_cookie_prompt:OFFENABLE_LYNXRC:force_ssl_prompt:OFFENABLE_LYNXRC:kblayout:ONENABLE_LYNXRC:keypad_mode:ONENABLE_LYNXRC:lineedit_mode:ONENABLE_LYNXRC:locale_charset:ONENABLE_LYNXRC:make_links_for_all_images:OFFENABLE_LYNXRC:make_pseudo_alts_for_inlines:OFFENABLE_LYNXRC:multi_bookmark:ONENABLE_LYNXRC:personal_mail_address:ONENABLE_LYNXRC:preferred_charset:ONENABLE_LYNXRC:preferred_language:ONENABLE_LYNXRC:raw_mode:OFFENABLE_LYNXRC:run_all_execution_links:ONENABLE_LYNXRC:run_execution_links_on_local_files:ONENABLE_LYNXRC:scrollbar:OFFENABLE_LYNXRC:select_popups:ONENABLE_LYNXRC:set_cookies:OFFENABLE_LYNXRC:show_color:ONENABLE_LYNXRC:show_cursor:ONENABLE_LYNXRC:show_dotfiles:ONENABLE_LYNXRC:show_kb_rate:OFFENABLE_LYNXRC:sub_bookmarks:ONENABLE_LYNXRC:tagsoup:OFFENABLE_LYNXRC:underline_links:OFFENABLE_LYNXRC:user_mode:ONENABLE_LYNXRC:useragent:OFFENABLE_LYNXRC:verbose_images:ONENABLE_LYNXRC:vi_keys:ONENABLE_LYNXRC:visited_links:ON
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 compilation default is FALSE (if REVERSE_CLEAR_SCREEN_PROBLEM was not
defined in the Unix Makefile to invoke this behavior as a workaround for
some poor curses implementations).
The default compilation or configuration setting can be toggled via an
"-enable_scrollback" command line switch.
ENABLE_SCROLLBACK:FALSE
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.
FORCE_8BIT_TOUPPER:FALSE
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.
FORCE_COOKIE_PROMPT:PROMPTFORCE_EMPTY_HREFLESS_A:FALSE
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.
FORCE_SSL_COOKIES_SECURE:FALSE
Toggle whether the Options Menu is key-based or form-based;
the key-based version is available only if specified at compile time.
FORMS_OPTIONS:TRUEFTP_PASSIVE:TRUE
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:
GLOBAL_EXTENSION_MAP:/usr/local/lib/mosaic/mime.typesGLOBAL_EXTENSION_MAP:Lynx_Dir:mime.types
Unix (sought in user's home directory):
PERSONAL_EXTENSION_MAP:.mime.typesPERSONAL_EXTENSION_MAP:mime.types
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:
GLOBAL_MAILCAP:/usr/local/lib/mosaic/mailcapGLOBAL_MAILCAP:Lynx_Dir:mailcap
Sought in user's home (Unix) or sys$login (VMS) directory.
PERSONAL_MAILCAP:.mailcap
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.
GOTOBUFFER:FALSEHELPFILE:http://www.subir.com/lynx/lynx_help/lynx_help_main.htmlHELPFILE:file://localhost/PATH_TO/lynx_help/lynx_help_main.html
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.
HIDDEN_LINK_MARKER:none
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.
HISTORICAL_COMMENTS:FALSEHTMLSRC_TAGNAME_XFORM:2HTMLSRC_ATTRNAME_XFORM:2
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.
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
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:
INCLUDE:~/lynx.cfg for COLOR VIEWER KEYMAPINCLUDE:~/lynx.cfg:COLOR VIEWER KEYMAPIf 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.
SVr4-curses implementations support time delays in milliseconds,
hence the value may be given shorter, e.g., 0.5
INFOSECS:1MESSAGESECS:2ALERTSECS:3JUMPBUFFER:FALSE
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.
JUMPFILE:/FULL_LOCAL_PATH/jumps.htmlJUMPFILE:/Lynx_Dir/ips.html:i:IP or Interest group (? for list):
JUMP_PROMPT is the default statusline prompt for selecting a jumps file
shortcut. (see below).
You can change the prompt here from that defined in userdefs.h. Any
trailing white space will be trimmed, and a single space is added by Lynx
following the last non-white character. You must set the default prompt
before setting the default jumps file (below). If a default jumps file
was set via userdefs.h, and you change the prompt here, you must set the
default jumps file again (below) for the change to be implemented.
JUMP_PROMPT:Jump to (use "?" for list):none
JUSTIFY - Appearance
This option mirrors command-line option with same name. Default is TRUE. If
true, most of text (except headers and like this) will be justified. This
has no influence on CJK text rendering.
This option is only available if Lynx was compiled with EXP_JUSTIFY_ELTS.
JUSTIFY:TRUE
JUSTIFY_MAX_VOID_PERCENT - Appearance
This option controls the maximum allowed value for ratio (in percents) of
'the number of spaces to spread across the line to justify it' to
'max line size for current style and nesting' when justification is allowed.
When that ratio exceeds the value specified, that particular line won't be
justified. I.e. the value 28 for this setting will mean maximum value for
that ratio is 0.28.
JUSTIFY_MAX_VOID_PERCENT:35
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 redisplayKEYMAP:q:QUIT # Ask the user to quitKEYMAP:Q:ABORT # Quit without verificationKEYMAP:0x20:NEXT_PAGE # Move down to next pageKEYMAP:-:PREV_PAGE # Move up to previous pageKEYMAP:^P:UP_TWO # Move display up two linesKEYMAP:0x10C:UP_TWO # Function key Insert - Move display up two linesKEYMAP:^N:DOWN_TWO # Move display down two linesKEYMAP:0x10D:DOWN_TWO # Function key Remove - Move display down two linesKEYMAP:(:UP_HALF # Move display up half a pageKEYMAP:):DOWN_HALF # Move display down half a pageKEYMAP:^W:REFRESH # Refresh the screenKEYMAP:^A:HOME # Go to top of current documentKEYMAP:0x106:HOME # Keypad Home - Go to top of current documentKEYMAP:0x10A:HOME # Function key Find - Go to top of current documentKEYMAP:^E:END # Go to bottom of current documentKEYMAP:0x107:END # Keypad End - Go to bottom of current documentKEYMAP:0x10B:END # Function key Select - Go to bottom of current documentKEYMAP:0x100:PREV_LINK # Move to the previous link or pageKEYMAP:0x101:NEXT_LINK # Move to the next link or pageKEYMAP:0x10F:FASTBACKW_LINK # Back Tab - Move to previous link or text areaKEYMAP:^I:FASTFORW_LINK # Tab key - Move always to next link or text areaKEYMAP:^:FIRST_LINK # Move to the first link on lineKEYMAP:$:LAST_LINK # Move to the last link on lineKEYMAP:<:UP_LINK # Move to the link aboveKEYMAP:>:DOWN_LINK # Move to the link belowKEYMAP:0x7F:HISTORY # Show the history listKEYMAP:0x08:HISTORY # Show the history listKEYMAP:0x103:PREV_DOC # Return to the previous document in history stackKEYMAP:0x102:ACTIVATE # Select the current linkKEYMAP:0x109:ACTIVATE # Function key Do - Select the current linkKEYMAP:g:GOTO # Goto a random URLKEYMAP:G:ECGOTO # Edit the current document's URL and go to itKEYMAP:H:HELP # Show default help screenKEYMAP:0x108:DWIMHELP # Function key Help - Show a help screenKEYMAP: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 transmissionKEYMAP:m:MAIN_MENU # Return to the main menuKEYMAP:o:OPTIONS # Show the options menuKEYMAP:i:INDEX_SEARCH # Search a server based indexKEYMAP:/:WHEREIS # Find a string within the current documentKEYMAP:n:NEXT # Find next occurrence of string within documentKEYMAP:c:COMMENT # Comment to the author of the current documentKEYMAP:C:CHDIR # Change current directoryKEYMAP: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 itKEYMAP:=:INFO # Show info about current documentKEYMAP:p:PRINT # Show print optionsKEYMAP:a:ADD_BOOKMARK # Add current document to bookmark listKEYMAP:v:VIEW_BOOKMARK # View the bookmark listKEYMAP:V:VLINKS # List links visited during the current Lynx sessionKEYMAP:!:SHELL # Spawn default shellKEYMAP:d:DOWNLOAD # Download current linkKEYMAP:j:JUMP # Jump to a predefined targetKEYMAP:k:KEYMAP # Display the current key mapKEYMAP:l:LIST # List the references (links) in the current documentKEYMAP:#:TOOLBAR # Go to the Toolbar or Banner in the current documentKEYMAP:^T:TRACE_TOGGLE # Toggle detailed tracing for debuggingKEYMAP:;:TRACE_LOG # View trace log if available for the current sessionKEYMAP:*:IMAGE_TOGGLE # Toggle inclusion of links for all imagesKEYMAP:[:INLINE_TOGGLE # Toggle pseudo-ALTs for inlines with no ALT stringKEYMAP:]: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 pageKEYMAP:.: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 parsingKEYMAP:0x00:DO_NOTHING # Does nothing (ignore this key)KEYMAP:0x10E:DO_NOTHING # Does nothing (ignore this key)KEYMAP:{:SHIFT_LEFT # shift the screen leftKEYMAP:}:SHIFT_RIGHT # shift the screen rightKEYMAP:|:LINEWRAP_TOGGLE # toggle linewrap on/off, for shift-commandsKEYMAP:~:NESTED_TABLES # toggle nested-tables parsing on/off
KEYMAP:???:RIGHT_LINK # Move to the link to the rightKEYMAP:???:LEFT_LINK # Move to the link to the leftKEYMAP:???:LPOS_PREV_LINK # Like PREV_LINK, last column pos if form inputKEYMAP:???: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 contextKEYMAP:???: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 textareaKEYMAP:???:GROWTEXTAREA # Add some blank lines to bottom of textareaKEYMAP:???: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.
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
KEYMAP:^U:PREV_DOC:DIRED # Return to the previous documentKEYMAP:.:TAG_LINK:DIRED # Tag a file or directory for later actionKEYMAP:c:CREATE:DIRED # Create a new file or directoryKEYMAP:C:CHDIR:DIRED # change current directoryKEYMAP:f:DIRED_MENU:DIRED # Display a menu of file operationsKEYMAP:m:MODIFY:DIRED # Modify name or location of a file or directoryKEYMAP:r:REMOVE:DIRED # Remove files or directoriesKEYMAP:t:TAG_LINK:DIRED # Tag a file or directory for later actionKEYMAP: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: ignoreModify following key (prefixing only works within line-editing, edit actions of some resulting prefixed keys are built-in, see Line Editor help pages)
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 ExtensionMay 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 printableIf 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,
KEYMAP:0x10C:UP_TWO:PASS # Function key Insert - Move display up two lines
Other examples (repeating built-in bindings)
KEYMAP:^V::LKCMD # set (only) line-edit action for ^VKEYMAP:^V:SWITCH_DTD:LKCMD # set main lynxaction and line-edit action for ^VKEYMAP:^U::ERASE:1 # set line-edit binding for ^U, for default styleKEYMAP:^[::SETM2:3 # use escape key as modifier - works only sometimes
LEFTARROW_IN_TEXTFIELD_PROMPT
This option controls what happens when a Left Arrow key is pressed while
in the first position of an active text input field. By default, Lynx
asks for confirmation ("Do you want to go back to the previous document?")
only if the contents of the fields have been changed since entering it.
If set to TRUE, the confirmation prompt is always issued.
LEFTARROW_IN_TEXTFIELD_PROMPT:FALSE
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:
LIST_FORMAT: %a
If you want a brief output:
LIST_FORMAT: %4K %-12.12d %a
If you want the Unix "ls -l" format:
LIST_FORMAT: %p %4l %-8.8o %-8.8g %7s %-12.12d %a
If LIST_NEWS_DATES is set TRUE, Lynx will include the dates of articles in
news listings. The dates always are included in the articles, themselves.
The default is defined in userdefs.h, and can be overridden here.
LIST_NEWS_DATES:FALSE
If LIST_NEWS_NUMBERS is set TRUE, Lynx will use an ordered list and include
the numbers of articles in news listings, instead of using an unordered
list. The default is defined in userdefs.h, and can be overridden here.
LIST_NEWS_NUMBERS:FALSE
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.
This feature is experimental because 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.
LOCALE_CHARSET:FALSE
localhost aliases
Any LOCALHOST_ALIAS definitions also will be accepted as local when
the -localhost switch is set. These need not actually be local, i.e.,
in contrast to LYNX_HOST_NAME, you can define them to trusted hosts at
other Internet sites.
LOCALHOST_ALIAS:gopher.server.domainLOCALHOST_ALIAS:news.server.domain
LOCAL_DOMAIN is used for a tail match with the ut_host element of
the utmp or utmpx structure on systems with utmp capabilities, to
determine if a user is local to your campus or organization when
handling -restrictions=inside_foo or outside_foo settings for ftp,
news, telnet/tn3270 and rlogin URLs. An "inside" user is assumed
if your system does not have utmp capabilities. CHANGE THIS here
if it was not changed in userdefs.h at compilation time.
LOCAL_DOMAIN:ukans.edu
If LYNX_HOST_NAME is defined here or in userdefs.h, it will be
treated as an alias for the local host name in checks for URLs on
the local host (e.g., when the -localhost switch is set), and this
host name, "localhost", and HTHostName (the fully qualified domain
name of the system on which Lynx is running) will all be passed as
local. A different definition here will override that in userdefs.h.
LYNX_HOST_NAME:www.cc.ukans.edu
LYNX_SIG_FILE defines the name of a file containing a signature which
can be appended to email messages and news postings or followups. The
user will be prompted whether to append it. It is sought in the home
directory. If it is in a subdirectory, begin it with a dot-slash
(e.g., ./lynx/.lynxsig). The definition is set in userdefs.h and can
be changed here.
LYNX_SIG_FILE:.lynxsig
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.
MAIL_SYSTEM_ERROR_LOGGING:FALSE
If MAKE_LINKS_FOR_ALL_IMAGES is TRUE, all images will be given links
which can be ACTIVATEd. For inlines, the ALT or pseudo-ALT ("[INLINE]")
strings will be links for the resolved SRC rather than just text.
For ISMAP or other graphic links, ALT or pseudo-ALT ("[ISMAP]" or "[LINK]")
will have "-" and a link labeled "[IMAGE]" for the resolved SRC appended.
See also VERBOSE_IMAGES flag.
The definition here will override that in userdefs.h
and can be toggled via an "-image_links" command-line switch.
The user can also use the LYK_IMAGE_TOGGLE key (default `*')
or `Show Images' in the Form-based Options Menu.
MAKE_LINKS_FOR_ALL_IMAGES:FALSE
If MAKE_PSEUDO_ALTS_FOR_INLINES is FALSE, inline images which don't specify
an ALT string will not have "[INLINE]" inserted as a pseudo-ALT,
i.e. they'll be treated as having ALT="".
Otherwise (if TRUE), pseudo-ALTs will be created for inlines,
so that they can be used as links to the SRCs.
See also VERBOSE_IMAGES flag.
The definition here will override that in userdefs.h
and can be toggled via a "-pseudo_inlines" command-line switch.
The user can also use the LYK_INLINE_TOGGLE key (default `[')
or `Show Images' in the Form-based Options Menu.
MAKE_PSEUDO_ALTS_FOR_INLINES:TRUE
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.
MINIMAL_COMMENTS:TRUE
If MULTI_BOOKMARK_SUPPORT is set TRUE, and BLOCK_MULTI_BOOKMARKS (see
below) is FALSE, and sub-bookmarks exist, all bookmark operations will
first prompt the user to select an active sub-bookmark file or the
default bookmark file. FALSE is the default so that one (the default)
bookmark file will be available initially. The definition here will
override that in userdefs.h. The user can turn on multiple bookmark
support via the "o"ptions menu, and can save that choice as the startup
default via the .lynxrc file. When on, the setting can be STANDARD or
ADVANCED. If SUPPORT is set to the latter, and the user mode also is
ADVANCED, the VIEW_BOOKMARK command will invoke a statusline prompt at
which the user can enter the letter token (A - Z) of the desired bookmark,
or "=" to get a menu of available bookmark files. The menu always is
presented in NOVICE or INTERMEDIATE mode, or if the SUPPORT is set to
STANDARD. No prompting or menu display occurs if only one (the startup
default) bookmark file has been defined (define additional ones via the
"o"ptions menu). The startup default, however set, can be overridden on
the command line via the -restrictions=multibook or the -anonymous or
-validate switches.
MULTI_BOOKMARK_SUPPORT:FALSE
NCR_IN_BOOKMARKS:TRUE allows you to save 8-bit characters in bookmark titles
in the unicode format (NCR). This may be useful if you need to switch
display charsets frequently. This is the case when you use Lynx on different
platforms, e.g., on UNIX and from a remote PC, and want to keep the bookmarks
file persistent.
Another aspect is compatibility: NCR is part of I18N and HTML4.0
specifications supported starting with Lynx 2.7.2, Netscape 4.0 and MSIE 4.0.
Older browser versions will fail so keep NCR_IN_BOOKMARKS:FALSE if you
plan to use them.
NCR_IN_BOOKMARKS:FALSE
NEWS_CHUNK_SIZE and NEWS_MAX_CHUNK regulate the chunking of news article
listings with inclusion of links for listing earlier and/or later articles.
The defaults are defined in HTNews.c as 30 and 40, respectively. If the
news group contains more than NEWS_MAX_CHUNK articles, they will be listed
in NEWS_CHUNK_SIZE chunks. You can change the defaults here, and/or on
the command line via -newschunksize=NUMBER and/or -newsmaxchunk=NUMBER
switches. Note that if the chunk size is increased, here or on the command
line, to a value greater than the current maximum, the maximum will be
increased to that number. Conversely, if the maximum is set to a number
less than the current chunk size, the chunk size will be reduced to that
number. Thus, you need use only one of the two switches on the command
line, based on the direction of intended change relative to the compilation
or configuration defaults. The compilation defaults ensure that there will
be at least 10 earlier articles before bothering to chunk and create a link
for earlier articles.
NEWS_CHUNK_SIZE:30NEWS_MAX_CHUNK:40
Set NEWS_POSTING to FALSE if you do not want to support posting to
news groups via Lynx. If left TRUE, Lynx will use its news gateway to
post new messages or followups to news groups, using the URL schemes
described in the "Supported URLs" section of the online "h"elp. The
posts will be attempted via the nntp server specified in the URL, or
if none was specified, via the NNTPSERVER configuration or environment
variable. Links with these URLs for posting or sending followups are
created by the news gateway when reading group listings or articles
from nntp servers if the server indicates that it permits posting.
The compilation default set in userdefs.h can be changed here. If
the default is TRUE, posting can still be disallowed via the
-restrictions command line switch.
The posting facility in Lynx is quite limited. Lynx does not provide a
full featured news poster with elaborate error checking and safety features.
NEWS_POSTING:TRUE
To enable news reading ability via Lynx, the environment variable NNTPSERVER
must be set so that it points to your site's NNTP server
(see Lynx Users Guide on environment variables).
Lynx respects RFC 1738 (http://www.ics.uci.edu/pub/ietf/uri/rfc1738.txt)
and does not accept a host field in news URLs (use nntp: instead of news: for
the scheme if you wish to specify an NNTP host in a URL, as explained in the
RFC). If you have not set the variable externally, you can set it at run
time via this configuration file. It will not override an external setting.
Note that on VMS it is set as a process logical rather than symbol, and will
outlive the Lynx image.
The news reading facility in Lynx is quite limited. Lynx does not provide a
full featured news reader with elaborate error checking and safety features.
NNTPSERVER:news.server.dom
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.
NONRESTARTING_SIGWINCH:FALSENO_DOT_FILES:TRUE
If NO_FILE_REFERER is TRUE, Referer headers never will be sent in
transmissions to servers for links or actions derived from documents
or forms with file URLs. This ensures that paths associated with
the local file system are never indicated to servers, even if
NO_REFERER_HEADER is FALSE. If set to FALSE here, it can still be
set TRUE at run time via the -nofilereferer switch.
NO_FILE_REFERER:TRUE
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.
NO_FORCED_CORE_DUMP:FALSE
If NO_FROM_HEADER is set FALSE, From headers will be sent in transmissions
to http or https servers if the personal_mail_address has been defined via
the "o"ptions menu. The compilation default is TRUE (no From header is
sent) and the default can be changed here. The default can be toggled at
run time via the -from switch. Note that transmissions of From headers
have become widely considered to create an invasion of privacy risk.
NO_FROM_HEADER:TRUE
The compilation default, or default defined here, can be toggled via
the "-ismap" command line switch.
NO_ISMAP_IF_USEMAP:FALSEThe no_proxy variable can be a comma-separated list of strings defining no-proxy zones in the DNS domain name space. If a tail substring of the domain-path for a host matches one of these strings, transactions with that node will not be proxied.
no_proxy:domain.path1,path2A single asterisk as an entry will override all proxy variables and no transactions will be proxied.
no_proxy:*Warning: Note that setting 'il' as an entry in this list will block proxying for the .mil domain as well as the .il domain. If the entry is '.il' this will not happen.
If NO_REFERER_HEADER is TRUE, Referer headers never will be sent in
transmissions to servers. Lynx normally sends the URL of the document
from which the link was derived, but not for startfile URLs, "g"oto
URLs, "j"ump shortcuts, bookmark file links, history list links, or
URLs that include the content from form submissions with method GET.
If left FALSE here, it can be set TRUE at run time via the -noreferer
switch.
NO_REFERER_HEADER:FALSE
Denotes the position for link- and field-numbers (whether it is on the left
or right of the anchor). These are subject to DEFAULT_KEYPAD_MODE, which
determines whether numbers are shown.
NUMBER_LINKS_ON_LEFT:TRUENUMBER_FIELDS_ON_LEFT:TRUEOUTGOING_MAIL_CHARSET:nonePARTIAL:TRUEPARTIAL_THRES:-1
PERSISTENT_COOKIES indicates that cookies should be read at startup from
the COOKIE_FILE, and saved at exit for storage between Lynx sessions.
It is not used if Lynx was compiled without USE_PERSISTENT_COOKIES.
The default is FALSE, so that the feature needs to be enabled here
explicitly if you want it.
PERSISTENT_COOKIES:FALSE
PREFERRED_CHARSET specifies the character set in MIME notation (e.g.,
"ISO-8859-2", "ISO-8859-5") which Lynx will indicate you prefer in
requests to http servers using an Accept-Charsets header. Users can
change it via the "o"ptions menu and save that preference in their RC file.
The value should NOT include "ISO-8859-1" or "US-ASCII",
since those values are always assumed by default.
If a file in that character set is available, the server will send it.
If no Accept-Charset header is present, the default is that any
character set is acceptable. If an Accept-Charset header is present,
and if the server cannot send a response which is acceptable
according to the Accept-Charset header, then the server SHOULD send
an error response with the 406 (not acceptable) status code, though
the sending of an unacceptable response is also allowed. See RFC 2068
(http://www.ics.uci.edu/pub/ietf/uri/rfc2068.txt).
PREFERRED_CHARSET:none
PREFERRED_LANGUAGE is the language in MIME notation (e.g., "en",
"fr") which will be indicated by Lynx in its Accept-Language headers
as the preferred language. If available, the document will be
transmitted in that language. Users can override this setting via
the "o"ptions menu and save that preference in their RC file.
This may be a comma-separated list of languages in decreasing preference.
PREFERRED_LANGUAGE:en
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.
PREPEND_BASE_TO_SOURCE:TRUE
PREPEND_CHARSET_TO_SOURCE:TRUE tells Lynx to prepend a META CHARSET line
to text/html source files when they are retrieved for "d"ownloading
or passed to "p"rint functions, so HTTP headers will not be lost.
This is necessary for resolving charset for local html files,
while the assume_local_charset is just an assumption.
For the "d"ownload option, a META CHARSET will be added only if the HTTP
charset is present. The compilation default is TRUE.
It is generally desirable to have charset information for every local
html file, but META CHARSET string potentially could cause
compatibility problems with other browsers, see also PREPEND_BASE_TO_SOURCE.
Note that the prepending is not done for -source dumps.
PREPEND_CHARSET_TO_SOURCE:TRUEPRETTYSRC:FALSEPRETTYSRC_SPEC:<LEXEMENAME>:<TAGSPEC>:<TAGSPEC>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
PRETTYSRC_SPEC:COMM:B I:!I !BHTML comments will be surrounded by <b><i> and </i></b> in the internal html markup
PRETTYSRC_SPEC:ATTRVAL: span.attrval : !span PRETTYSRC_SPEC:HREF::
For lynx compiled with lss support, the following settings are the default:
PRETTYSRC_SPEC:COMM:span.htmlsrc_comment:!spanPRETTYSRC_SPEC:TAG:span.htmlsrc_tag:!spanPRETTYSRC_SPEC:ATTRIB:span.htmlsrc_attrib:!spanPRETTYSRC_SPEC:ATTRVAL:span.htmlsrc_attrval:!spanPRETTYSRC_SPEC:ABRACKET:span.htmlsrc_abracket:!spanPRETTYSRC_SPEC:ENTITY:span.htmlsrc_entity:!spanPRETTYSRC_SPEC:HREF:span.htmlsrc_href:!spanPRETTYSRC_SPEC:ENTIRE:span.htmlsrc_entire:!spanPRETTYSRC_SPEC:BADSEQ:span.htmlsrc_badseq:!spanPRETTYSRC_SPEC:BADTAG:span.htmlsrc_badtag:!spanPRETTYSRC_SPEC:BADATTR:span.htmlsrc_badattr:!spanPRETTYSRC_SPEC:SGMLSPECIAL:span.htmlsrc_sgmlspecial:!spanPRETTYSRC_SPEC:COMM:b:!bPRETTYSRC_SPEC:TAG:b:!bPRETTYSRC_SPEC:ATTRIB:b:!bPRETTYSRC_SPEC:ATTRVAL::nonePRETTYSRC_SPEC:ABRACKET:b:!bPRETTYSRC_SPEC:ENTITY:b:!bPRETTYSRC_SPEC:HREF::nonePRETTYSRC_SPEC:ENTIRE::nonePRETTYSRC_SPEC:BADSEQ:b:!bPRETTYSRC_SPEC:BADTAG::nonePRETTYSRC_SPEC:BADATTR::nonePRETTYSRC_SPEC:SGMLSPECIAL:b:!bPRETTYSRC_VIEW_NO_ANCHOR_NUMBERING:FALSE
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>
DOWNLOADER:<name>:<command>:<option>
<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.
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:
PRINTER:Computer Center printer:lpr -Pccprt %s:FALSEPRINTER:Office printer:lpr -POffprt %s:TRUEPRINTER:VMS printer:print /queue=cc$print %s:FALSE:58PRINTER:Busy VMS printer:@Lynx_Dir\:VMSPrint sys$print %s:FALSE:58PRINTER:Specify at run-time:echo -n "Enter a print command\: "; read word; sh -c "$word %s":FALSEPRINTER:Use Most to view:most -k +s %s:TRUE:23Downloader 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):
DOWNLOADER:Use Kermit to download to the terminal:kermit -i -s %s -a %s:TRUEDOWNLOADER:Use Most to view:most +s %s:TRUEDOWNLOADER:Use Zmodem to download to the local terminal:sz %s:TRUEDOWNLOADER: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:TRUEUPLOADER:Use Kermit to upload from your computer: kermit -i -r -a %s:TRUEUPLOADER:Use Zmodem to upload from your computer: rz %s:TRUENote for OS/390: /* S/390 -- gil -- 1464 */ The following is strongly recommended to undo ASCII->EBCDIC conversion.
DOWNLOADER:Save OS/390 binary file: iconv -f IBM-1047 -t ISO8859-1 %s >%s:FALSE
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.
QUIT_DEFAULT_YES:TRUE
REFERER_WITH_QUERY controls what happens when the URL in a Referer
header to be sent would contain a query part in the form of a "?"
character followed by one or more attribute=value pairs. Query parts
often contain sensitive or personal information resulting from filling
out forms, or other info that allows tracking of a user's browsing path
through a site, an thus should not be put in a Referer header (which may
get sent to an unrelated third-party site). On the other hand, some
sites (improperly) rely on browsers sending Referer headers, even when
the user is coming from a page whose URL has a query part.
If REFERER_WITH_QUERY is SEND, full Referer headers will be sent
including the query part (unless sending of Referer is disabled in
general, see NO_REFERER_HEADER above). If REFERER_WITH_QUERY is
PARTIAL, the Referer header will contain a partial URL, with the query
part stripped off. This is not strictly correct, but should satisfy
those sites that check only whether the user arrived at a page from an
"outside" link. If REFERER_WITH_QUERY is set to DROP (or anything else
unrecognized), the default, no Referer header is sent at all in this
situation.
REFERER_WITH_QUERY:DROPREPLAYSECS:0
Lynx uses temporary files for (among other purposes) the content of
various user interface pages. REUSE_TEMPFILES changes the behavior
for some of these temp files, among them pages shown for HISTORY,
VLINKS, OPTIONS, INFO, PRINT, DOWNLOAD commands.
If set to TRUE, the same file can be used multiple times for the same
purpose. If set to FALSE, a new filename is generated each time before
rewriting such a page. With TRUE, repeated invocation of these commands
is less likely to push previous documents out of the cache of rendered
texts (see also DEFAULT_CACHE_SIZE). This is especially useful with
intermittent (dialup) network connections, when it is desirable to
continue browsing through the cached documents after disconnecting.
With the default setting of FALSE, there can be more than one incarnation
of e.g. the VLINKS page cached in memory (but still only the most recently
generated one is kept as a file), resulting in sometimes less surprising
behaviour when returning to such a page via HISTORY or PREV_DOC functions
(most users will not encounter and notice this difference).
REUSE_TEMPFILES:FALSE
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/*
If SAVE_SPACE is defined, it will be used as a path prefix for the
suggested filename in "Save to Disk" operations from the "p"rint or
"d"ownload menus. On VMS, you can use either VMS (e.g., "SYS$LOGIN:")
or Unix syntax (including "~" for the HOME directory). On Unix, you
must use Unix syntax. If the symbol is not defined, or is zero-length
(""), no prefix will be used, and only a filename for saving in the
current default directory will be suggested.
This definition will be overridden if a "LYNX_SAVE_SPACE" environment
variable has been set on Unix, or logical has been defined on VMS.
SAVE_SPACE:~/foo/
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.
SCAN_FOR_BURIED_NEWS_REFS:TRUE
If SEEK_FRAG_AREA_IN_CUR is set FALSE, then HREF attribute values
in AREA tags consisting of only a fragment (HREF="#foo") will be
resolved with respect to the current document's base, which might
not be the same as the current document's URL. The compilation
default is to use the current document's URL, as is done for the
HREF attribute values of Anchors and LINKs that consist solely of
a fragment.
SEEK_FRAG_AREA_IN_CUR:TRUE
If SEEK_FRAG_MAP_IN_CUR is set FALSE, then USEMAP attribute values
(in IMG or OBJECT tags) consisting of only a fragment (USEMAP="#foo")
will be resolved with respect to the current document's base, which
might not be the same as the current document's URL.
The compilation default is to use the current document's URL in all
cases (i.e., assume the MAP is present below, if it wasn't present
above the point in the HTML stream where the USEMAP attribute was
detected). Lynx's present "single pass" rendering engine precludes
checking below before making the decision on how to resolve a USEMAP
reference consisting solely of a fragment.
SEEK_FRAG_MAP_IN_CUR:TRUESET_COOKIES:TRUE
SHOW_CURSOR controls whether or not the cursor is hidden or appears
over the current link in documents or the current option in popups.
Showing the cursor is handy if you are a sighted user with a poor
terminal that can't do bold and reverse video at the same time or
at all. It also can be useful to blind users, as an alternative
or supplement to setting LINKS_AND_FIELDS_ARE_NUMBERED or
LINKS_ARE_NUMBERED.
The default defined here or in userdefs.h can be changed via the
"o"ptions menu and saved in the RC file, and always can be toggled
via the -show_cursor command line switch.
SHOW_CURSOR:FALSE
If you prefer using the conventional (and more common) "KB", modify this
setting.
SHOW_KB_NAME:KiBSHOW_KB_RATE:TRUE
If SOFT_DQUOTES is TRUE, Lynx will emulate the invalid behavior of
treating '>' as a co-terminator of a double-quoted attribute value
and the tag which contains it, as was done in old versions of Netscape
and Mosaic. The compilation default is FALSE.
The compilation default, or default defined here, can be toggled via
a "-soft_dquotes" command line switch.
SOFT_DQUOTES:FALSE
SOURCE_CACHE sets the source caching behavior for Lynx:
FILE causes Lynx to keep a temporary file for each cached document
containing the HTML source of the document, which it uses to regenerate
the document when certain settings are changed (for instance,
historical vs. minimal vs. valid comment parsing) instead of reloading
the source from the network.
MEMORY is like FILE, except the document source is kept in memory. You
may wish to adjust DEFAULT_CACHE_SIZE and DEFAULT_VIRTUAL_MEMORY_SIZE
accordingly.
NONE is the default; the document source is not cached, and is reloaded
from the network when needed.
SOURCE_CACHE:NONE
This setting controls what will happen with cached source for the document
being fetched from the net if fetching was aborted (either user pressed
"z" or network went down). If set to KEEP, the source fetched so far will
be preserved (and used as cache), if set to DROP lynx will drop the
source cache for that document (i.e. only completely downloaded documents
will be cached in that case).
SOURCE_CACHE_FOR_ABORTED:DROP
Normally we expect you will connect to a remote site, e.g., the Lynx starting
site:
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:
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.
If STRIP_DOTDOT_URLS is TRUE, Lynx emulates the invalid behavior of many
browsers to strip a leading "../" segment from relative URLs in HTML
documents with a http or https base URL, if this would otherwise lead to
an absolute URLs with those characters still in it. Such URLs are normally
erroneous and not what is intended by page authors. Lynx will issue
a warning message when this occurs.
If STRIP_DOTDOT_URLS is FALSE, Lynx will use those URLs for requests
without taking any special actions or issuing Warnings, in most cases
this will result in an error response from the server.
Note that Lynx never tries to fix similar URLs for protocols other than
http and https, since they are less common and may actually be valid in
some cases.
STRIP_DOTDOT_URLS:TRUE
If SUBSTITUTE_UNDERSCORES is TRUE, the _underline_ format will be used
for emphasis tags in dumps.
The default defined here will override that in userdefs.h, and the user
can toggle the default via a "-underscore" command line switch.
SUBSTITUTE_UNDERSCORES:FALSE
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"
SUFFIX:.gif:image/gifThe 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:
SUFFIX:.html-u8:text/html;charset=utf-8:::UTF-8 HTMLThe 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.)
SUFFIX:.ps_gz:application/postscript:gzip::gzip'd PostscriptThe following is meant to match a full filename (but can match any file ending in "core", so be careful):
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.
SUFFIX:.ps:application/postscriptSUFFIX:.eps:application/postscriptSUFFIX:.ai:application/postscriptSUFFIX:.rtf:application/rtfSUFFIX:.snd:audio/basicSUFFIX:.gif:image/gifSUFFIX:.rgb:image/x-rgbSUFFIX:.png:image/pngSUFFIX:.xbm:image/x-xbitmapSUFFIX:.tiff:image/tiffSUFFIX:.jpg:image/jpegSUFFIX:.jpeg:image/jpegSUFFIX:.mpg:video/mpegSUFFIX:.mpeg:video/mpegSUFFIX:.mov:video/quicktimeSUFFIX:.hqx:application/mac-binhex40SUFFIX:.bin:application/octet-streamSUFFIX:.exe:application/octet-streamSUFFIX:.tar:application/x-tarSUFFIX:.tgz:application/x-tar:gzipSUFFIX:.Z::compressSUFFIX:.gz::gzipSUFFIX:.bz2:application/x-bzip2SUFFIX:.zip:application/zipSUFFIX:.lzh:application/x-lzhSUFFIX:.lha:application/x-lhaSUFFIX:.dms:application/x-dmsSUFFIX:.html:text/htmlSUFFIX:.txt:text/plain
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.
SUFFIX_ORDER:PRECEDENCE_OTHER
SYSTEM_EDITOR behaves the same as DEFAULT_EDITOR,
except that it can't be changed by users.
SYSTEM_EDITOR:none
VMS:
The mail command and qualifiers are defined in userdefs.h. Lynx
will spawn a subprocess to send replies and error messages. The
command, and qualifiers (if any), can be re-defined here. If
you use PMDF then headers will we passed via a header file.
If you use "generic" VMS MAIL, the subject will be passed on the
command line via a /subject="SUBJECT" qualifier, and inclusion
of other relevant headers may not be possible.
If your mailer uses another syntax, some hacking of the mailform()
mailmsg() and reply_by_mail() functions in LYMail.c, and send_file_to_mail()
function in LYPrint.c, may be required.
SYSTEM_MAIL:PMDF SENDSYSTEM_MAIL_FLAGS:/headersSYSTEM_MAIL:MAILSYSTEM_MAIL_FLAGS:
Unix:
The mail path and flags normally are defined for sendmail (or submit
with MMDF) in userdefs.h. You can change them here, but should first
read the zillions of CERT advisories about security problems with Unix
mailers.
SYSTEM_MAIL:/usr/mmdf/bin/submitSYSTEM_MAIL_FLAGS:-mlruxto,cc\*SYSTEM_MAIL:/usr/sbin/sendmailSYSTEM_MAIL_FLAGS:-t -oiSYSTEM_MAIL:/usr/lib/sendmailSYSTEM_MAIL_FLAGS:-t -oi
If TAGSOUP is set, Lynx uses the "Tag Soup DTD" rather than "SortaSGML".
The two approaches differ by the style of error detection and recovery.
Tag Soup DTD allows for improperly nested tags; SortaSGML is stricter.
TAGSOUP:FALSE
If TEXTFIELDS_NEED_ACTIVATION is set to TRUE, and lynx was compiled with
TEXTFIELDS_MAY_NEED_ACTIVATION defined, then text input form fields need
to be activated (by pressing the Enter key or similar) before the user
can enter or modify input. By default, input fields become automatically
activated when selected. Requiring explicit activation can be desired for
users who use alphanumeric keys for navigation (or other keys that have
special meaning in the line editor - ' ', "b", INS, DEL, etc), and don't
want to 'get stuck' in form fields. Instead of setting the option here,
explicit activation can also be requested with the -tna command line
option.
TEXTFIELDS_NEED_ACTIVATION:FALSE
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.
TRIM_INPUT_FIELDS:FALSE
UNDERLINE_LINKS controls whether links are underlined by default, or shown
in bold. Normally this default is set from the configure script.
UNDERLINE_LINKS:FALSE
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).
URL_DOMAIN_PREFIXES:www.URL_DOMAIN_SUFFIXES:.com,.edu,.net,.org
ncurses and slang have built-in support for the xterm mouse protocol. In
addition, ncurses can be linked with the gpm mouse library, to automatically
provide support for this interface in applications such as Lynx. (Please
read the ncurses faq to work around broken gpm configurations packaged by
some distributors). PDCurses implements mouse support for win32 console
windows, as does slang.
USE_MOUSE:FALSEUSE_SELECT_POPUPS:TRUE
VERBOSE_IMAGES controls whether Lynx replaces [LINK], [INLINE] and [IMAGE]
(for images without ALT) with filenames of these images.
This can be useful in determining what images are important
and which are mere decorations, e.g. button.gif, line.gif,
provided the author uses meaningful names.
The definition here will override the setting in userdefs.h.
VERBOSE_IMAGES:TRUE
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.
VIEWER:application/postscript:ghostview %s&:XWINDOWSVIEWER:image/gif:xli %s&:XWINDOWSVIEWER:image/x-xbm:xli %s&:XWINDOWSVIEWER:image/png:xli %s&:XWINDOWSVIEWER:image/tiff:xli %s&:XWINDOWSVIEWER:image/jpeg:xli %s&:XWINDOWSVIEWER:video/mpeg:mpeg_play %s &:XWINDOWS
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 .
VI_KEYS_ALWAYS_ON:FALSEEMACS_KEYS_ALWAYS_ON:FALSE
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.
XLOADIMAGE_COMMAND:xv %s