# lynx.cfg file.
# The default placement for this file is /usr/local/lib/lynx.cfg (UNIX)
#                                     or Lynx_Dir:lynx.cfg (VMS)
#
# Definition pairs are of the form  VARIABLE:DEFINITION
# NO spaces are allowed between the pair items.
#
#  If you do not have access to /usr/local/bin you may change
#  the default location of this file in the userdefs.h file and recompile,
#  or specify it's location on the command line with the "-cfg"
#  command line option.
#
# Items may be commented out by putting a '#' as the FIRST char of the line
#
# All definitions must be flush left and have NO spaces.!!!
#
#
# STARTFILE is the default URL if none is specified on the command line 
# note: these files can be remote (http://www.w3.org/default.html) 
# or local (file://localhost/DIRECTORY/FILENAME
#  replace DIRECTORY with the current directory path and
#  FILENAME with the name of the file.
#  file://localhost/dua#/DIRECTORY/FILENAME on VMS systems.)
#
STARTFILE:http://www.cc.ukans.edu/about_lynx/www_start.html
 
# HELPFILE must be defined as a URL and must have a 
# complete local path name if local 
# (file://localhost/DIRECTORY/FILENAME
#  replace DIRECTORY with the current directory path and
#  FILENAME with the name of the file.
#  file://localhost/dua#/DIRECTORY/FILENAME on VMS systems.)
# the default HELPFILE is:
# http://kufacts.cc.ukans.edu/lynx_help/lynx_help_main.html
# This file will be updated as needed.
#
HELPFILE:http://kufacts.cc.ukans.edu/lynx_help/lynx_help_main.html

# JUMPFILE is the local file checked for shortcut URL's 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 URL's.  See the sample jumps files in the samples
# subdirectory.  Make sure your jumps file includes a '?' shortcut
# for a file://localhost URL to itself:
#
# <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.
#
#JUMPFILE:/Lynx_Dir/jumps.html
 
# DEFAULT_INDEX_FILE is the default file retrieved when the
# user presses the 'I' key when viewing any document.
# An index to your CWIS can be placed here or a document containing
# pointers to lots of interesting places on the web.
#
#DEFAULT_INDEX_FILE:http://www.w3.org/default.html
DEFAULT_INDEX_FILE:http://www.ncsa.uiuc.edu/SDG/Software/Mosaic/MetaIndex.html
 
# The CHARACTER_SET defines the users default 8 bit character set
# which is used to represent the list of character entities within
# HTML. New character sets may be defined by modifying the file
# src/LYCharSets in the Lynx source code distribution and
# recompiling.
# The default character sets include:
#    ISO Latin 1
#    DEC Multinational
#    IBM PC character set
#    NeXT character set
#    7 bit approximations
#
CHARACTER_SET:ISO Latin 1
 
# If BOLD_HEADERS is set to TRUE the HT_BOLD default style will be
# acted upon for <H1> through <H7> headers.  The compilation default
# is FALSE (only the uppercasing and indentation styles are acted
# upon).  On Unix, compilation with -DUNDERLINE_LINKS also will
# apply to the HT_BOLD style for headers when BOLD_HEADERS is TRUE.
#
BOLD_HEADERS:FALSE

# Local execution links and scripts are completely disabled
# in the source code unless they are enabled in the
# userdefs.h file and the sources recompiled.  Please
# see the Lynx source code distribution and the userdefs.h
# file for more detail on enabling execution links and scripts.
#
# If you have enabled execution links or scripts the following
# two variables control Lynx's action when an execution link
# or script is encountered.
#
# If LOCAL_EXECUTION_LINKS_ALWAYS_ON is set to TRUE any execution
# link or script will be executed no matter where it came from.
# This is EXTREMELY dangerous.  Since Lynx can access files from
# anywhere in the world, you may encounter links or scripts that
# will cause damage or comprimise the security of your system.
#
# If LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE is set to TRUE only
# links or scripts that reside on the local machine and are
# referenced with a URL beginning with "file://localhost/" or via
# TRUSTED_EXEC rules (see below) will be executed.  This is much
# less dangerous than enabling all execution links, but can still
# be dangerous.
#
LOCAL_EXECUTION_LINKS_ALWAYS_ON:FALSE
LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:FALSE
 
