# These settings control the ability of Lynx to invoke various programs for # the user.
# If DEFAULT_EDITOR is defined, users may edit local documents with it # & it 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 primitive line-oriented mail-input mode will be used. # # For sysadmins: do not define a default editor # unless you know EVERY user will know how to use it; # users can easily define their own editor in the Options Menu. # #DEFAULT_EDITOR: DEFAULT_EDITOR:sensible-editor
# SYSTEM_EDITOR behaves the same as DEFAULT_EDITOR, # except that it can't be changed by users. # #SYSTEM_EDITOR: # # If POSITIONABLE_EDITOR is defined once or multiple times and if the same # editor is used as editor in lynx, lynx will use its features, i.e., adding an # option to set the initial line-position, when editing files and textarea. # The commented editors below are already known; there is no need to uncomment # them. # #POSITIONABLE_EDITOR:emacs #POSITIONABLE_EDITOR:jed #POSITIONABLE_EDITOR:jmacs #POSITIONABLE_EDITOR:joe #POSITIONABLE_EDITOR:jove #POSITIONABLE_EDITOR:jpico #POSITIONABLE_EDITOR:jstar #POSITIONABLE_EDITOR:nano #POSITIONABLE_EDITOR:pico #POSITIONABLE_EDITOR:rjoe #POSITIONABLE_EDITOR:vi
# PRINTER, DOWNLOADER & UPLOADER DEFINITIONS: # Lynx has 4 pre-defined print options & 1 pre-defined download option, # which are called up on-screen when `p' or `d' are entered; # any number of options can be added by the user, as explained below. # Uploaders can be defined only for UNIX with DIRED_SUPPORT: # see the Makefile in the top directory & the header of src/LYUpload.c . # # For `p' pre-defined options are: `Save to local file', `E-mail the file', # `Print to screen' and `Print to local printer attached to vt100'. # `Print to screen' allows file transfers in the absence of alternatives # and is often the only option allowed here for anonymous users; # the 3rd & 4th options are not pre-defined for DOS/WINDOWS versions of Lynx. # For `d' the pre-defined option is: `Download to local file'. # # To define your own print or download option use the following formats: # # PRINTER:<name>:<command>:<option>:<lines/page>[:<environment>] # # DOWNLOADER:<name>:<command>:<option>[:<environment>] # # <name> is what you will see on the print/download screen. # # <command> is the command your system will execute: # the 1st %s in the command will be replaced # by the temporary filename used by Lynx; # a 2nd %s will be replaced by a filename of your choice, # for which Lynx will prompt, offering a suggestion. # On Unix, which has pipes, you may use a '|' as the first # character of the command, and Lynx will open a pipe to # the command. # If the command format of your printer/downloader requires # a different layout, you will need to use a script # (see the last 2 download examples below). # # <option> TRUE : the printer/downloader will always be ENABLED, # except that downloading is disabled when -validate is used; # FALSE : both will be DISABLED for anonymous users # and printing will be disabled when -noprint is used. # # <lines/page> (printers: optional) the number of lines/page (default 66): # used to compute the approximate output size # and prompt if the document is > 4 printer pages; # it uses current screen length for the computation # when `Print to screen' is selected. # # [:<environment>] # optional, if XWINDOWS then printer/downloader will be # enabled if DISPLAY environment variable IS defined and # disabled otherwise, if environment is NON_XWINDOWS # then printer/downloader will be enabled if DISPLAY # environment variable IS NOT defined and disabled otherwise, # for anything else or if environment is not specified # printer/downloader is always enabled. # # You must put the whole definition on one line; # if you use a colon, precede it with a backslash. # # `Printer' can be any file-handling program you find useful, # even if it does not physically print anything. # # Usually, down/up-loading involves the use of (e.g.) Ckermit or ZModem # to transfer files to a user's local machine over a serial link, # but download options do not have to be download-protocol programs. # # Printer examples: # # 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 # 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: # # Example: #PRINTER:Busy VMS printer:@Lynx_Dir\:VMSPrint sys$print %s:FALSE:58 # To specify a print option at run-time: # NBB if you have ANONYMOUS users, DO NOT allow this option! # # Example: #PRINTER:Specify at run-time:echo -n "Enter a print command\: "; read word; sh -c "$word %s":FALSE # To pass to a sophisticated file viewer: -k suppresses invocation # of hex display mode if 8-bit or control characters are present; # +s invokes secure mode (see ftp://space.mit.edu/pub/davis/most): # # Example: #PRINTER:Use Most to view:most -k +s %s:TRUE:23 # # Downloader examples: # in Kermit, -s %s is the filename sent, -a %s the filename on arrival # (if they are given in reverse order here, the command will fail): # # Example: #DOWNLOADER:Use Kermit to download to the terminal:kermit -i -s %s -a %s:TRUE # NB don't use -k with Most, so that binaries will invoke hexadecimal mode: # # Example: #DOWNLOADER:Use Most to view:most +s %s:TRUE # The following example gives wrong filenames # (`sz' doesn't support a suggested filename parameter): # # Example: #DOWNLOADER:Use Zmodem to download to the local terminal:sz %s:TRUE # The following example returns correct filenames # by using a script to make a subdirectory in /tmp, # but may conflict with very strong security or permissions restrictions: # # Example: #DOWNLOADER:Use Zmodem to download to the local terminal:set %s %s;td=/tmp/Lsz$$;mkdir $td;ln -s $1 $td/"$2";sz $td/"$2";rm -r $td:TRUE # # Examples: #UPLOADER:Use Kermit to upload from your computer: kermit -i -r -a %s:TRUE #UPLOADER:Use Zmodem to upload from your computer: rz %s:TRUE # # Note for OS/390: /* S/390 -- gil -- 1464 */ # The following is strongly recommended to undo ASCII->EBCDIC conversion. # # Example: #DOWNLOADER:Save OS/390 binary file: iconv -f IBM-1047 -t ISO8859-1 %s >%s:FALSE DOWNLOADER:<BR> Open in GUI [generic `open this' command]:thunar %s:TRUE
# file extensions may be assigned to MIME types using # 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 overridden by those in EXTENSION_MAP files and even by # some built-in defaults in src/HTInit.c. On the other hand, # definitions here allow some more fields that are not possible # in those files. # # 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 global and personal EXTENSION_MAP files allow you to assign extensions # to MIME types which will override 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 PERSONAL_EXTENSION_MAP:~/.lynx/mime.types
# With SUFFIX_ORDER the precedence of suffix mappings can be changed.
# Two kinds of settings are recognized:
#
# PRECEDENCE_OTHER or PRECEDENCE_HERE
# Suffix mappings can come from four sources: (1) SUFFIX rules
# given here - see below, (2) builtin defaults (HTInit.c), and the
# (3) GLOBAL_EXTENSION_MAP and (4) PERSONAL_EXTENSION_MAP files.
# The order of precedence is normally as listed: (1) has the
# *lowest*, (4) has the *highest* precedence if there are conflicts.
# In other words, SUFFIX mappings here are overridden by conflicting
# ones elsewhere. This default ordering is called PRECEDENCE_OTHER.
# With PRECEDENCE_HERE, the order becomes (2) (3) (4) (1), i.e.
# mappings here override others made elsewhere.
#
# NO_BUILTIN
# This disables all builtin default rules. In other words, (2) in the
# list above is skipped. Some recognition for compressed files (".gz",
# ".Z") is still hardwired. A mapping for some basic types, at least
# for text/html is probably necessary to get a usable configuration,
# it can be given in a SUFFIX rule below or an extension map file.
# Both kinds of settings can be combined, separated by comma as in
# SUFFIX_ORDER:PRECEDENCE_HERE,NO_BUILTIN
# Note: Using PRECEDENCE_HERE has only an effect on SUFFIX rules that follow.
# Moreover, if GLOBAL_EXTENSION_MAP or PERSONAL_EXTENSION_MAP directives
# are used, they should come *before* a SUFFIX_ORDER:PRECEDENCE_HERE.
#
#SUFFIX_ORDER:PRECEDENCE_OTHER
# The SUFFIX definition takes the form of: # # SUFFIX:<file extension>:<mime type>:<encoding>:<quality>:<description> # # All fields after <mime type> are optional (including the separators # if no more fields follow). # # <file extension> trailing end of file name. This need not strictly # be a file extension as understood by the OS, a dot # has to be given explicitly if it is indented, for # some uses one could even match full filenames here. # In addition, two forms are special: "*.*" and "*" # refer to the defaults for otherwise unmatched files # (the first for filenames with a dot somewhere in # the name, the second without), these are currently # mapped to text/plain in the (HTInit.c) builtin code. # # <mime type> a MIME content type. It can also contain a charset # parameter, see example below. This should be given in # all lowercase, use <description> for more fancy labels. # It can be left empty if an HTTP style encoding is given. # # Fields in addition to the usual ones are # # <encoding> either a mail style trivial encoding (7bit, 8bit, binary) # which could be used on some systems to determine how to # open local files (currently it isn't), and is used to # determine transfer mode for some FTP URLs; or a HTTP style # content encoding (gzip (equivalent to x-gzip), compress) # # <quality> a floating point quality factor, usually between 0.0 and 1.0 # currently unused in most situations. # # <description> text that can appear in FTP directory listings, and in # local directory listings (see LIST_FORMAT, code %t) # # For instance the following definition maps the # extension ".gif" to the mime type "image/gif" # # Example: # SUFFIX:.gif:image/gif # # The following can be used if you have a convention to label # HTML files in some character set that differs from your local # default (see also ASSUME_LOCAL_CHARSET) with a different # extension, here ".html-u8". It also demonstrates use of the # description field, note extra separators for omitted fields: # # Example: # SUFFIX:.html-u8:text/html;charset=utf-8:::UTF-8 HTML # # The following shows how a suffix can indicate a combination # of MIME type and compression method. (The ending ".ps.gz" should # already be recognized by default; the form below could be used on # systems that don't allow more than one dot in filenames.) # # Example: # SUFFIX:.ps_gz:application/postscript:gzip::gzip'd Postscript # # The following is meant to match a full filename (but can match # any file ending in "core", so be careful): # # Example: # SUFFIX:core:application/x-core-file # # file suffixes are case INsensitive! # # The suffix definitions listed here in the default lynx.cfg file are # similar to those normally established via src/HTInit.c. You can change # the defaults by editing that file or disable them, or via the global or # personal mime.types files at run time (except for the additional fields). # Assignments made here are overridden by entries in those files # unless preceded with a SUFFIX_ORDER:PRECEDENCE_HERE. # # # Examples: #SUFFIX:.ps:application/postscript #SUFFIX:.eps:application/postscript #SUFFIX:.ai:application/postscript #SUFFIX:.rtf:application/rtf #SUFFIX:.snd:audio/basic #SUFFIX:.gif:image/gif #SUFFIX:.rgb:image/x-rgb #SUFFIX:.png:image/png #SUFFIX:.xbm:image/x-xbitmap #SUFFIX:.tiff:image/tiff #SUFFIX:.jpg:image/jpeg #SUFFIX:.jpeg:image/jpeg #SUFFIX:.mpg:video/mpeg #SUFFIX:.mpeg:video/mpeg #SUFFIX:.mov:video/quicktime #SUFFIX:.hqx:application/mac-binhex40 #SUFFIX:.bin:application/octet-stream #SUFFIX:.exe:application/octet-stream #SUFFIX:.tar:application/x-tar #SUFFIX:.tgz:application/x-tar:gzip #SUFFIX:.Z::compress #SUFFIX:.gz::gzip #SUFFIX:.bz2:application/x-bzip2 #SUFFIX:.zip:application/zip #SUFFIX:.lzh:application/x-lzh #SUFFIX:.lha:application/x-lha #SUFFIX:.dms:application/x-dms #SUFFIX:.html:text/html #SUFFIX:.txt:text/plain
# VMS: # ==== # XLOADIMAGE_COMMAND will be used as a default in src/HTInit.c # for viewing image content types when the DECW$DISPLAY logical # is set. Make it the foreign command for your system's X image # viewer (commonly, "xv"). It can be anything that will handle GIF, # TIFF and other popular image formats. Freeware ports of xv for # VMS are available in the ftp://ftp.wku.edu/vms/unsupported and # http://www.openvms.digital.com/cd/XV310A/ subdirectories. You # must also have a "%s" for the filename. The default is defined # in userdefs.h and can be overridden here, or via the global or # personal mailcap files (see below). # # Make this empty (but not commented out) if you don't have such a viewer or # want to disable the built-in default viewer mappings for image types. # #XLOADIMAGE_COMMAND:xv %s # Unix: # ===== # XLOADIMAGE_COMMAND will be used as a default in src/HTInit.c for # viewing image content types when the DISPLAY environment variable # is set. Make it the full path and name of the xli (also know as # xloadimage or xview) command, or other image viewer. It can be # anything that will handle GIF, TIFF and other popular image formats # (xli does). The freeware distribution of xli is available in the # ftp://ftp.x.org/contrib subdirectory. The shareware, xv, also is # suitable. You must also have a "%s" for the filename; "&" for # background is optional. The default is defined in userdefs.h and can be # overridden here, or via the global or personal mailcap files (see below). # Make this empty (but not commented out) if you don't have such a # viewer or don't want to disable the built-in default viewer # mappings for image types. # Note that open is used as the default for NeXT, instead of the # XLOADIMAGE_COMMAND definition. # If you use xli, you may want to add the -quiet flag. # #XLOADIMAGE_COMMAND:xli %s &
# 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. # 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>] # where -mime type is the MIME content type of the file # -viewer command is a system command that can be # used to display the file where %s is replaced # within the command with the physical filename # (e.g., "ghostview %s" becomes "ghostview /tmp/temppsfile") # -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:xli %s:XWINDOWS # VIEWER:image/gif:ascii-view %s:NON_XWINDOWS # VIEWER:application/start-elm:elm # # You must put the whole definition on one line. # # If you must use a colon in the viewer command, precede it with a backslash! # # 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_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. Assignments made here will be overridden # by entries in those files. # # # Examples: #VIEWER:application/postscript:ghostview %s&:XWINDOWS #VIEWER:image/gif:xli %s&:XWINDOWS #VIEWER:image/x-xbm:xli %s&:XWINDOWS #VIEWER:image/png:xli %s&:XWINDOWS #VIEWER:image/tiff:xli %s&:XWINDOWS #VIEWER:image/jpeg:xli %s&:XWINDOWS #VIEWER:video/mpeg:mpeg_play %s &:XWINDOWS
# The global and personal MAILCAP files allow you to specify external # viewers to be spawned when Lynx encounters different MIME types, which # will override any of the suffix maps in this (lynx.cfg) configuration # file, or in src/HTInit.c. See http://www.internic.net/rfc/rfc1524.txt # 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 PERSONAL_MAILCAP:~/.lynx/mailcap
# When doing a GET, lynx lists the MIME types which it knows how to present # (the "Accept:" string). Depending on your system configuration, the # mime.types or other data given by the GLOBAL_EXTENSION_MAP may include many # entries that lynx really does not handle. Use this option to select one # of the built-in subsets of the MIME types that lynx could list in the # Accept. # # Values for this option are keywords: # INTERNAL lynx's built-in types for internal conversions # CONFIGFILE adds lynx.cfg # USER adds PERSONAL_EXTENSION_MAP settings # SYSTEM adds GLOBAL_EXTENSION_MAP settings # ALL adds lynx's built-in types for external conversions # #PREFERRED_MEDIA_TYPES:internal
# When doing a GET, lynx tells what types of compressed data it can decompress # (the "Accept-Encoding:" string). This is determined by compiled-in support # for decompression or external decompression programs. # # Values for this option are keywords: # NONE Do not request compressed data # GZIP For gzip # COMPRESS For compress # BZIP2 For bzip2 # ALL All of the above. #PREFERRED_ENCODING:all
# VMS ONLY:
#==========
# On VMS, CSwing (an XTree emulation for VTxxx terminals) is intended for
# use as the Directory/File Manager (sources, objects, or executables are
# available from ftp://narnia.memst.edu/). CSWING_PATH should be defined
# here or in userdefs.h to your foreign command for CSwing, with any
# regulatory switches you want included. If not defined, or defined as
# a zero-length string ("") or "none" (case-insensitive), the support
# will be disabled. It will also be disabled if the -nobrowse or
# -selective switches are used, or if the file_url restriction is set.
#
# When enabled, the DIRED_MENU command (normally 'f' or 'F') will invoke
# CSwing, normally with the current default directory as an argument to
# position the user on that node of the directory tree. However, if the
# current document is a local directory listing, or a local file and not
# one of the temporary menu or list files, the associated directory will
# be passed as an argument, to position the user on that node of the tree.
#
#CSWING_PATH:swing
# Unix ONLY: #=========== # DIRED_MENU items are used to compose the F)ull menu list in DIRED mode # The behavior of the default configuration given here is much the same # as it was when this menu was hard-coded but these items can now be adjusted # to suit local needs. In particular, many of the LYNXDIRED actions can be # replaced with lynxexec, lynxprog and lynxcgi script references. # # NOTE that defining even one DIRED_MENU line overrides all the built-in # definitions, so a complete set must then be defined here. # # Each line consists of the following fields: # # # DIRED_MENU:type:suffix:link text:extra text:action # # type: TAG: list only when one or more files are tagged # FILE: list only when the current selection is a regular file # DIR: list only when the current selection is a directory # LINK: list only when the current selection is a symbolic link # # suffix: list only if the current selection ends in this pattern # # link text: the displayed text of the link # # extra text: the text displayed following the link # # action: the URL to be followed upon selection # # link text and action are scanned for % sequences that are expanded # at display time as follows: # # %p path of current selection # %f filename (last component) of current selection # %t tagged list (full paths) # %l list of tagged file names # %d the current directory # # #DIRED_MENU:::New File:(in current directory):LYNXDIRED://NEW_FILE%d #DIRED_MENU:::New Directory:(in current directory):LYNXDIRED://NEW_FOLDER%d # # Following depends on OK_INSTALL #DIRED_MENU:FILE::Install:selected file to new location:LYNXDIRED://INSTALL_SRC%p #DIRED_MENU:DIR::Install:selected directory to new location:LYNXDIRED://INSTALL_SRC%p # #DIRED_MENU:FILE::Modify File Name:(of current selection):LYNXDIRED://MODIFY_NAME%p #DIRED_MENU:DIR::Modify Directory Name:(of current selection):LYNXDIRED://MODIFY_NAME%p #DIRED_MENU:LINK::Modify Name:(of selected symbolic link):LYNXDIRED://MODIFY_NAME%p # # Following depends on OK_PERMIT #DIRED_MENU:FILE::Modify File Permissions:(of current selection):LYNXDIRED://PERMIT_SRC%p #DIRED_MENU:DIR::Modify Directory Permissions:(of current selection):LYNXDIRED://PERMIT_SRC%p # #DIRED_MENU:FILE::Change Location:(of selected file):LYNXDIRED://MODIFY_LOCATION%p #DIRED_MENU:DIR::Change Location:(of selected directory):LYNXDIRED://MODIFY_LOCATION%p #DIRED_MENU:LINK::Change Location:(of selected symbolic link):LYNXDIRED://MODIFY_LOCATION%p #DIRED_MENU:FILE::Remove File:(current selection):LYNXDIRED://REMOVE_SINGLE%p #DIRED_MENU:DIR::Remove Directory:(current selection):LYNXDIRED://REMOVE_SINGLE%p #DIRED_MENU:LINK::Remove Symbolic Link:(current selection):LYNXDIRED://REMOVE_SINGLE%p # # Following depends on OK_UUDECODE and !ARCHIVE_ONLY #DIRED_MENU:FILE::UUDecode:(current selection):LYNXDIRED://UUDECODE%p # # Following depends on OK_TAR and !ARCHIVE_ONLY #DIRED_MENU:FILE:.tar.Z:Expand:(current selection):LYNXDIRED://UNTAR_Z%p # # Following depend on OK_TAR and OK_GZIP and !ARCHIVE_ONLY #DIRED_MENU:FILE:.tar.gz:Expand:(current selection):LYNXDIRED://UNTAR_GZ%p #DIRED_MENU:FILE:.tgz:Expand:(current selection):LYNXDIRED://UNTAR_GZ%p # # Following depends on !ARCHIVE_ONLY #DIRED_MENU:FILE:.Z:Uncompress:(current selection):LYNXDIRED://DECOMPRESS%p # # Following depends on OK_GZIP and !ARCHIVE_ONLY #DIRED_MENU:FILE:.gz:Uncompress:(current selection):LYNXDIRED://UNGZIP%p # # Following depends on OK_ZIP and !ARCHIVE_ONLY #DIRED_MENU:FILE:.zip:Uncompress:(current selection):LYNXDIRED://UNZIP%p # # Following depends on OK_TAR and !ARCHIVE_ONLY #DIRED_MENU:FILE:.tar:UnTar:(current selection):LYNXDIRED://UNTAR%p # # Following depends on OK_TAR #DIRED_MENU:DIR::Tar:(current selection):LYNXDIRED://TAR%p # # Following depends on OK_TAR and OK_GZIP #DIRED_MENU:DIR::Tar and compress:(using GNU gzip):LYNXDIRED://TAR_GZ%p # # Following depends on OK_ZIP #DIRED_MENU:DIR::Package and compress:(using zip):LYNXDIRED://ZIP%p # #DIRED_MENU:FILE::Compress:(using Unix compress):LYNXDIRED://COMPRESS%p # # Following depends on OK_GZIP #DIRED_MENU:FILE::Compress:(using gzip):LYNXDIRED://GZIP%p # # Following depends on OK_ZIP #DIRED_MENU:FILE::Compress:(using zip):LYNXDIRED://ZIP%p # #DIRED_MENU:TAG::Move all tagged items to another location.::LYNXDIRED://MOVE_TAGGED%d # # Following depends on OK_INSTALL #DIRED_MENU:TAG::Install tagged files into another directory.::LYNXDIRED://INSTALL_SRC%00 # #DIRED_MENU:TAG::Remove all tagged files and directories.::LYNXDIRED://REMOVE_TAGGED #DIRED_MENU:TAG::Untag all tagged items.::LYNXDIRED://CLEAR_TAGGED
# External application support. This feature allows Lynx to pass a given # URL to an external program. It was written for three reasons. # # 1) To overcome the deficiency of Lynx_386 not supporting ftp and news. # External programs can be used instead by passing the URL. # # 2) To allow for background transfers in multitasking systems. # I use wget for http and ftp transfers via the external command. # # 3) To allow for new URLs to be used through Lynx. # URLs can be made up such as mymail: to spawn desired applications # via the external command. # # Restrictions can be imposed using -restrictions=externals at the Lynx command # line. This will disallow all EXTERNAL lines in lynx.cfg that have FALSE in # the 3rd field (not counting the name of the setting). TRUE lines will still # function. # # The lynx.cfg line is as follows: # # EXTERNAL:<url>:<command> %s:<norestriction>:<allow_for_activate>[:environment] # # <url> Any given URL. This can be normal ones like ftp or http or it # can be one made up like mymail. # # <command> The command to run with %s being the URL that will be passed. # In Linux I use "wget -q %s &" (no quotes) to spawn a copy of wget for # downloading http and ftp files in the background. In Win95 I use # "start ncftp %s" to spawn ncftp in a new window. # # <norestriction> This complements the -restrictions=externals feature to allow # for certain externals to be enabled while restricting others. TRUE means # a command will still function while Lynx is restricted. WB # # <allow_for_activate> Setting this to TRUE allows the use of this command not # only when EXTERN key is pressed, but also when ACTIVATE command is invoked # (i.e., activating the link with the given prefix will be equivalent to # pressing EXTERN key on it). If this component of the line is absent, then # FALSE is assumed. # # [:environment] Optional, if XWINDOWS then command is allowed only if # $DISPLAY environment variable is set, else if NON_XWINDOWS then command # is allowed only if $DISPLAY environment variable is not set, if absent or # anything else command is always allowed. # # For invoking the command use the EXTERN_LINK or EXTERN_PAGE key. By default # EXTERN_LINK is mapped to '.', and EXTERN_PAGE to ',' (if the feature is # enabled), see the KEYMAP section above. # #EXTERNAL:ftp:wget %s &:TRUE EXTERNAL:file:thunar %s &:TRUE EXTERNAL:file:mousepad %s &:TRUE EXTERNAL:ftp:wget %s &:TRUE EXTERNAL:ftp:gftp %s &:TRUE EXTERNAL:http:wget %s &:TRUE EXTERNAL:http:dillo %s &:TRUE EXTERNAL:http:opera %s &:TRUE EXTERNAL:https:wget %s &:TRUE EXTERNAL:https:dillo %s &:TRUE EXTERNAL:https:opera %s &:TRUE EXTERNAL:mailto:sylpheed-claws %s &:TRUE
# Any of the compiled-in pathnames of external programs can be overridden # by specifying the corresponding xxx_PATH variable. If the variable is # given as an empty string, lynx will not use the program. For a few cases, # there are internal functions (such as mkdir) which can be used instead. #BZIP2_PATH: #CHMOD_PATH: #COMPRESS_PATH: #COPY_PATH: #GZIP_PATH: #INFLATE_PATH: #INSTALL_PATH: #MKDIR_PATH: #MV_PATH: #RLOGIN_PATH: #RMDIR_PATH: #RM_PATH: #SETFONT_PATH: #TAR_PATH: #TELNET_PATH: #TN3270_PATH: #TOUCH_PATH: #UNCOMPRESS_PATH: #UNZIP_PATH: #UUDECODE_PATH: #ZCAT_PATH: #ZIP_PATH:
# Log the requested URLs using the syslog interface. #SYSLOG_REQUESTED_URLS:TRUE
# Add the given text to calls made to syslog, to distinguish Lynx from other # applications which use that interface. #SYSLOG_TEXT:
Prev: Cookies || Next: HTML Parsing