snapshot of project "lynx", label v2-8-2dev_23

1 files changed, 50 insertions, 32 deletions

diff --git a/lynx.cfg b/lynx.cfg
index 3161094c..c35ad97b 100644
--- a/lynx.cfg
+++ b/lynx.cfg
@@ -40,15 +40,18 @@
 #                or local, e.g. file://localhost/PATH_TO/FILENAME ,
 #           where PATH_TO is replaced with the complete path to FILENAME
 #           using Unix shell syntax and including the device on VMS.
-# The default offered for ordinary users is their current directory:
-STARTFILE:.
 #
-# *** NBB *** System administrators with ANONYMOUS USERS !!!
-#   set STARTFILE to a REMOTE FILE by uncommenting the next line:
-#STARTFILE:http://lynx.browser.org/
-#   and commenting out the default offered above;
-#   you may, of course, choose to replace `lynx.browser.org'
-#   with another remote/local file which you know to be safe.
+# Normally we expect you will connect to a remote site, e.g., the Lynx starting
+# site:
+STARTFILE:http://lynx.browser.org/
+#
+# As an alternative, you may want to use a local URL.  A good choice for this is
+# the user's home directory: 
+#STARTFILE:file://localhost/~/ 
+#
+# Your choice of STARTFILE should reflect your site's needs, and be a URL that
+# you can connect to reliably.  Otherwise users will become confused and think
+# that they cannot run Lynx.
 
 # HELPFILE must be defined as a URL and must have a
 # complete path if local:
@@ -89,30 +92,28 @@ DEFAULT_INDEX_FILE:http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html
 #
 #JUMP_PROMPT:Jump to (use '?' for list):
 
-# JUMPFILE is the default local file checked for shortcut URLs when
-# the user presses the 'J' (JUMP) key.  The user will be prompted for
-# a shortcut entry (analogously to 'g'oto), and can enter one
-# or use '?' for a list of the shortcuts with associated links to
-# their actual URLs.  See the jumps files in the lynx*/samples
-# subdirectory.  Make sure your jumps file includes a '?' shortcut
-# for a file://localhost URL to itself:
-#
+# JUMPFILE is the local file checked for short-cut names for URLs
+# when the user presses the 'j' (JUMP) key.  The user will be prompted
+# to enter a short-cut name for an URL, which Lynx will then follow
+# in a similar manner to 'g'oto; alternatively, s/he can enter '?'
+# to view the full JUMPFILE list of short-cuts with associated URLs.
+# There is an example jumps file in the samples subdirectory.
+# If not defined here or in  userdefs.h , the JUMP command will invoke
+# the NO_JUMPFILE statusline message (cp  LYMessages_en.h ).
+#
+# To allow '?' to work, include in the JUMPFILE
+# a short-cut to the JUMPFILE itself, e.g.
 # <dt>?<dd><a href="file://localhost/path/jumps.html">This Shortcut List</a>
 #
-# If not defined here or in userdefs.h, the JUMP command will invoke
-# the NO_JUMPFILE statusline message (see userdefs.h).
-#
 # On VMS, use Unix SHELL syntax (including a lead slash) to define it.
 #
-# Do not include "file://localhost" in the definition.
-#
-# Additional alternate jumps files can be defined and mapped to
-# keystrokes at the bottom of lynx.cfg, but you should first define
-# the default jumps file (mapped by default to 'J', and to 'j' when
-# the "VI keys" 'o'ption is not ON) here or in userdefs.h, if you
-# wish to implement the jumps mechanism.
+# Additional jumps files can be defined and mapped to keystrokes
+# in  lynx.cfg , but you should first define the default jumps file,
+# which is mapped by default to 'j' (or 'J' when VI keys are ON).
 #
-#JUMPFILE:/Lynx_Dir/jumps.html
+# In the following line, include the actual full local path to JUMPFILE,
+# but do not include 'file://localhost' in the line.
+#JUMPFILE:/FULL_LOCAL_PATH/jumps.html
 
 # Set JUMPBUFFER to TRUE if you want to have the previous jump target,
 # if any, offered for reuse or editing when using the 'J'ump command.
@@ -1380,8 +1381,20 @@ MINIMAL_COMMENTS:TRUE
 # MIME types and viewers!
 #
 # file extensions may be assigned to MIME types using
-# the SUFFIX: definition.  [This has an effect for ftp and local files only,
-# http server does specify MIME type in the Content-Type header].
+# the SUFFIX: definition.
+#
+# NOTE: It is normally preferable to define new extension mappings in
+#       EXTENSION_MAP files (see below) instead of here:  Definitions
+#       here are overriden by those in EXTENSION_MAP files and even by
+#       some built-in defaults in src/HTInit.c.
+#       Extension mappings have an effect mostly for ftp and local files,
+#       they are NOT used to determine the type of content for URLs with
+#       the http protocol.  This is because HTTP servers already specify
+#       the MIME type in the Content-Type header.  [It may still be
+#       necessary to set up an appropriate suffix for some MIME types,
+#       even if they are accessed only via the HTTP protocol, if the viewer
+#       (see below) for those MIME types requires a certain suffix for the
+#       temporary file passed to it.]
 #
 # The SUFFIX definition takes the form of:
 #    SUFFIX:<file extension>:<mime type>
@@ -1394,7 +1407,8 @@ MINIMAL_COMMENTS:TRUE
 # The suffix definitions listed here in the default lynx.cfg file are
 # among those established via src/HTInit.c.  You can change any of the
 # defaults by editing that file, or via the global or personal mime.types
-# files at run time.  They will be overridden if you assign them here.
+# files at run time.  Assignments made here will be overridden by entries
+# in those files.
 #
 #SUFFIX:.ps:application/postscript
 #SUFFIX:.eps:application/postscript
@@ -1479,6 +1493,10 @@ MINIMAL_COMMENTS:TRUE
 # NOTE: if you do not define a viewer to a new MIME type
 #       that you assigned above then it will be saved to
 #       disk by default.
+#       It is normally preferable to define new viewers in
+#       MAILCAP files (see below) instead of here:  Definitions
+#       here are overridden by those in MAILCAP files and even
+#       by some built-in defaults in src/HTInit.c.
 #
 # The VIEWER definition takes the form of:
 #    VIEWER:<mime type>:<viewer command>[:environment]
@@ -1507,8 +1525,8 @@ MINIMAL_COMMENTS:TRUE
 # file are among those established via src/HTInit.c.  For the image types,
 # HTInit.c uses the XLOADIMAGE_COMMAND definition in userdefs.h or above
 # (open is used for NeXT).  You can change any of these defaults via the
-# global or personal mailcap files at run time.  They will be overridden
-# if you assign them here.
+# global or personal mailcap files.  Assignments made here will be overridden
+# by entries in those files.
 #
 #VIEWER:application/postscript:ghostview %s&:XWINDOWS
 #VIEWER:image/gif:xli %s&:XWINDOWS