# If LOCAL_EXECUTION_LINK_ON_BUT_NOT_REMOTE is TRUE, and no TRUSTED_EXEC
# rule is defined, it defaults to "file://localhost/" and any lynxexec
# command will be permitted if it was referenced with a URL beginning with
# that string.  If you wish to restrict the referencing URL's further, you
# can extend the string to include a trusted path.  You also can specify
# a trusted directory for http URL's, which will then be treated as if they
# were local rather than remote.  For example:
#
#	TRUSTED_EXEC:file://localhost/trusted/
#	TRUSTED_EXEC:http://sci.wfeb.edu/trusted/
#
# If you also wish to restrict the commands which can be executed, create
# a series of rules with the path (Unix) or command name (VMS) following
# the string, separated by a tab.  For example:
#
# Unix:
#	TRUSTED_EXEC:file://localhost/	bin/cp
#	TRUSTED_EXEC:file://localhost/	bin/rm
# VMS:
#	TRUSTED_EXEC:file://localhost/	copy
#	TRUSTED_EXEC:file://localhost/	delete
#
# Once you specify a TRUSTED_EXEC referencing string, the default is
# replaced, and all the referencing strings you desire must be specified
# as a series.  Similarly, if you associate a command with the referencing
# string, you must specify all of the allowable commands as a series of
# TRUSTED_EXEC rules for that string.
#
# If EXEC_LINKS and JUMPFILE have been defined, any lynxexec URL's in that
# file will be permitted, regardless of other settings.  If you also set
# LOCAL_EXECUTION_LINKS_ON_BUT_NOT_REMOTE:TRUE and a single TRUSTED_EXEC
# rule that will always fail (e.g., "none"), then *ONLY* the lynxexec URL's
# in JUMPFILE will be allowed.
#
#TRUSTED_EXEC:none

# TRUSTED_LYNXCGI defines where cgi scripts can live (if LYNXCGI_LINKS 
# is defined in userdefs.h). Note that it must be given in order for
# cgi support to work (there is no default path).  For example:
# 
# 	TRUSTED_LYNXCGI:<tab>/usr/local/etc/httpd/cgi-bin/
# 	TRUSTED_LYNXCGI:file://localhost/<tab>/usr/local/www/cgi-bin/
#
#TRUSTED_LYNXCGI:none

# LYNXCGI_ENVIRONMENT adds the current value of the specified
# environment variable to the list of environment variables passed on to the
# lynxcgi script. Useful variables are HOME, USER, EDITOR, etc...
#LYNXCGI_ENVIRONMENT:

#  MAIL_SYSTEM_ERROR_LOGGING will send a message to the owner of 
#  the information, or ALERTMAIL if there is no owner, every time
#  that a document cannot be accessed!
#
#  NOTE: This can generate A LOT of mail, be warned.
#
MAIL_SYSTEM_ERROR_LOGGING:FALSE
 
# If CHECKMAIL is set to TRUE, the user will be informed (via a statusline
# message) about the existence of any unread mail at startup of Lynx, and
# will get statusline messages if subsequent new mail arrives.  If a jumps
# file with a lynxexec URL for invoking mail is available, or your html
# pages include an mail launch file URL, the user thereby can access mail
# and read the messages.  The checks and statusline reports will not be
# performed if Lynx has been invoked with the -restrictions=mail switch.
#
#  VMS USERS !!!
# New mail is normally broadcast as it arrives, via "unsolicitied screen
# broadcasts", which can be "wiped" from the Lynx display via the Ctrl-W
# command.  You may prefer to disable the broadcasts and use CHECKMAIL
# instead (e.g., in a public account which will be used by people who
# are ignorant about VMS).
#
CHECKMAIL:FALSE

