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