Lynx -README file
Here is a discription of Lynx. (Looks alot like the man file)
For installation instructions, see the INSTALLATION file.


   Local                                                              LYNX(1)



   NAME
     Lynx - hypertext browser for local and remote hypertext and text files

   SYNOPSIS
     Lynx path


   DESCRIPTION
     Lynx is a general hypertext browser, originally derived from Peter
     Scott's Hytelnet.  Lynx was designed to support a Campus Wide Informa-
     tion Server (CWIS), but can be used for many other general purpose
     applications. When it is started, Lynx is given the name of a file con-
     taining text information in which hypertext links are embedded.  The
     simplest hypertext link is just a pointer to another file containing
     text and links.  Links show up as highlighted text, and users press
     Return when a link is highlighted to select that link.  When the link is
     selected Lynx finds the associated file and displays it on the screen in
     place of the first file.

     Lynx data files can reside on any accessable file system. (i.e. nfs,
     afs, etc.), or on Gopher servers.  A Lynx data file may point to multi-
     ple Gopher servers, so that Lynx provides a truly distributed hypertext
     system.

     Any text in angle brackets (e.g. <HELP>), or following a self-defined
     delimiter, becomes a link pointer.  The link pointer is not actually
     displayed on the screen. Instead, the text following the link pointer is
     highlighted on the screen. If the user selects the link, Lynx examines
     the link pointer and takes appropriate action.  Link pointers can con-
     tain file names, target names for target strings that appear in the
     specified files, or shell commands.  If the link pointer contains a file
     name, Lynx displays the specified file on the screen.  If the pointer
     contains a link target along with the file name, Lynx displays the por-
     tion of the target file containing the target on the screen.  If the
     link pointer contains a shell command, Lynx exectues the command and
     displays the command output on the screen.

     Since Lynx has the ability to execute any shell command embedded in a
     link pointer, it can be used to build menuing systems.

     Lynx database files may begin with special Lynx commands.  These incude:

          DELIMETER=<character_string>
          OWNER=<account@host>
          BASE=<pathname>

     The DELIMITER= command allows users to redefine the initial delimiter
     used to define a link pointer.  The terminal delimiter remains ">".  The
     OWNER information determines who will receive messages sent by users who
     select the Comment command while in Lynx.  The BASE information quack
     quck quack.




                                                                            1






   LYNX(1)                                                              Local


     Lynx link pointers can be described as having one of two syntices:

          < pathname@hostname : target_string : character_count > or
          < shell_command : character_count >

     where the character_count specifies the number of characters following
     the link pointer to be highlighted on the screen. The highlighted text
     appears as the link to the user.  In both syntices the initial < may be
     replaced by the delimiter specified by the user in a DELIMITER= command.

     The syntax of a target embedded in a Lynx database is

          [* target_string *]

     The intial target string delimiter can be redefined by using the
     TARGET_DELIMITER= command.

     Lynx is or will soon be available for Unix, VMS, Mac and IBM PC systems.

     This Un*x version of Lynx should work on any system with a reasonable
     Curses implementation

     Lynx also notices telnet(1) commands embedded in the files, and will
     execute them for the user, if desired.  (This feature is a hangover from
     its origins as a Hytelnet look-alike.) tn3270(1) commands can be exe-
     cuted as well, if this program is available on your system.

   COMMANDS

     Use the cursor control keys to move around in Lynx.  The up and down
     arrows move you from one highlighted link to another.  Use the right
     arrow (or <return>) to follow a link, and use the left arrow to return
     from a link.  The numeric keypad, or the numbers mapped to the keypad
     keys, can also be used (ie 6-right 8-up 9-pgup 3-pgdn)

     Other commands include:

     m    Return to the main menu (the first screen you see when you start
          Lynx)

     + or <space> or PgDn
          Scroll down to the next page

     - or b or PgUp
          Scroll up to the previous page

     ?    Help

     q <Ctrl>-D
          Quit Lynx

     <Backspace> or <Del>
          Display a list of links that have already been visited.  The
          displayed links may be selected and will result in a new display of


   2






   Local                                                              LYNX(1)


          the previously displayed information.

     /<string>
          Search a selected file for all occurences of the string "string",
          and display the portion of the file containing that string.

     n    Find and display the next occurence of a search string.

     r or c
          Send a message to the designated file owner or to the Lynx database
          administrator

   NOTES
     This is the first release of Lynx for UN*X/VMS

     This program understands the same file format as HYPERRES, and it is
     possible to plug-and-play other HYPERRES databases as well.

     Thanks to Michael A. Rowley (mcrowley@mtholyoke.edu) for some of the
     interrupt handling code.  And Earl Fogel, Computing Services, University
     of Saskatchewan, fogel@sask.usask.ca, who wrote the original hytelnet
     code

   AUTHOR
     Lou Montulli, Computing Services, University of Kansas
     Montulli@kuhub.cc.ukans.edu

   FILES
     /usr/local/lynx          default database directory
     /usr/local/lynx/start    default starting point

   BUGS

     Doesn't understand complex HYPERRES links.

     Should timeout when reading escape sequences.

   SEE ALSO
     telnet(1), gopher(1), hytelnet(1), kufacts(1)

















                                                                            3