# VMS:
#=====
# INEWS is the foreign command for the ANU-NEWS client (normally defined
# as "NEWS" in userdefs.h) which serves as a transparent vector for posting
# to newsgroups from Lynx via the ANU-NEWS client's server.  The account
# running Lynx must have access to the ANU-NEWS client, which in turn must
# have posting privileges (the news server could also be ANU-NEWS, or any
# other server to which the ANU-NEWS client has access).  You can disable
# news posting by setting INEWS to "none", or via -restrictions switches.
# The ANU-NEWS software for VMS is available from ftp.cc.ukans.edu.
#
#INEWS:NEWS

# UNIX:
#======
# Set INEWS to the full path and name of your program for posting to
# newsgroups.  A "mini" inews is included in the utils subdirectory of
# the Lynx distribution.  You can disable news posting by setting INEWS
# to "none", or via -restrictions switches.
# Note that INN may require an -h switch added to the path.
#
#INEWS:inews

# VMS ONLY:
#==========
# If USE_FIXED_RECORDS is set to TRUE, Lynx_Dir:FIXED512.COM will be
# executed automatically to convert 'd'ownloaded binary files to
# FIXED 512 record format before saving them permanently to disk or
# acting on a DOWNLOADER option.  Read the header of FIXED512.COM for
# more information.  If set to FALSE, the headers of such files will
# indicate that they are Stream_LF with Implied Carriage Control, which
# is incorrect, and can cause downloading software to get confused and
# unhappy.
#
#USE_FIXED_RECORDS:TRUE

# VI_KEYS can be turned on by the user in the options
# screen or the .lynxrc file.  This is just the default.
#
VI_KEYS_ALWAYS_ON:FALSE
 
# EMACS_KEYS can be turned on by the user in the options
# screen or the .lynxrc file.  This is just the default.
#
EMACS_KEYS_ALWAYS_ON:FALSE
 
# DEFAULT_KEYPAD_MODE specifies whether by default the user
# has numbers that work like arrows or else numbered links
# DEFAULT KEYPAD MODE may be set to TRUE for
# using numbers as arrows as default or FALSE for
# using numbered links as the default
# 
DEFAULT_KEYPAD_MODE_IS_NUMBERS_AS_ARROWS:TRUE
 
# The default search type.
# This is a default that can be overridden by the user!
#
CASE_SENSITIVE_ALWAYS_ON:FALSE

# DEFAULT_BOOKMARK_FILE is a default filename for use as a
# personal bookmark file.  It should start without a slash
# and will reference a file from the users home directory.
# NOTE: A file ending in .html should be used eliminate potential problems
#
DEFAULT_BOOKMARK_FILE:lynx_bookmarks.html

# DEFAULT_USER_MODE sets the default user mode for Lynx users.
# NOVICE  shows a three line help message at the bottom of the screen
# INTERMEDIATE  shows normal amount of help (one line)
# ADVANCED  help is replaced by the URL of the current link
#
DEFAULT_USER_MODE:NOVICE

# DEFAULT_EDITOR sets the default editor for Lynx users.
# If an editor is defined then the user may edit local documents
# using that editor.  The editor will also be used for sending
# mail messages.  If no editor is defined here or by the user
# the user will not be able to edit local documents and a primative
# line oriented mail input mode will be used.  
# NOTE: Do not define an editor unless you know that every user will
#       know how to use it.  Most users do not enjoy getting stuck in
#       an unknown editor that they can't get out of.  Users can
#       easily define an editor of their own using the options menu,
#       so it is not always desirable to set the DEFAULT_EDITOR.
#
#DEFAULT_EDITOR:

# SYSTEM_EDITOR behaves the same as DEFAULT_EDITOR except that it can't be
# changed.
#
#SYSTEM_EDITOR:

# PREFERRED_LANGUAGE is the language in MIME notation (e.g., "en",
# "fr") which will be indicated by Lynx in its Accept-Language headers
# as the preferred language.  If available, the document will be
# transmitted in that language.  Users can override this setting via
# the 'o'ptions menu and save that preference in their RC file.
#
#PREFERRED_LANGUAGE:en

