lynx-dev patch to add description of extended INCLUDE syntax to lynx.cfg

[Vlad Harchev]

  This patch adds description of extended INCLUDE syntaxt to lynx.cfg and also 
adds a version to htmlized description of settings (it's to pre9).
  Please check my English.

 Best regards,
  -Vlad

--- lynx.cfg-orig       Mon May  3 15:41:30 1999
+++ lynx.cfg    Sun May 30 18:12:49 1999
@@ -15,6 +15,10 @@
 #
 # All definitions must be flush left and have NO spaces.!!!
 #
+# The htmlized description of all settings (based on comments in this file, 
+# with alphabetical table of settings and with table of setings by category) 
+# is availble at http://www.hippo.ru/~hvv/lynxcfg_toc.html
+# 
 #
 # Starting with Lynx 2.8.1, the lynx.cfg file has a crude "include"
 # facility.  This means that you can take advantage of the global lynx.cfg
@@ -32,6 +36,29 @@
 #INCLUDE:/usr/local/lib/lynx.cfg
 #       ^^^^^^^^^^^^^^^^^^^^^^^ or whatever is appropriate on your system
 #and now your own tweaks.
+#
+# Starting from Lynx 2.8.2 INCLUDE facility became yet more powerful. It's 
+# possible to reduce the set of settings that will be read from included file. 
+# Such facility allows sysadmins to provide users in their systems additional 
+# ability to control lynx by the set of options considered secure - like COLOR,
+# VIEWER, KEYMAP.
+# The syntax is
+# INCLUDE:filename for <space-separated-list-of-allowed-settings>
+# sample:
+#INCLUDE:~/lynx.cfg for COLOR VIEWER KEYMAP
+# only one space character should surround the word 'for'. On unix systems ':'
+# is also accepted as separator, eg the following example can be rewritten as
+#INCLUDE:~/lynx.cfg:COLOR VIEWER KEYMAP
+# In this example, only settings COLOR,VIEWER,KEYMAP will be accepted by lynx, 
+# other settings will be ignored. Note: INCLUDE is also treated as setting, so
+# to allow included file to include any files, put INCLUDE in the list of
+# allowed settings.
+# If it's allowed for included file to include other files, and if the set of
+# allowed settings is specified in that file with INCLUDED command, nested file
+# will be allowed to include the set of settings that is set AND of settings
+# allowed for included file and of settings allowed by nested INCLUDE command
+# (ie there is no security hole in including user-defined configuration file 
+# if a set of allowed settings is secure).
 
 # STARTFILE is the default starting URL if none is specified
 #   on the command line or via a WWW_HOME environment variable;