PageRenderTime 125ms CodeModel.GetById 101ms app.highlight 5ms RepoModel.GetById 1ms app.codeStats 0ms

/lynx-cur/lynx.cfg

http://github.com/brinkman83/bashrc
Config | 3689 lines | 3296 code | 393 blank | 0 comment | 0 complexity | 75397362dfd646d32855b841779d6cb1 MD5 | raw file

Large files files are truncated, but you can click here to view the full file

   1# $LynxId: lynx.cfg,v 1.189 2009/11/24 09:25:18 tom Exp $
   2# lynx.cfg file.
   3# The default placement for this file is /usr/local/lib/lynx.cfg (Unix)
   4#                                     or Lynx_Dir:lynx.cfg (VMS)
   5#
   6# $Format: "#PRCS LYNX_VERSION \"$ProjectVersion$\""$
   7#PRCS LYNX_VERSION "2.8.8dev.2"
   8#
   9# $Format: "#PRCS LYNX_DATE \"$ProjectDate$\""$
  10#PRCS LYNX_DATE "Wed, 25 Nov 2009 02:56:48 -0800"
  11#
  12# Definition pairs are of the form  VARIABLE:DEFINITION
  13# NO spaces are allowed between the pair items.
  14#
  15#  If you do not have write access to /usr/local/lib you may change
  16#  the default location of this file in the userdefs.h file and recompile,
  17#  or specify its location on the command line with the "-cfg"
  18#  command line option.
  19#
  20# Items may be commented out by putting a '#' as the FIRST char of the line
  21# (Any line beginning with punctuation is ignored).  Leading blanks on each
  22# line are ignored; trailing blanks may be significant depending on the option.
  23
  24# An HTML'ized description of all settings (based on comments in this file,
  25# with alphabetical table of settings and with table of settings by category)
  26# is available at http://lynx.isc.org/release/lynx2-8-5/lynx_help/cattoc.html
  27#
  28### The conversion is done via the scripts/cfg2html.pl script.
  29### Several directives beginning with '.' are used for this purpose.
  30
  31
  32.h1 Auxiliary Facilities
  33# These settings control the auxiliary navigating facilities of lynx, e.g.,
  34# jumpfiles, bookmarks, default URLs.
  35
  36
  37.h2 INCLUDE
  38# Starting with Lynx 2.8.1, the lynx.cfg file has a crude "include"
  39# facility.  This means that you can take advantage of the global lynx.cfg
  40# while also supplying your own tweaks.
  41#
  42# You can use a command-line argument (-cfg /where/is/lynx.cfg) or an
  43# environment variable (LYNX_CFG=/where/is/lynx.cfg).
  44# For instance, put in your .profile or .login:
  45#
  46#   LYNX_CFG=~/lynx.cfg; export LYNX_CFG   # in .profile for sh/ksh/bash/etc.
  47#   setenv LYNX_CFG ~/lynx.cfg             # in .login for [t]csh
  48#
  49# Then in ~/lynx.cfg:
  50#
  51#   INCLUDE:/usr/local/lib/lynx.cfg
  52#           ^^^^^^^^^^^^^^^^^^^^^^^ or whatever is appropriate on your system
  53# and now your own tweaks.
  54#
  55# Starting with Lynx 2.8.2, the INCLUDE facility is yet more powerful.  You can
  56# suppress all but specific settings that will be read from included files.
  57# This allows sysadmins to provide users the ability to customize lynx with
  58# options that normally do not affect security, such as COLOR, VIEWER, KEYMAP.
  59#
  60# The syntax is
  61#
  62#   INCLUDE:filename for <space-separated-list-of-allowed-settings>
  63#
  64# sample:
  65.ex
  66#INCLUDE:~/lynx.cfg for COLOR VIEWER KEYMAP
  67# only one space character should surround the word 'for'.  On Unix systems ':'
  68# is also accepted as separator.  In that case, the example can be written as
  69.ex
  70#INCLUDE:~/lynx.cfg:COLOR VIEWER KEYMAP
  71# In the example, only the settings COLOR, VIEWER and KEYMAP are accepted by
  72# lynx.  Other settings are ignored.  Note:  INCLUDE is also treated as a
  73# setting, so to allow an included file to include other files, put INCLUDE in
  74# the list of allowed settings.
  75#
  76# If you allow an included file to include other files, and if a list of
  77# allowed settings is specified for that file with the INCLUDE command, nested
  78# files are only allowed to include the list of settings that is the set AND of
  79# settings allowed for the included file and settings allowed by nested INCLUDE
  80# commands.  In short, there is no security hole introduced by including a
  81# user-defined configuration file if the original list of allowed settings is
  82# secure.
  83
  84
  85.h2 STARTFILE
  86# STARTFILE is the default starting URL if none is specified
  87#   on the command line or via a WWW_HOME environment variable;
  88#   Lynx will refuse to start without a starting URL of some kind.
  89# STARTFILE can be remote, e.g. http://www.w3.org/default.html ,
  90#                or local, e.g. file://localhost/PATH_TO/FILENAME ,
  91#           where PATH_TO is replaced with the complete path to FILENAME
  92#           using Unix shell syntax and including the device on VMS.
  93#
  94# Normally we expect you will connect to a remote site, e.g., the Lynx starting
  95# site:
  96#STARTFILE:http://lynx.isc.org/
  97#
  98# As an alternative, you may want to use a local URL.  A good choice for this is
  99# the user's home directory:
 100.ex
 101#STARTFILE:file://localhost/~/
 102#
 103# Your choice of STARTFILE should reflect your site's needs, and be a URL that
 104# you can connect to reliably.  Otherwise users will become confused and think
 105# that they cannot run Lynx.
 106
 107
 108.h2 HELPFILE
 109# HELPFILE must be defined as a URL and must have a
 110# complete path if local:
 111# file://localhost/PATH_TO/lynx_help/lynx_help_main.html
 112#   Replace PATH_TO with the path to the lynx_help subdirectory
 113#   for this distribution (use SHELL syntax including the device
 114#   on VMS systems).
 115# The default HELPFILE is:
 116# http://lynx.isc.org/release/lynx2-8-7/lynx_help/lynx_help_main.html
 117#   This should be changed to the local path.
 118# This definition will be overridden if the "LYNX_HELPFILE" environment
 119# variable has been set.
 120#
 121#HELPFILE:http://lynx.isc.org/release/lynx2-8-7/lynx_help/lynx_help_main.html
 122.ex
 123##HELPFILE:file://localhost/PATH_TO/lynx_help/lynx_help_main.html
 124HELPFILE:file://localhost/usr/share/doc/lynx-cur/lynx_help/lynx_help_main.html.gz
 125
 126
 127.h2 DEFAULT_INDEX_FILE
 128# DEFAULT_INDEX_FILE is the default file retrieved when the
 129# user presses the 'I' key when viewing any document.
 130# An index to your CWIS can be placed here or a document containing
 131# pointers to lots of interesting places on the web.
 132#
 133#DEFAULT_INDEX_FILE:http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html
 134DEFAULT_INDEX_FILE:http://lynx.isc.org/
 135
 136
 137.h1 Interaction
 138
 139.h2 GOTOBUFFER
 140# Set GOTOBUFFER to TRUE if you want to have the previous goto URL,
 141# if any, offered for reuse or editing when using the 'g'oto command.
 142# The default is defined in userdefs.h.  If left FALSE, the circular
 143# buffer of previously entered goto URLs can still be invoked via the
 144# Up-Arrow or Down-Arrow keys after entering the 'g'oto command.
 145#
 146#GOTOBUFFER:FALSE
 147
 148
 149.h2 JUMP_PROMPT
 150# JUMP_PROMPT is the default statusline prompt for selecting a jumps file
 151# shortcut.  (see below).
 152# You can change the prompt here from that defined in userdefs.h.  Any
 153# trailing white space will be trimmed, and a single space is added by Lynx
 154# following the last non-white character.  You must set the default prompt
 155# before setting the default jumps file (below).  If a default jumps file
 156# was set via userdefs.h, and you change the prompt here, you must set the
 157# default jumps file again (below) for the change to be implemented.
 158#
 159#JUMP_PROMPT:Jump to (use '?' for list):
 160
 161
 162.h1 Auxiliary Facilities
 163
 164.h2 JUMPFILE
 165# JUMPFILE is the local file checked for short-cut names for URLs
 166# when the user presses the 'j' (JUMP) key.  The user will be prompted
 167# to enter a short-cut name for an URL, which Lynx will then follow
 168# in a similar manner to 'g'oto; alternatively, s/he can enter '?'
 169# to view the full JUMPFILE list of short-cuts with associated URLs.
 170# There is an example jumps file in the samples subdirectory.
 171# If not defined here or in userdefs.h, the JUMP command will invoke
 172# the NO_JUMPFILE statusline message (see  LYMessages_en.h ).
 173#
 174# To allow '?' to work, include in the JUMPFILE
 175# a short-cut to the JUMPFILE itself, e.g.
 176# <dt>?<dd><a href="file://localhost/path/jumps.html">This Shortcut List</a>
 177#
 178# On VMS, use Unix SHELL syntax (including a lead slash) to define it.
 179#
 180# Alternate jumps files can be defined and mapped to keys here.  If the
 181# keys have already been mapped, then those mappings will be replaced,
 182# but you should leave at least one key mapped to the default jumps
 183# file.  You optionally may include a statusline prompt string for the
 184# mapping.  You must map upper and lowercase keys separately (beware of
 185# mappings to keys which the user can further remap via the 'o'ptions
 186# menu).  The format is:
 187#
 188#	JUMPFILE:path:key[:prompt]
 189#
 190# where path should begin with a '/' (i.e., not include file://localhost).
 191# Any white space following a prompt string will be trimmed, and a single
 192# space will be added by Lynx.
 193#
 194# In the following line, include the actual full local path to JUMPFILE,
 195# but do not include 'file://localhost' in the line.
 196#JUMPFILE:/FULL_LOCAL_PATH/jumps.html
 197.ex
 198#JUMPFILE:/Lynx_Dir/ips.html:i:IP or Interest group (? for list):
 199
 200
 201.h2 JUMPBUFFER
 202# Set JUMPBUFFER to TRUE if you want to have the previous jump target,
 203# if any, offered for reuse or editing when using the 'J'ump command.
 204# The default is defined in userdefs.h.  If left FALSE, the circular
 205# buffer of previously entered targets (shortcuts) can still be invoked
 206# via the Up-Arrow or Down-Arrow keys after entering the 'J'ump command.
 207# If multiple jumps files are installed, the recalls of shortcuts will
 208# be specific to each file.  If Lynx was built with PERMIT_GOTO_FROM_JUMP
 209# defined, any random URLs used instead of shortcuts will be stored in the
 210# goto URL buffer, not in the shortcuts buffer(s), and the single character
 211# ':' can be used as a target to invoke the goto URL buffer (as if 'g'oto
 212# followed by Up-Arrow had been entered).
 213#
 214#JUMPBUFFER:FALSE
 215
 216
 217.h1 Internal Behavior
 218
 219.h2 SAVE_SPACE
 220# If SAVE_SPACE is defined, it will be used as a path prefix for the
 221# suggested filename in "Save to Disk" operations from the 'p'rint or
 222# 'd'ownload menus.  On VMS, you can use either VMS (e.g., "SYS$LOGIN:")
 223# or Unix syntax (including '~' for the HOME directory).  On Unix, you
 224# must use Unix syntax.  If the symbol is not defined, or is zero-length
 225# (""), no prefix will be used, and only a filename for saving in the
 226# current default directory will be suggested.
 227# This definition will be overridden if a "LYNX_SAVE_SPACE" environment
 228# variable has been set on Unix, or logical has been defined on VMS.
 229#
 230#SAVE_SPACE:~/foo/
 231
 232
 233.h2 REUSE_TEMPFILES
 234# Lynx uses temporary files for (among other purposes) the content of
 235# various user interface pages.  REUSE_TEMPFILES changes the behavior
 236# for some of these temp files, among them pages shown for HISTORY,
 237# VLINKS, OPTIONS, INFO, PRINT, DOWNLOAD commands.
 238# If set to TRUE, the same file can be used multiple times for the same
 239# purpose.  If set to FALSE, a new filename is generated each time before
 240# rewriting such a page.  With TRUE, repeated invocation of these commands
 241# is less likely to push previous documents out of the cache of rendered
 242# texts (see also DEFAULT_CACHE_SIZE).  This is especially useful with
 243# intermittent (dialup) network connections, when it is desirable to
 244# continue browsing through the cached documents after disconnecting.
 245# With the default setting of FALSE, there can be more than one incarnation
 246# of e.g. the VLINKS page cached in memory (but still only the most recently
 247# generated one is kept as a file), resulting in sometimes less surprising
 248# behaviour when returning to such a page via HISTORY or PREV_DOC functions
 249# (most users will not encounter and notice this difference).
 250#
 251#REUSE_TEMPFILES:FALSE
 252
 253
 254.h2 LYNX_HOST_NAME
 255# If LYNX_HOST_NAME is defined here or in userdefs.h, it will be
 256# treated as an alias for the local host name in checks for URLs on
 257# the local host (e.g., when the -localhost switch is set), and this
 258# host name, "localhost", and HTHostName (the fully qualified domain
 259# name of the system on which Lynx is running) will all be passed as
 260# local.  A different definition here will override that in userdefs.h.
 261#
 262#LYNX_HOST_NAME:www.cc.ukans.edu
 263
 264
 265.h2 LOCALHOST_ALIAS
 266# localhost aliases
 267# Any LOCALHOST_ALIAS definitions also will be accepted as local when
 268# the -localhost switch is set.  These need not actually be local, i.e.,
 269# in contrast to LYNX_HOST_NAME, you can define them to trusted hosts at
 270# other Internet sites.
 271#
 272.ex 2
 273#LOCALHOST_ALIAS:gopher.server.domain
 274#LOCALHOST_ALIAS:news.server.domain
 275
 276
 277.h2 LOCAL_DOMAIN
 278# LOCAL_DOMAIN is used for a tail match with the ut_host element of
 279# the utmp or utmpx structure on systems with utmp capabilities, to
 280# determine if a user is local to your campus or organization when
 281# handling -restrictions=inside_foo or outside_foo settings for ftp,
 282# news, telnet/tn3270 and rlogin URLs.  An "inside" user is assumed
 283# if your system does not have utmp capabilities.  CHANGE THIS here
 284# if it was not changed in userdefs.h at compilation time.
 285#
 286#LOCAL_DOMAIN:ukans.edu
 287
 288
 289.h1 Session support
 290
 291.h2 AUTO_SESSION
 292# If AUTO_SESSION is TRUE lynx will save/restore useful information about
 293# your browsing history when closing/starting current lynx session if
 294# no command-line session switches override this setting.
 295# This setting is useful only if SESSION_FILE is defined here or in the user's
 296# .lynxrc file.
 297#
 298#AUTO_SESSION:FALSE
 299
 300.h2 SESSION_FILE
 301# SESSION_FILE defines the file name where lynx will store user sessions.
 302# This setting is used only when AUTO_SESSION is true.
 303# Note: the default setting will store/resume each session in a different
 304# folder under same file name (if that is allowed by operating system)
 305# when lynx is invoked from different directories.
 306# (The current working directory may be changed inside lynx)
 307#
 308# If you want to use the same session file wherever you invoke Lynx,
 309# enter the full path below, eg '/home/<username>/.lynx_session'.
 310#
 311# If you do not want this feature, leave the setting commented.
 312# Users can still customize SESSION_FILE and AUTO_SESSION via
 313# their .lynxrc file.
 314#
 315#SESSION_FILE:lynx_session
 316
 317.h2 SESSION_LIMIT
 318# SESSION_LIMIT defines maximum number of:  searched strings, goto URLs,
 319# visited links and history entries which will be saved in session file.  The
 320# minimum allowed is 1, the maximum is 10000.
 321#
 322# For instance, if SESSION_LIMIT is 250, a per-session limit of 250 entries of
 323# searched strings, goto URLs, visited links and history entries will be saved
 324# in the session file.
 325#
 326# There is no fixed limit on the number of entries which can be restored;
 327# It is limited only by available memory.
 328#
 329#SESSION_LIMIT:250
 330
 331
 332.h1 Character sets
 333
 334.h2 CHARACTER_SET
 335# CHARACTER_SET defines the display character set, i.e., assumed to be
 336# installed on the user's terminal.  It determines which characters or strings
 337# will be used to represent 8-bit character entities within HTML.  New
 338# character sets may be defined as explained in the README files of the
 339# src/chrtrans directory in the Lynx source code distribution.  For Asian (CJK)
 340# character sets, it also determines how Kanji code will be handled.  The
 341# default is defined in userdefs.h and can be changed here or via the
 342# 'o'ptions menu.  The 'o'ptions menu setting will be stored in the user's RC
 343# file whenever those settings are saved, and thereafter will be used as the
 344# default.  For Lynx a "character set" has two names:  a MIME name (for
 345# recognizing properly labeled charset parameters in HTTP headers etc.), and a
 346# human-readable string for the 'O'ptions Menu (so you may find info about
 347# language or group of languages besides MIME name).  Not all 'human-readable'
 348# names correspond to exactly one valid MIME charset (example is "Chinese");
 349# in that case an appropriate valid (and more specific) MIME name should be
 350# used where required.  Well-known synonyms are also processed in the code.
 351#
 352# Raw (CJK) mode
 353#
 354# Lynx normally translates characters from a document's charset to display
 355# charset, using ASSUME_CHARSET value (see below) if the document's charset
 356# is not specified explicitly.  Raw (CJK) mode is OFF for this case.
 357# When the document charset is specified explicitly, that charset
 358# overrides any assumption like ASSUME_CHARSET or raw (CJK) mode.
 359#
 360# For the Asian (CJK) display character sets, the corresponding charset is
 361# assumed in documents, i.e., raw (CJK) mode is ON by default.  In raw CJK
 362# mode, 8-bit characters are not reverse translated in relation to the entity
 363# conversion arrays, i.e., they are assumed to be appropriate for the display
 364# character set.  The mode should be toggled OFF when an Asian (CJK) display
 365# character set is selected but the document is not CJK and its charset not
 366# specified explicitly.
 367#
 368# Raw (CJK) mode may be toggled by user via '@' (LYK_RAW_TOGGLE) key,
 369# the -raw command line switch or from the 'o'ptions menu.
 370#
 371# Raw (CJK) mode effectively changes the charset assumption about unlabeled
 372# documents.  You can toggle raw mode ON if you believe the document has a
 373# charset which does correspond to your Display Character Set.  On the other
 374# hand, if you set ASSUME_CHARSET the same as Display Character Set you get raw
 375# mode ON by default (but you get assume_charset=iso-8859-1 if you try raw mode
 376# OFF after it).
 377#
 378# Note that "raw" does not mean that every byte will be passed to the screen.
 379# HTML character entities may get expanded and translated, inappropriate
 380# control characters filtered out, etc.  There is a "Transparent" pseudo
 381# character set for more "rawness".
 382#
 383# Since Lynx now supports a wide range of platforms it may be useful to note
 384# the cpXXX codepages used by IBM PC compatible computers, and windows-xxxx
 385# used by native MS-Windows apps.  We also note that cpXXX pages rarely are
 386# found on Internet, but are mostly for local needs on DOS.
 387#
 388# Recognized character sets include:
 389#
 390.nf
 391#    string for 'O'ptions Menu          MIME name
 392#    ===========================        =========
 393#    7 bit approximations (US-ASCII)    us-ascii
 394#    Western (ISO-8859-1)               iso-8859-1
 395#    Western (ISO-8859-15)              iso-8859-15
 396#    Western (cp850)                    cp850
 397#    Western (windows-1252)             windows-1252
 398#    IBM PC US codepage (cp437)         cp437
 399#    DEC Multinational                  dec-mcs
 400#    Macintosh (8 bit)                  macintosh
 401#    NeXT character set                 next
 402#    HP Roman8                          hp-roman8
 403#    Chinese                            euc-cn
 404#    Japanese (EUC-JP)                  euc-jp
 405#    Japanese (Shift_JIS)               shift_jis
 406#    Korean                             euc-kr
 407#    Taipei (Big5)                      big5
 408#    Vietnamese (VISCII)                viscii
 409#    Eastern European (ISO-8859-2)      iso-8859-2
 410#    Eastern European (cp852)           cp852
 411#    Eastern European (windows-1250)    windows-1250
 412#    Latin 3 (ISO-8859-3)               iso-8859-3
 413#    Latin 4 (ISO-8859-4)               iso-8859-4
 414#    Baltic Rim (ISO-8859-13)		iso-8859-13
 415#    Baltic Rim (cp775)                 cp775
 416#    Baltic Rim (windows-1257)          windows-1257
 417#    Celtic (ISO-8859-14)		iso-8859-14
 418#    Cyrillic (ISO-8859-5)              iso-8859-5
 419#    Cyrillic (cp866)                   cp866
 420#    Cyrillic (windows-1251)            windows-1251
 421#    Cyrillic (KOI8-R)                  koi8-r
 422#    Arabic (ISO-8859-6)                iso-8859-6
 423#    Arabic (cp864)                     cp864
 424#    Arabic (windows-1256)              windows-1256
 425#    Greek (ISO-8859-7)                 iso-8859-7
 426#    Greek (cp737)                      cp737
 427#    Greek2 (cp869)                     cp869
 428#    Greek (windows-1253)               windows-1253
 429#    Hebrew (ISO-8859-8)                iso-8859-8
 430#    Hebrew (cp862)                     cp862
 431#    Hebrew (windows-1255)              windows-1255
 432#    Turkish (ISO-8859-9)               iso-8859-9
 433#    North European (ISO-8859-10)	iso-8859-10
 434#    Ukrainian Cyrillic (cp866u)        cp866u
 435#    Ukrainian Cyrillic (KOI8-U)        koi8-u
 436#    UNICODE (UTF-8)                    utf-8
 437#    RFC 1345 w/o Intro                 mnemonic+ascii+0
 438#    RFC 1345 Mnemonic                  mnemonic
 439#    Transparent                        x-transparent
 440.fi
 441#
 442# The value should be the MIME name of a character set recognized by
 443# Lynx (case insensitive).
 444# Find RFC 1345 at http://www.ics.uci.edu/pub/ietf/uri/rfc1345.txt .
 445#
 446CHARACTER_SET:iso-8859-1
 447
 448.h2 LOCALE_CHARSET
 449# LOCALE_CHARSET overrides CHARACTER_SET if true, using the current locale to
 450# lookup a MIME name that corresponds, and use that as the display charset.
 451#
 452# Note that while nl_langinfo(CODESET) itself is standardized, the return
 453# values and their relationship to the locale value is not.  GNU libiconv
 454# happens to give useful values, but other implementations are not guaranteed
 455# to do this.
 456#LOCALE_CHARSET:FALSE
 457LOCALE_CHARSET:TRUE
 458
 459
 460.h2 ASSUME_CHARSET
 461# ASSUME_CHARSET changes the handling of documents which do not
 462# explicitly specify a charset.  Normally Lynx assumes that 8-bit
 463# characters in those documents are encoded according to iso-8859-1
 464# (the official default for the HTTP protocol).  When ASSUME_CHARSET
 465# is defined here or by an -assume_charset command line flag is in effect,
 466# Lynx will treat documents as if they were encoded accordingly.
 467# See above on how this interacts with "raw mode" and the Display
 468# Character Set.
 469# ASSUME_CHARSET can also be changed via the 'o'ptions menu but will
 470# not be saved as permanent value in user's .lynxrc file to avoid more chaos.
 471#
 472#ASSUME_CHARSET:iso-8859-1
 473
 474
 475.h2 ASSUMED_DOC_CHARSET_CHOICE
 476.h2 DISPLAY_CHARSET_CHOICE
 477# It is possible to reduce the number of charset choices in the 'O'ptions menu
 478# for "display charset" and "assumed document charset" fields via
 479# DISPLAY_CHARSET_CHOICE and ASSUMED_DOC_CHARSET_CHOICE settings correspondingly.
 480# Each of these settings can be used several times to define the set of possible
 481# choices for corresponding field. The syntax for the values is
 482#
 483#	string | prefix* | *
 484#
 485# where
 486#
 487#	'string' is either the MIME name of charset or it's full name (listed
 488#		either in the left or in the right column of table of
 489#		recognized charsets), case-insensitive - e.g.  'Koi8-R' or
 490#		'Cyrillic (KOI8-R)' (both without quotes),
 491#
 492#	'prefix' is any string, and such value will select all charsets having
 493#		the name with prefix matching given (case insensitive), i.e.,
 494#		for the charsets listed in the table of recognized charsets,
 495#
 496.ex
 497# ASSUMED_DOC_CHARSET_CHOICE:cyrillic*
 498#		will be equal to specifying
 499.ex 4
 500# ASSUMED_DOC_CHARSET_CHOICE:cp866
 501# ASSUMED_DOC_CHARSET_CHOICE:windows-1251
 502# ASSUMED_DOC_CHARSET_CHOICE:koi8-r
 503# ASSUMED_DOC_CHARSET_CHOICE:iso-8859-5
 504#		or lines with full names of charsets.
 505#
 506#	literal string '*' (without quotes) will enable all charset choices
 507#		in corresponding field.  This is useful for overriding site
 508#		defaults in private pieces of lynx.cfg included via INCLUDE
 509#		directive.
 510#
 511# Default values for both settings are '*', but any occurrence of settings
 512# with values that denote any charsets will make only listed choices available
 513# for corresponding field.
 514#ASSUMED_DOC_CHARSET_CHOICE:*
 515#DISPLAY_CHARSET_CHOICE:*
 516
 517
 518.h2 ASSUME_LOCAL_CHARSET
 519# ASSUME_LOCAL_CHARSET is like ASSUME_CHARSET but only applies to local
 520# files.  If no setting is given here or by an -assume_local_charset
 521# command line option, the value for ASSUME_CHARSET or -assume_charset
 522# is used.  It works for both text/plain and text/html files.
 523# This option will ignore "raw mode" toggling when local files are viewed
 524# (it is "stronger" than "assume_charset" or the effective change
 525# of the charset assumption caused by changing "raw mode"),
 526# so only use when necessary.
 527#
 528#ASSUME_LOCAL_CHARSET:iso-8859-1
 529
 530
 531.h2 PREPEND_CHARSET_TO_SOURCE
 532# PREPEND_CHARSET_TO_SOURCE:TRUE tells Lynx to prepend a META CHARSET line
 533# to text/html source files when they are retrieved for 'd'ownloading
 534# or passed to 'p'rint functions, so HTTP headers will not be lost.
 535# This is necessary for resolving charset for local html files,
 536# while the assume_local_charset is just an assumption.
 537# For the 'd'ownload option, a META CHARSET will be added only if the HTTP
 538# charset is present.  The compilation default is TRUE.
 539# It is generally desirable to have charset information for every local
 540# html file, but META CHARSET string potentially could cause
 541# compatibility problems with other browsers, see also PREPEND_BASE_TO_SOURCE.
 542# Note that the prepending is not done for -source dumps.
 543#
 544PREPEND_CHARSET_TO_SOURCE:FALSE
 545
 546
 547.h2 NCR_IN_BOOKMARKS
 548# NCR_IN_BOOKMARKS:TRUE allows you to save 8-bit characters in bookmark titles
 549# in the unicode format (NCR).  This may be useful if you need to switch
 550# display charsets frequently.  This is the case when you use Lynx on different
 551# platforms, e.g., on UNIX and from a remote PC, and want to keep the bookmarks
 552# file persistent.
 553# Another aspect is compatibility:  NCR is part of I18N and HTML4.0
 554# specifications supported starting with Lynx 2.7.2, Netscape 4.0 and MSIE 4.0.
 555# Older browser versions will fail so keep NCR_IN_BOOKMARKS:FALSE if you
 556# plan to use them.
 557#
 558#NCR_IN_BOOKMARKS:FALSE
 559
 560
 561.h2 FORCE_8BIT_TOUPPER
 562# FORCE_8BIT_TOUPPER overrides locale settings and uses internal 8-bit
 563# case-conversion mechanism for case-insensitive searches in non-ASCII display
 564# character sets.  It is FALSE by default and should not be changed unless
 565# you encounter problems with case-insensitive searches.
 566#
 567#FORCE_8BIT_TOUPPER:FALSE
 568
 569
 570.h2 OUTGOING_MAIL_CHARSET
 571# While Lynx supports different platforms and display character sets
 572# we need to limit the charset in outgoing mail to reduce
 573# trouble for remote recipients who may not recognize our charset.
 574# You may try US-ASCII as the safest value (7 bit), any other MIME name,
 575# or leave this field blank (default) to use the display character set.
 576# Charset translations currently are implemented for mail "subjects= " only.
 577#
 578#OUTGOING_MAIL_CHARSET:
 579
 580
 581.h2 ASSUME_UNREC_CHARSET
 582# If Lynx encounters a charset parameter it doesn't recognize, it will
 583# replace the value given by ASSUME_UNREC_CHARSET (or a corresponding
 584# -assume_unrec_charset command line option) for it.  This can be used
 585# to deal with charsets unknown to Lynx, if they are "sufficiently
 586# similar" to one that Lynx does know about, by forcing the same
 587# treatment.  There is no default, and you probably should leave this
 588# undefined unless necessary.
 589#
 590#ASSUME_UNREC_CHARSET:iso-8859-1
 591
 592.h2 PREFERRED_LANGUAGE
 593# PREFERRED_LANGUAGE is the language in MIME notation (e.g., "en",
 594# "fr") which will be indicated by Lynx in its Accept-Language headers
 595# as the preferred language.  If available, the document will be
 596# transmitted in that language.  Users can override this setting via
 597# the 'o'ptions menu and save that preference in their RC file.
 598# This may be a comma-separated list of languages in decreasing preference.
 599#
 600PREFERRED_LANGUAGE:en
 601
 602
 603.h2 PREFERRED_CHARSET
 604# PREFERRED_CHARSET specifies the character set in MIME notation (e.g.,
 605# "ISO-8859-2", "ISO-8859-5") which Lynx will indicate you prefer in
 606# requests to http servers using an Accept-Charsets header.  Users can
 607# change it via the 'o'ptions menu and save that preference in their RC file.
 608# The value should NOT include "ISO-8859-1" or "US-ASCII",
 609# since those values are always assumed by default.
 610# If a file in that character set is available, the server will send it.
 611# If no Accept-Charset header is present, the default is that any
 612# character set is acceptable.  If an Accept-Charset header is present,
 613# and if the server cannot send a response which is acceptable
 614# according to the Accept-Charset header, then the server SHOULD send
 615# an error response with the 406 (not acceptable) status code, though
 616# the sending of an unacceptable response is also allowed.  See RFC 2068
 617# (http://www.ics.uci.edu/pub/ietf/uri/rfc2068.txt).
 618#
 619#PREFERRED_CHARSET:
 620
 621
 622.h2 CHARSETS_DIRECTORY
 623# CHARSETS_DIRECTORY specifies the directory with the fonts (glyph data)
 624# used by Lynx to switch the display-font to a font best suited for the
 625# given document.  The font should be in a format understood by the
 626# platforms TTY-display-font-switching API.  Currently supported on OS/2 only.
 627#
 628# Lynx expects the glyphs for the charset CHARSET with character cell
 629# size HHHxWWW to be stored in a file HHHxWWW/CHARSET.fnt inside the directory
 630# specified by CHARSETS_DIRECTORY.  E.g., the font for koi8-r sized 14x9
 631# should be in the file 14x9/koi8-r.fnt.
 632#
 633#CHARSETS_DIRECTORY:
 634
 635
 636.h2 CHARSET_SWITCH_RULES
 637# CHARSET_SWITCH_RULES hints lynx on how to choose the best display font given
 638# the document encoding.  This string is a sequence of chunks, each chunk
 639# having the following form:
 640#
 641# IN_CHARSET1 IN_CHARSET2 ... IN_CHARSET5 :OUT_CHARSET
 642#
 643# For readability, one may insert arbitrary additional punctuation (anything
 644# but : is ignored).  E.g., if lynx is able to switch only to display charsets
 645# cp866, cp850, cp852, and cp862, then the following setting may be useful
 646# (split for readability):
 647#
 648# CHARSET_SWITCH_RULES: koi8-r ISO-8859-5 windows-1251 cp866u KOI8-U :cp866,
 649#	iso-8859-1 windows-1252 ISO-8859-15 :cp850,
 650#	ISO-8859-2 windows-1250 :cp852,
 651#	ISO-8859-8 windows-1255 :cp862
 652#
 653#CHARSET_SWITCH_RULES:
 654
 655
 656.h1 Interaction
 657
 658.h2 URL_DOMAIN_PREFIXES
 659.h2 URL_DOMAIN_SUFFIXES
 660# URL_DOMAIN_PREFIXES and URL_DOMAIN_SUFFIXES are strings which will be
 661# prepended (together with a scheme://) and appended to the first element
 662# of command line or 'g'oto arguments which are not complete URLs and
 663# cannot be opened as a local file (file://localhost/string).  Both
 664# can be comma-separated lists.  Each prefix must end with a dot, each
 665# suffix must begin with a dot, and either may contain other dots (e.g.,
 666# .com.jp).  The default lists are defined in userdefs.h and can be
 667# replaced here.  Each prefix will be used with each suffix, in order,
 668# until a valid Internet host is created, based on a successful DNS
 669# lookup (e.g., foo will be tested as www.foo.com and then www.foo.edu
 670# etc.).  The first element can include a :port and/or /path which will
 671# be restored with the expanded host (e.g., wfbr:8002/dir/lynx will
 672# become http://www.wfbr.edu:8002/dir/lynx).  The prefixes will not be
 673# used if the first element ends in a dot (or has a dot before the
 674# :port or /path), and similarly the suffixes will not be used if the
 675# the first element begins with a dot (e.g., .nyu.edu will become
 676# http://www.nyu.edu without testing www.nyu.com).  Lynx will try to
 677# guess the scheme based on the first field of the expanded host name,
 678# and use "http://" as the default (e.g., gopher.wfbr.edu or gopher.wfbr.
 679# will be made gopher://gopher.wfbr.edu).
 680#
 681#URL_DOMAIN_PREFIXES:www.
 682#URL_DOMAIN_SUFFIXES:.com,.edu,.net,.org
 683
 684
 685.h2 FORMS_OPTIONS
 686# Toggle whether the Options Menu is key-based or form-based;
 687# the key-based version is available only if specified at compile time.
 688#FORMS_OPTIONS:TRUE
 689
 690
 691.h2 PARTIAL
 692# Display partial pages while downloading
 693#PARTIAL:TRUE
 694
 695
 696.h2 PARTIAL_THRES
 697# Set the threshold # of lines Lynx must render before it
 698# redraws the screen in PARTIAL mode.  Anything < 0 implies
 699# use of the screen size.
 700#PARTIAL_THRES:-1
 701
 702
 703.h2 SHOW_KB_RATE
 704# While getting large files, Lynx shows the approximate rate of transfer.
 705# Set this to change the units shown.  "Kilobytes" denotes 1024 bytes:
 706#	NONE to disable the display of transfer rate altogether.
 707#	TRUE or KB for Kilobytes/second.
 708#	FALSE or BYTES for bytes/second.
 709#	KB,ETA to show Kilobytes/second with estimated completion time.
 710#	BYTES,ETA to show BYTES/second with estimated completion time.
 711# Note that the "ETA" values are available if USE_READPROGRESS was defined.
 712#SHOW_KB_RATE:TRUE
 713
 714.h2 SHOW_KB_NAME
 715# Set the abbreviation for Kilobytes (1024).
 716# Quoting from
 717#	http://www.romulus2.com/articles/guides/misc/bitsbytes.shtml
 718# In December 1998, the International Electrotechnical Commission (IEC)
 719# approved a new IEC International Standard.  Instead of using the metric
 720# prefixes for multiples in binary code, the new IEC standard invented specific
 721# prefixes for binary multiples made up of only the first two letters of the
 722# metric prefixes and adding the first two letters of the word "binary".  Thus,
 723# for instance, instead of Kilobyte (KB) or Gigabyte (GB), the new terms would
 724# be kibibyte (KiB) or gibibyte (GiB).
 725#
 726# If you prefer using the conventional (and more common) "KB", modify this
 727# setting.
 728#SHOW_KB_NAME:KiB
 729
 730.h1 Timeouts
 731
 732.h2 INFOSECS
 733.h2 MESSAGESECS
 734.h2 ALERTSECS
 735.h2 NO_PAUSE
 736# The following definitions set the number of seconds for
 737# pauses following statusline messages that would otherwise be
 738# replaced immediately, and are more important than the unpaused
 739# progress messages.  Those set by INFOSECS are also basically
 740# progress messages (e.g., that a prompted input has been canceled)
 741# and should have the shortest pause.  Those set by MESSAGESECS are
 742# informational (e.g., that a function is disabled) and should have
 743# a pause of intermediate duration.  Those set by ALERTSECS typically
 744# report a serious problem and should be paused long enough to read
 745# whenever they appear (typically unexpectedly).  The default values
 746# are defined in userdefs.h, and can be modified here should longer
 747# pauses be desired for braille-based access to Lynx.
 748#
 749# SVr4-curses implementations support time delays in milliseconds,
 750# hence the value may be given shorter, e.g., 0.5
 751#
 752# Use the NO_PAUSE option (like the command-line -nopause) to override
 753# all of the delay times.
 754#
 755#INFOSECS:1
 756#MESSAGESECS:2
 757#ALERTSECS:3
 758#NO_PAUSE:FALSE
 759
 760.h2 DEBUGSECS
 761# Set DEBUGSECS to a nonzero value to slow down progress messages
 762# (see "-delay" option).
 763#DEBUGSECS:0
 764
 765.h2 REPLAYSECS
 766# Set REPLAYSECS to a nonzero value to allow for slow replaying of
 767# command scripts (see "-cmd_script" option).
 768#REPLAYSECS:0
 769
 770.h1 Appearance
 771# These settings control the appearance of Lynx's screen and the way
 772# Lynx renders some tags.
 773
 774.h2 USE_SELECT_POPUPS
 775# If USE_SELECT_POPUPS is set FALSE, Lynx will present a vertical list of
 776# radio buttons for the OPTIONs in SELECT blocks which lack the MULTIPLE
 777# attribute, instead of using a popup menu.  Note that if the MULTIPLE
 778# attribute is present in the SELECT start tag, Lynx always will create a
 779# vertical list of checkboxes for the OPTIONs.
 780# The default defined here or in userdefs.h can be changed via the 'o'ptions
 781# menu and saved in the RC file, and always can be toggled via the -popup
 782# command line switch.
 783#
 784#USE_SELECT_POPUPS:TRUE
 785
 786
 787.h2 SHOW_CURSOR
 788# SHOW_CURSOR controls whether or not the cursor is hidden or appears
 789# over the current link in documents or the current option in popups.
 790# Showing the cursor is handy if you are a sighted user with a poor
 791# terminal that can't do bold and reverse video at the same time or
 792# at all.  It also can be useful to blind users, as an alternative
 793# or supplement to setting LINKS_AND_FIELDS_ARE_NUMBERED or
 794# LINKS_ARE_NUMBERED.
 795# The default defined here or in userdefs.h can be changed via the
 796# 'o'ptions menu and saved in the RC file, and always can be toggled
 797# via the -show_cursor command line switch.
 798#
 799SHOW_CURSOR:TRUE
 800
 801.h2 UNDERLINE_LINKS
 802# UNDERLINE_LINKS controls whether links are underlined by default, or shown
 803# in bold.  Normally this default is set from the configure script.
 804#
 805#UNDERLINE_LINKS:FALSE
 806
 807.h2 BOLD_HEADERS
 808# If BOLD_HEADERS is set to TRUE the HT_BOLD default style will be acted
 809# upon for <H1> through <H6> headers.  The compilation default is FALSE
 810# (only the indentation styles are acted upon, but see BOLD_H1, below).
 811# On Unix, compilation with -DUNDERLINE_LINKS also will apply to the
 812# HT_BOLD style for headers when BOLD_HEADERS is TRUE.
 813#
 814#BOLD_HEADERS:FALSE
 815
 816
 817.h2 BOLD_H1
 818# If BOLD_H1 is set to TRUE the HT_BOLD default style will be acted
 819# upon for <H1> headers even if BOLD_HEADERS is FALSE.  The compilation
 820# default is FALSE.  On Unix, compilation with -DUNDERLINE_LINKS also
 821# will apply to the HT_BOLD style for headers when BOLD_H1 is TRUE.
 822#
 823#BOLD_H1:FALSE
 824
 825
 826.h2 BOLD_NAME_ANCHORS
 827# If BOLD_NAME_ANCHORS is set to TRUE the content of anchors without
 828# an HREF attribute, (i.e., anchors with a NAME or ID attribute) will
 829# have the HT_BOLD default style.  The compilation default is FALSE.
 830# On Unix, compilation with -DUNDERLINE_LINKS also will apply to the
 831# HT_BOLD style for NAME (ID) anchors when BOLD_NAME_ANCHORS is TRUE.
 832#
 833#BOLD_NAME_ANCHORS:FALSE
 834
 835
 836.h1 Internal Behavior
 837
 838.h2 DEFAULT_CACHE_SIZE
 839.h2 DEFAULT_VIRTUAL_MEMORY_SIZE
 840# The DEFAULT_CACHE_SIZE specifies the number of WWW documents to be
 841# cached in memory at one time.
 842#
 843# This so-called cache size (actually, number) is defined in userdefs.h and
 844# may be modified here and/or with the command line argument -cache=NUMBER
 845# The minimum allowed value is 2, for the current document and at least one
 846# to fetch, and there is no absolute maximum number of cached documents.
 847# On Unix, and VMS not compiled with VAXC, whenever the number is exceeded
 848# the least recently displayed document will be removed from memory.
 849#
 850# On VMS compiled with VAXC, the DEFAULT_VIRTUAL_MEMORY_SIZE specifies the
 851# amount (bytes) of virtual memory that can be allocated and not yet be freed
 852# before previous documents are removed from memory.  If the values for both
 853# the DEFAULT_CACHE_SIZE and DEFAULT_VIRTUAL_MEMORY_SIZE are exceeded, then
 854# the least recently displayed documents will be freed until one or the other
 855# value is no longer exceeded.  The default value is defined in userdefs.h.
 856#
 857# The Unix and VMS (but not VAXC) implementations use the C library malloc's
 858# and calloc's for memory allocation, but procedures for taking the actual
 859# amount of cache into account still need to be developed.  They use only
 860# the DEFAULT_CACHE_SIZE value, and that specifies the absolute maximum
 861# number of documents to cache (rather than the maximum number only if
 862# DEFAULT_VIRTUAL_MEMORY_SIZE has been exceeded, as with VAXC/VAX).
 863#
 864#DEFAULT_CACHE_SIZE:10
 865#DEFAULT_VIRTUAL_MEMORY_SIZE:512000
 866
 867
 868.h2 SOURCE_CACHE
 869# SOURCE_CACHE sets the source caching behavior for Lynx:
 870# FILE causes Lynx to keep a temporary file for each cached document
 871#   containing the HTML source of the document, which it uses to regenerate
 872#   the document when certain settings are changed (for instance,
 873#   historical vs. minimal vs. valid comment parsing) instead of reloading
 874#   the source from the network.
 875# MEMORY is like FILE, except the document source is kept in memory.  You
 876#   may wish to adjust DEFAULT_CACHE_SIZE and DEFAULT_VIRTUAL_MEMORY_SIZE
 877#   accordingly.
 878# NONE is the default; the document source is not cached, and is reloaded
 879#   from the network when needed.
 880#
 881#SOURCE_CACHE:NONE
 882
 883
 884.h2 SOURCE_CACHE_FOR_ABORTED
 885# This setting controls what will happen with cached source for the document
 886# being fetched from the net if fetching was aborted (either user pressed
 887# 'z' or network went down). If set to KEEP, the source fetched so far will
 888# be preserved (and used as cache), if set to DROP lynx will drop the
 889# source cache for that document (i.e. only completely downloaded documents
 890# will be cached in that case).
 891#SOURCE_CACHE_FOR_ABORTED:DROP
 892
 893.h2 ALWAYS_RESUBMIT_POSTS
 894# If ALWAYS_RESUBMIT_POSTS is set TRUE, Lynx always will resubmit forms
 895# with method POST, dumping any cache from a previous submission of the
 896# form, including when the document returned by that form is sought with
 897# the PREV_DOC command or via the history list.  Lynx always resubmits
 898# forms with method POST when a submit button or a submitting text input
 899# is activated, but normally retrieves the previously returned document
 900# if it had links which you activated, and then go back with the PREV_DOC
 901# command or via the history list.
 902#
 903# The default defined here or in userdefs.h can be toggled via
 904# the -resubmit_forms command line switch.
 905#
 906#ALWAYS_RESUBMIT_POSTS:FALSE
 907
 908.h2 TRIM_INPUT_FIELDS
 909# If TRIM_INPUT_FIELDS is set TRUE, Lynx will trim trailing whitespace (e.g.,
 910# space, tab, carriage return, line feed and form feed) from the text entered
 911# into form text and textarea fields.  Older versions of Lynx do this trimming
 912# unconditionally, but other browsers do not, which would yield different
 913# behavior for CGI scripts.
 914#TRIM_INPUT_FIELDS:FALSE
 915
 916.h1 HTML Parsing
 917
 918.h2 NO_ISMAP_IF_USEMAP
 919# If NO_ISMAP_IF_USEMAP is set TRUE, Lynx will not include a link to the
 920# server-side image map if both a server-side and client-side map for the
 921# same image is indicated in the HTML markup.  The compilation default is
 922# FALSE, such that a link with "[ISMAP]" as the link name, followed by a
 923# hyphen, will be prepended to the ALT string or "[USEMAP]" pseudo-ALT for
 924# accessing Lynx's text-based rendition of the client-side map (based on
 925# the content of the associated MAP element).  If the "[ISMAP]" link is
 926# activated, Lynx will send a 0,0 coordinate pair to the server, which
 927# Lynx-friendly sites can map to a for-text-client document, homologous
 928# to what is intended for the content of a FIG element.
 929#
 930# The compilation default, or default defined here, can be toggled via
 931# the "-ismap" command line switch.
 932#
 933#NO_ISMAP_IF_USEMAP:FALSE
 934
 935
 936.h2 SEEK_FRAG_MAP_IN_CUR
 937# If SEEK_FRAG_MAP_IN_CUR is set FALSE, then USEMAP attribute values
 938# (in IMG or OBJECT tags) consisting of only a fragment (USEMAP="#foo")
 939# will be resolved with respect to the current document's base, which
 940# might not be the same as the current document's URL.
 941# The compilation default is to use the current document's URL in all
 942# cases (i.e., assume the MAP is present below, if it wasn't present
 943# above the point in the HTML stream where the USEMAP attribute was
 944# detected).  Lynx's present "single pass" rendering engine precludes
 945# checking below before making the decision on how to resolve a USEMAP
 946# reference consisting solely of a fragment.
 947#
 948#SEEK_FRAG_MAP_IN_CUR:TRUE
 949
 950
 951.h2 SEEK_FRAG_AREA_IN_CUR
 952# If SEEK_FRAG_AREA_IN_CUR is set FALSE, then HREF attribute values
 953# in AREA tags consisting of only a fragment (HREF="#foo") will be
 954# resolved with respect to the current document's base, which might
 955# not be the same as the current document's URL.  The compilation
 956# default is to use the current document's URL, as is done for the
 957# HREF attribute values of Anchors and LINKs that consist solely of
 958# a fragment.
 959#
 960#SEEK_FRAG_AREA_IN_CUR:TRUE
 961
 962
 963.h1 CGI scripts
 964# These settings control Lynx's ability to execute various types of scripts.
 965
 966.h2 LOCAL_EXECUTION_LINKS_ALWAYS_ON
 967.h2 LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE
 968# Local execution links and scripts are by default completely disabled,
 969# unless a change is made to the userdefs.h file to enable them or
 970# the configure script is used with the corresponding options
 971# (--enable-exec-links and --enable-exec-scripts).
 972# See the Lynx source code distribution and the userdefs.h
 973# file for more detail on enabling execution links and scripts.
 974#
 975# If you have enabled execution links or scripts the following
 976# two variables control Lynx's action when an execution link
 977# or script is encountered.
 978#
 979# If LOCAL_EXECUTION_LINKS_ALWAYS_ON is set to TRUE any execution
 980# link or script will be executed no matter where it came from.
 981# This is EXTREMELY dangerous.  Since Lynx can access files from
 982# anywhere in the world, you may encounter links or scripts that
 983# will cause damage or compromise the security of your system.
 984#
 985# If LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE is set to TRUE only
 986# links or scripts that reside on the local machine and are
 987# referenced with a URL beginning with "file://localhost/" or meet
 988# TRUSTED_EXEC or ALWAYS_TRUSTED_EXEC rules (see below) will be
 989# executed.  This is much less dangerous than enabling all execution
 990# links, but can still be dangerous.
 991#
 992LOCAL_EXECUTION_LINKS_ALWAYS_ON:FALSE
 993LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:FALSE
 994
 995
 996.h2 TRUSTED_EXEC
 997# If LOCAL_EXECUTION_LINK_ON_BUT_NOT_REMOTE is TRUE, and no TRUSTED_EXEC
 998# rule is defined, it defaults to "file://localhost/" and any lynxexec
 999# or lynxprog command will be permitted if it was referenced from within