# Proxy variables
# Lynx version 2.2 and beyond supports the use of proxy servers that can
# act as firewall gateways and caching servers.  They are preferable to
# the older gateway servers.  Each protocol used by Lynx can be mapped
# separately using PROTOCOL_proxy environment variables (see INSTALLATION).
# If you have not set them externally, you can set them at run time via
# this configuration file.  They will not override external settings.
# Note that on VMS they are set as process logicals rather than symbols,
# to preserve lowercasing, and will outlive the Lynx image.
#
#http_proxy:http://some.server.dom:port/
#ftp_proxy:http://some.server.dom:port/
#gopher_proxy:http://some.server.dom:port/
#news_proxy:http://some.server.dom:port/
#wais_proxy:http://some.server.dom:port/
#no_proxy:host.domain.dom

# Printer definitions
# any number of printers may be defined by using multiple 
# printer definition sets.  Printers may be any program
# that could be useful to your users, they do not necessarily
# have to print.
#
# the definition of a printer is of the form
# PRINTER:<printer name>:<printer command>:<printer option>:<lines/page>
#
#    <printer name> is the name that the user will see
# <printer command> is the command line arguments for printing a file
#		    the %s will be replaced with the file being printed.
#                   If a second %s is given the second %s will be replaced by a
#                   suggested filename that is prettier than the tempfile
#                   name given in the first %s.  This does not remove the first
#                   %s from the command line in any manner.  If you need to
#                   use only the second %s file name in your printer command,
#                   then I suggest creating a script which will first copy the
#                   first %s file name to the second %s file name, and then
#                   executing your print command with the second %s file name.
#  <printer option> specifies whether the printer should be disabled for
#		    users without printing options.  The options are
#		    TRUE or FALSE;
#		    TRUE means the printer will always be ENABLED
#			 regardless of printer or anonymous settings
#		    FALSE means the printer will be DISABLED when
#			  the -noprint option is on, or for anonymous
#			  users which are not allowed to print
#
#  <lines/page>    is an optional parameter for indicating the number of
#		   lines per page for the printer.  Defaults to 66.  Used
#		   for computing the approximate number of pages and
#		   generating a statusline query of whether to proceed if
#		   the document is longer than 4 printer pages.  Uses the
#		   current screen length for the computation when the
#		   built in "print to screen" option is selected.
#
#  You must put the whole definition on one line.  
#
#  If you must use a colon, precede it with a backslash!
#
#  If you have a very busy VMS print queue and Lynx deletes the temporary
#  files before they have been queued, use the VMSPrint.com included in
#  the distribution.
#
#    examples
#PRINTER:Computer Center printer:lpr -Pccprt %s:FALSE
#PRINTER:Office printer:lpr -POffprt %s:TRUE
#PRINTER:VMS printer:print /queue=cc$print %s:FALSE:58
#PRINTER:Busy VMS printer:@Lynx_Dir\:VMSPrint sys$print %s:FALSE:58
#
# check out the lpansi program in utils/ for printing on vt100
# attached printers.
#PRINTER:Use vt100 print sequence to print from your local terminal:lpansi %s:TRUE
# don't use the following printer on anonymous accounts since
# allowing shell input is very dangerous
#PRINTER:Specify your own print command:echo -n "Enter a print command\: "; read word; sh -c "$word %s":FALSE

# Downloader definitions
# any number of downloaders may be defined by using multiple
# downloader definition sets.  Downloaders may be any program
# that could be useful to your users, they do not necessarily
# have to be a download protocol program. The most common use
# of a downloader is to use Ckermit or some other transfer
# program so that the user may easily transfer files back to
# their local machine over a serial link.
#
# the definition of a downloader is of the form
# DOWNLOADER:<downloadername>:<downloader command>:<downloader option>
#
#    <downloader name> is the name that the user will see
# <downloader command> is the command line arguments for printing a file
#                      the %s will be replaced with the file being printed
#                      If a second %s is given the second %s will be replaced
#                      by a suggested filename that is nicer than the tempfile
#                      name given in the first %s.  This does not replace the
#                      first %s in the command line.  If your command needs
#                      the suggest file name on the command line only, then
#                      I suggest creating a script that will first copy the
#                      first %s file name to the second %s file name, and then
#                      execute the downloading command using the second %s file
#                      name (e.g., 'sz' needs such a script interposed).
#  <downloader option> specifies whether the downloader should be disabled for
#                      anonymous users.  The options are
#                      TRUE or FALSE;
#                      TRUE means the downloader will always be ENABLED
#                           regardless of the anonymous settings
#                      FALSE means the downloader will be DISABLED when
#                            the user is anonymous.
#
#  You must put the whole definition on one line.
#
#  If you must use a colon, precede it with a backslash!
#
#    examples
#DOWNLOADER:Use Kermit to download to the local terminal:kermit -i -s %s %s:TRUE
#DOWNLOADER:Use Zmodem to download to the local terminal:sz %s:TRUE

# Uploader definitions (implemented only with Unix DIRED_SUPPORT;
#                       see the Makefile in the top directory)
# any number of uploaders may be defined by using multiple
# uploader definition sets.  Uploaders may be any program
# that could be useful to your users, they do not necessarily
# have to be an upload protocol program. The most common use
# of an uploader is to use Ckermit or some other transfer
# program so that the user may easily transfer files from
# their local machine over a serial link.
#
# the definition of an uploader is of the same form as a downloader
# UPLOADER:<uploadername>:<uploader command>:<uploader option>
#
#  You must put the whole definition on one line.
#
#  If you must use a colon, precede it with a backslash!
#
#    example
#UPLOADER:Use Kermit to upload from your computer: kermit -i -r -a %s:TRUE

# If NO_DOT_FILES is TRUE, the user will not be allowed to specify files
# beginning with a dot in reply to output filename prompts.
#
# On VMS, it also will stop inclusion of files beginning with a dot
# (e.g., file://localhost/device/directory/.lynxrc) in the directory
# browser's listings (they are never included on Unix).
#
#NO_DOT_FILES:FALSE

# MIME types and viewers!
#
# file extensions may be assigned to MIME types using
# the SUFFIX: definition.  
#
# The SUFFIX definition takes the form of:
#    SUFFIX:<file extension>:<mime type>
# for instance the following definition maps the
# extension ".gif" to the mime type "image/gif"
#    SUFFIX:.gif:image/gif
#
# file suffixes are case INsensitive!
#
# 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.

#SUFFIX:.ps:application/postscript
#SUFFIX:.eps:application/postscript
#SUFFIX:.ai:application/postscript
#SUFFIX:.rtf:application/x-rtf
#SUFFIX:.snd:audio/basic
#SUFFIX:.gif:image/gif
#SUFFIX:.rgb:image/x-rgb
#SUFFIX:.pict:image/x-pict
#SUFFIX:.xbm:image/x-xbm
#SUFFIX:.tiff:image/x-tiff
#SUFFIX:.jpg:image/jpeg
#SUFFIX:.jpeg:image/jpeg
#SUFFIX:.mpg:video/mpeg
#SUFFIX:.mpeg:video/mpeg
#SUFFIX:.mov:video/quicktime
#SUFFIX:.hqx:application/octet-stream
#SUFFIX:.bin:application/octet-stream
#SUFFIX:.exe:application/octet-stream
#SUFFIX:.tar:application/octet-stream
#SUFFIX:.Z:application/octet-stream
#SUFFIX:.gz:application/octet-stream
#SUFFIX:.zip:application/octet-stream
#SUFFIX:.lzh:application/octet-stream
#SUFFIX:.lha:application/octet-stream
#SUFFIX:.dms:application/octet-stream