1000# a document whose URL begins with that string.  If you wish to restrict the
1001# referencing URLs further, you can extend the string to include a trusted
1002# path.  You also can specify a trusted directory for http URLs, which will
1003# then be treated as if they were local rather than remote.  For example:
1004#
1005#	TRUSTED_EXEC:file://localhost/trusted/
1006#	TRUSTED_EXEC:http://www.wfbr.edu/trusted/
1007#
1008# If you also wish to restrict the commands which can be executed, create
1009# a series of rules with the path (Unix) or command name (VMS) following
1010# the string, separated by a tab.  For example:
1011#
1012# Unix:
1013# ====
1014#	TRUSTED_EXEC:file://localhost/<tab>/bin/cp
1015#	TRUSTED_EXEC:file://localhost/<tab>/bin/rm
1016# VMS:
1017# ===
1018#	TRUSTED_EXEC:file://localhost/<tab>copy
1019#	TRUSTED_EXEC:file://localhost/<tab>delete
1020#
1021# Once you specify a TRUSTED_EXEC referencing string, the default is
1022# replaced, and all the referencing strings you desire must be specified
1023# as a series.  Similarly, if you associate a command with the referencing
1024# string, you must specify all of the allowable commands as a series of
1025# TRUSTED_EXEC rules for that string.  If you specify ALWAYS_TRUSTED_EXEC
1026# rules below, you need not repeat them as TRUSTED_EXEC rules.
1027#
1028# If EXEC_LINKS and JUMPFILE have been defined, any lynxexec or lynxprog
1029# URLs in that file will be permitted, regardless of other settings.  If
1030# you also set LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:TRUE and a single
1031# TRUSTED_EXEC rule that will always fail (e.g., "none"), then *ONLY* the
1032# lynxexec or lynxprog URLs in JUMPFILE (and any ALWAYS_TRUSTED_EXEC rules,
1033# see below) will be allowed.  Note, however, that if Lynx was compiled with
1034# CAN_ANONYMOUS_JUMP set to FALSE (default is TRUE), or -restrictions=jump
1035# is included with the -anonymous switch at run time, then users of an
1036# anonymous account will not be able to access the jumps file or enter
1037# 'j'ump shortcuts, and this selective execution feature will be overridden
1038# as well (i.e., they will only be able to access lynxexec or lynxprog
1039# URLs which meet any ALWAYS_TRUSTED_EXEC rules).
1040#
1041TRUSTED_EXEC:none
1042
1043
1044.h2 ALWAYS_TRUSTED_EXEC
1045# If EXEC_LINKS was defined, any lynxexec or lynxprog URL can be made
1046# always enabled by an ALWAYS_TRUSTED_EXEC rule for it.  This is useful for
1047# anonymous accounts in which you have disabled execution links generally,
1048# and may also have disabled jumps file links, but still want to allow
1049# execution of particular utility scripts or programs.  The format is
1050# like that for TRUSTED_EXEC.  For example:
1051#
1052# Unix:
1053# ====
1054#   ALWAYS_TRUSTED_EXEC:file://localhost/<tab>/usr/local/kinetic/bin/usertime
1055#   ALWAYS_TRUSTED_EXEC:http://www.more.net/<tab>/usr/local/kinetic/bin/who.sh
1056# VMS:
1057# ===
1058#   ALWAYS_TRUSTED_EXEC:file://localhost/<tab>usertime
1059#   ALWAYS_TRUSTED_EXEC:http://www.more.net/<tab>show users
1060#
1061# The default ALWAYS_TRUSTED_EXEC rule is "none".
1062#
1063ALWAYS_TRUSTED_EXEC:none
1064
1065
1066.h2 TRUSTED_LYNXCGI
1067# Unix:
1068# =====
1069# TRUSTED_LYNXCGI rules define the permitted sources and/or paths for
1070# lynxcgi links (if LYNXCGI_LINKS is defined in userdefs.h).  The format
1071# is the same as for TRUSTED_EXEC rules (see above).  Example rules:
1072#
1073#	TRUSTED_LYNXCGI:file://localhost/
1074# 	TRUSTED_LYNXCGI:<tab>/usr/local/etc/httpd/cgi-bin/
1075# 	TRUSTED_LYNXCGI:file://localhost/<tab>/usr/local/www/cgi-bin/
1076#
1077# VMS:
1078# ====
1079# Do not define this.
1080#
1081# The default TRUSTED_LYNXCGI rule is "none".
1082#
1083TRUSTED_LYNXCGI:none
1084
1085
1086.h2 LYNXCGI_ENVIRONMENT
1087# Unix:
1088# =====
1089# LYNXCGI_ENVIRONMENT adds the current value of the specified
1090# environment variable to the list of environment variables passed on to the
1091# lynxcgi script.  Useful variables are HOME, USER, etc...  If proxies
1092# are in use, and the script invokes another copy of lynx (or a program like
1093# wget) in a subsidiary role, it can be useful to add http_proxy and other
1094# *_proxy variables.
1095#
1096# VMS:
1097# ====
1098# Do not define this.
1099#
1100#LYNXCGI_ENVIRONMENT:
1101
1102
1103.h2 LYNXCGI_DOCUMENT_ROOT
1104# Unix:
1105# =====
1106# LYNXCGI_DOCUMENT_ROOT is the value of DOCUMENT_ROOT that will be passed
1107# to lynxcgi scripts.  If set and the URL has PATH_INFO data, then
1108# PATH_TRANSLATED will also be generated.  Examples:
1109#	LYNXCGI_DOCUMENT_ROOT:/usr/local/etc/httpd/htdocs
1110#	LYNXCGI_DOCUMENT_ROOT:/data/htdocs/
1111#
1112# VMS:
1113# ====
1114# Do not define this.
1115#
1116#LYNXCGI_DOCUMENT_ROOT:
1117
1118
1119.h1 Cookies
1120
1121.h2 FORCE_SSL_COOKIES_SECURE
1122# If FORCE_SSL_COOKIES_SECURE is set to TRUE, then SSL encrypted cookies
1123# received from https servers never will be sent unencrypted to http
1124# servers.  The compilation default is to impose this block only if the
1125# https server included a secure attribute for the cookie.  The normal
1126# default or that defined here can be toggled via the -force_secure
1127# command line switch.
1128#
1129#FORCE_SSL_COOKIES_SECURE:FALSE
1130
1131
1132.h1 Internal Behavior
1133
1134.h2 MAIL_SYSTEM_ERROR_LOGGING
1135#  MAIL_SYSTEM_ERROR_LOGGING will send a message to the owner of
1136#  the information, or ALERTMAIL if there is no owner, every time
1137#  that a document cannot be accessed!
1138#
1139#  NOTE:  This can generate A LOT of mail, be warned.
1140#
1141#MAIL_SYSTEM_ERROR_LOGGING:FALSE
1142
1143
1144.h2 CHECKMAIL
1145# If CHECKMAIL is set to TRUE, the user will be informed (via a statusline
1146# message) about the existence of any unread mail at startup of Lynx, and
1147# will get statusline messages if subsequent new mail arrives.  If a jumps
1148# file with a lynxprog URL for invoking mail is available, or your html
1149# pages include an mail launch file URL, the user thereby can access mail
1150# and read the messages.  The checks and statusline reports will not be
1151# performed if Lynx has been invoked with the -restrictions=mail switch.
1152#
1153# VMS USERS !!!
1154# =============
1155# New mail is normally broadcast as it arrives, via "unsolicited screen
1156# broadcasts", which can be "wiped" from the Lynx display via the Ctrl-W
1157# command.  You may prefer to disable the broadcasts and use CHECKMAIL
1158# instead (e.g., in a public account which will be used by people who
1159# are ignorant about VMS).
1160#
1161#CHECKMAIL:FALSE
1162
1163
1164.h1 News-groups
1165
1166.h2 NNTPSERVER
1167# To enable news reading ability via Lynx, the environment variable NNTPSERVER
1168# must be set so that it points to your site's NNTP server
1169# (see Lynx Users Guide on environment variables).
1170# Lynx respects RFC 1738 (http://www.ics.uci.edu/pub/ietf/uri/rfc1738.txt)
1171# and does not accept a host field in news URLs (use nntp: instead of news: for
1172# the scheme if you wish to specify an NNTP host in a URL, as explained in the
1173# RFC).  If you have not set the variā€¦

Large files files are truncated, but you can click here to view the full file