# The global and personal EXTENSION_MAP files allow you to assign extensions
# to MIME types which will overide any of the suffix maps in this (lynx.cfg)
# configuration file, or in src/HTInit.c.  See the example mime.types file
# in the samples subdirectory.
#
# 	Unix:
#GLOBAL_EXTENSION_MAP:/usr/local/lib/mosaic/mime.types
# 	VMS:
#GLOBAL_EXTENSION_MAP:Lynx_Dir:mime.types
#
#	Unix (sought in user's home directory):
#PERSONAL_EXTENSION_MAP:.mime.types
#	VMS (sought in user's sys$login directory):
#PERSONAL_EXTENSION_MAP:mime.types

# MIME types may be assigned to external viewers using
# the VIEWER definition.
#
# Note: if you do not define a viewer to a new MIME type
#       that you assigned above then it will be saved to
#       disk by default.
#
# The VIEWER definition takes the form of:
#    VIEWER:<mime type>:<viewing command>[:environment]
#      where -mime type is the MIME content type of the file
#	     -viewing command is a system command that can be
#             used to display the file where "%s" is replaced
#             within the command with the physical filename
#             (i.e. "xv %s" becomes "xv /tmp/tempgiffile")
#            -environment is optional.  The only valid keywords
#             are currently XWINDOWS and NON_XWINDOWS.  If the XWINDOWS 
#             environment is specified then the viewer will only be
#             defined when the user has the environment variable DISPLAY
#             (DECW$DISPLAY on VMS) defined.  If the NON_XWINDOWS environment
#             is specified the specified viewer will only be defined when the
#             user DOES NOT have the environment variable DISPLAY defined.
#  examples:
#		VIEWER:image/gif:xv %s:XWINDOWS
#               VIEWER:image/gif:ascii-view %s:NON_XWINDOWS
#               VIEWER:application/start-elm:elm
#
# The MIME_type:viewer:XWINDOWS definitions listed here in the lynx.cfg
# file are among those established via src/HTInit.c.  For the image types,
# HTInit.c uses the XLOADIMAGE definition in userdefs.h (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.

#VIEWER:application/postscript:ghostview %s&:XWINDOWS
#VIEWER:image/gif:xv %s&:XWINDOWS
#VIEWER:image/x-xbm:xv %s&:XWINDOWS
#VIEWER:image/x-rgb:xv %s&:XWINDOWS
#VIEWER:image/x-tiff:xv %s&:XWINDOWS
#VIEWER:image/jpeg:xv %s&:XWINDOWS
#VIEWER:video/mpeg:mpeg_play %s &:XWINDOWS

# The global and personal MAILCAP files allow you to specify external
# viewers to spawned when Lynx encounters different MIME types, which
# will overide any of the suffix maps in this (lynx.cfg) configuration
# file, or in src/HTInit.c.  See RFC-MAILCAP.txt in the docs subdirectory
# and the example mailcap file in the samples subdirectory.
#
#	Unix:
#GLOBAL_MAILCAP:/usr/local/lib/mosaic/mailcap
#	VMS:
#GLOBAL_MAILCAP:Lynx_Dir:mailcap
#
# 	Sought in user's home (Unix) or sys$login (VMS) directory.
#PERSONAL_MAILCAP:.mailcap

# Key remapping definitions!
#
# You may redefine the keymapping of any function in Lynx by
# using the KEYMAP variable.  The form of KEYMAP is:
#  KEYMAP:<KEYSTROKE>:<LYNX FUNCTION>
#
# You must map upper and lowercase key's separately.
#
# A complete list of functions mapped to their default keys are
# provided below.  All of the mappings are commented out by default
# since they just map to the default mappings, except for TOGGLE_HELP
# (see below).
#
# Special keys map to:
#         Up Arrow: 0x80
#       Down Arrow: 0x81
#      Right Arrow: 0x82
#       Left Arrow: 0x83
#        Page Down: 0x84
#          Page Up: 0x85
#      Keypad Home: 0x86
#       Keypad End: 0x87
#   Function key 1: 0x88
# vt100   Help Key: 0x88
# vt100     Do Key: 0x89
# vt100   Find Key: 0x8A
# vt100 Select Key: 0x8B
# vt100 Insert Key: 0x8C
# vt100 Remove Key: 0x8D
#         NULL KEY: 0x00
#

#KEYMAP:0x2F:SOURCE	# Toggle source viewing mode (show HTML source
#KEYMAP:^R:RELOAD	# Reload the current document and redisplay
#KEYMAP:q:QUIT		# Ask the user to quit
#KEYMAP:Q:ABORT		# Quit without verification
#KEYMAP:0x20:NEXT_PAGE	# Move down to previous page
#KEYMAP:-:PREV_PAGE	# Move up to previous page
#KEYMAP:^P:UP_TWO	# Move display up two lines
#KEYMAP:0x8C:UP_TWO     # Function key - Move display up two lines
#KEYMAP:^N:DOWN_TWO	# Move display down two lines
#KEYMAP:0x8D:DOWN_TWO   # Function key - Move display down two lines
#KEYMAP:^W:REFRESH	# Refresh the screen
#KEYMAP:0x86:HOME   	# Keypad HOME (Go to top of current document
#KEYMAP:0x8A:HOME       # Function key - HOME (Go to top of current document
#KEYMAP:0x87:END	# Keypad END (Go to bottom of current document
#KEYMAP:0x8B:END        # Function key - END (Go to bottom of current document
#KEYMAP:0x80:PREV_LINK  # Move to the previous link
#KEYMAP:0x81:NEXT_LINK  # Move to the next link
#KEYMAP:0x00:UP_LINK    # Move to the link above
#KEYMAP:0x00:DOWN_LINK	# Move to the link below
#KEYMAP:0x00:RIGHT_LINK	# Move to the link to the right
#KEYMAP:0x00:LEFT_LINK	# Move to the link to the left
#KEYMAP:0x7f:HISTORY    # Show the history list
#KEYMAP:0x08:HISTORY    # Show the history list
#KEYMAP:0x83:PREV_DOC	# Return to the previous document
#KEYMAP:0x82:ACTIVATE	# Select the current link
#KEYMAP:0x89:ACTIVATE   # Function key - Select the current link
#KEYMAP:g:GOTO		# Goto a random URL
#KEYMAP:H:HELP		# Show default help screen
#KEYMAP:0x88:HELP       # Function key - Show default help screen
#KEYMAP:i:INDEX		# Show default index
#*** Edit FORM_LINK_SUBMIT_MESSAGE in userdefs.h if you change RESUBMIT ***
#KEYMAP:x:RESUBMIT	# Force resubmission of form if presently cached
#*** Do not change INTERRUPT from 'z' & 'Z' ***
#KEYMAP:z:INTERRUPT	# Interrupt network transmission
#KEYMAP:m:MAIN_MENU	# Return to the main menu
#KEYMAP:o:OPTIONS	# Show the options menu
#KEYMAP:i:INDEX_SEARCH	# Search a server based index
#KEYMAP:/:WHEREIS	# Find a string within the current document
#KEYMAP:n:NEXT		# Find next occurance of string within document
#KEYMAP:c:COMMENT	# Comment to the author of the current document
#KEYMAP:e:EDIT		# Edit current document
#KEYMAP:=:INFO		# Show info about current document
#KEYMAP:p:PRINT		# Show print options
#KEYMAP:a:ADD_BOOKMARK	# Add current document to bookmark list
#KEYMAP:v:VIEW_BOOKMARK	# View the bookmark list
#KEYMAP:!:SHELL		# Spawn default shell
#KEYMAP:d:DOWNLOAD	# Download current link
#KEYMAP:j:JUMP		# Jump to a predefined target
#KEYMAP:k:KEYMAP	# Display the current key map
#KEYMAP:0x00:DO_NOTHING	# Does nothing (ignore this key)

# If TOGGLE_HELP is mapped, in novice mode the second help menu line
# can be toggled among NOVICE_LINE_TWO_A, _B, and _C, as defined in
# userdefs.h.  Otherwise, it will be NOVICE_LINE_TWO.
#
#KEYMAP:O:TOGGLE_HELP	# Show other commands in the novice help menu
