

========> [LT89B2.CAP]AAAREADME.TXT;1 <========


	 CAP - Columbia AppleTalk Package for UNIX (4.2 BSD).
	       (For use with AppleTalk/Ethernet bridge)

	o RELEASE NOTES
	o CAP Distribution 5.00, May 1988

Introduction
------------

This distribution should allow asp, atp, pap client and server
applications to be developed.

The 10/86, 2/87, 9/87 or 1/88 Revision of the UDP software, known as
"KIP", developed by Bill Croft at SUMEX, Stanford University is
required.  Revision 1/88 or later is preferred.

ABSTRACT
--------

CAP is written for BSD 4.2 Unix and derivatives.  CAP implements a
library containing a portion of Apple Computer's AppleTalk protocols.
In order to use this package you need an AppleTalk/Ethernet bridge
(e.g. Kinetics FastPath box).  CAP includes a number of applications
that can be used to print to a LaserWriter, spool for a LaserWriter,
and act as Unix based AppleShare compatible file server (no support
for AppleShare PC).  CAP also includes a number of sample programs and
contributed software.

CAP library routines are structured, for the most part, the same as
the Apple routines described in "Inside AppleTalk" and "Inside
LaserWriter."  Refer to the Apple documents and the procedure comments
for a complete description of the routines and how to call them.

Bill Croft's original work in this area provided the inspiration for
CAP.






========> [LT89B2.CCA]AAAREADME.TXT;1 <========


TPU Programming Examples
  Submitted by Bob Tinkelman, CCA

These are examples of various utilities and programs implemented
by using the Callable TPU interface. They were examples in the
Pre Symposium Seminar by the submitter.






========> [LT89B2.DBRYANT]AAAREADME.TXT;2 <========


1 GSR
  Global Search and Replace will search for a character string in a
  user specified set of files and replace with a character string.
  When any strings are replaced in a file, a new version of the file
  will be created, with the exception of when a Quit is entered in 
  VERIFY mode.

  Format:

    GSR search-and-replace-file-spec search-string replace-string

    Original version by David Bryant (Ford Aerospace).

1 TETRIS
THIS IS THE GAME OF TETRIS, FIRST WRITTEN BY TWO GUYS FROM RUSSIA.

ADAPTED TO THE VAX WORLD BY:
        DAVID BRYANT
        COLUMBIA, MD

THE OBJECT IS TO MOVE AND ROTATE DROPPING OBJECTS SO AS TO
CREATE COMPLETE ROWS.  WHEN A ROW IS COMPLETE IT IS REMOVED AND
ALL THE OBJECTS ABOVE IT DROP DOWN ONE LEVEL.





========> [LT89B2.FLEX]AAAREADME.TXT;1 <========


This is the initial release of flex, a replacement for the lex(1)
tool.  As the copyright indicates, this distribution can be freely
redistributed.

Some notes on the distribution:

    Yes, there are some niggling lex features which are not available which
    seem like they'd be easy to add.  They're not, or if they are then the
    straight-forward implementation of them would slow down the scanner.
    Unfortunately I am unable to do any further work on flex other than bug
    fixes, so if there's something you've just gotta have, you'd better
    be willing to dive into the code.  I'll be happy to give (fairly
    high-level) advice on how to proceed.

    The compressed tables have been tested pretty thoroughly in the past,
    though may be suffering from bit-rot.  The fast/full tables have been
    recently implemented and are more likely to have bugs.

    For a System V machine, add the #define "SV".  Not guaranteed to do
    the full job, but a step in the right direction.

    Flex has been successfully ported to Sun Unix and 4.3BSD Vax Unix.


The flex distribution consists of the following files:

        README          This message

        Changes         Differences between this release and the beta-test

        Makefile
        flexdef.h
        parse.y
        scan.l
        ccl.c
        dfa.c           flex sources
        ecs.c
        main.c
        misc.c
        nfa.c
        sym.c
        tblcmp.c
        yylex.c

        scan.c.dist     pre-flex'd version of scan.l

        flex.skel
        flex.fastskel
        flexskelcom.h   skeleton scanner sources
        flexskeldef.h
        fastskeldef.h

        flex.1          manual entry

        Timings         a brief note comparing timings of flex vs. lex
                                                                Page 2




Either move {flexskelcom.h,flexskeldef.h,fastskeldef.h} into /usr/include
or edit {flex.skel,flex.fastskel,flexskeldef.h,fastskeldef.h,scan.c.dist}
and wire in the full pathname of where you are going to keep the include files.

Decide where you want to keep {flex.skel,flex.fastskel} (suggestion:
/usr/local/lib) and move it there.  Edit "Makefile" and change the
definitions of SKELETON_FILE and F_SKELETON_FILE to reflect the full
pathnames of {flex.skel,flex.fastskel}.

To make flex for the first time, use:

    make first_flex

which uses a pre-generated copy of the scanner whose source is in flex.

Assuming it builds successfully, you can test it using

    make test

The "diff" should not show any differences.

If you're feeling adventurous, rebuild scan.c using various
combinations of FLEX_FLAGS, each time trying "make test" when
you're done.  To rebuild it, do

        rm scan.c
        make FLEX_FLAGS="..."

where "..." is one of:

        -ist -c
        -ist -ce
        -ist -cm
        -ist -cfe
        -ist -cFe

and testing using:

        make FLEX_FLAGS="..." test


Format the manual entry using

    nroff -man flex.1


Please send problems and feedback to:

        vern@lbl-{csam,rtsg}.arpa  or  ucbvax!lbl-csam.arpa!vern

        Vern Paxson
        Real Time Systems Group
        Bldg. 46A
                                                                Page 3


        Lawrence Berkeley Laboratory
        1 Cyclotron Rd.
        Berkeley, CA 94720

        (415) 486-6411





========> [LT89B2.GNUSOFTWARE]AAAREADME.TXT;2 <========


        GNU Software

This software is from the Free Software Foundation. Included are
GNU EMACS, Gnu C and Gnu C++ plus many other utilities. Also
present in this directory tree are Angel Li's VMS ports of
Gnu C and Gnu C++. GCC and G++ (the C and C++ compilers) are
reputed to generate better code for the VAX (or most of their
other targets) than essentially any commercial C or C++
compilers. They link with VAXCRTL.EXE in VMS. Numerous other
utilities include BISON, a YACC clone, and GAWK, an AWK
clone, and FLEX, a LEX clone. Information on FSF has appeared
in these directories on previous tapes. See file GETTING_GNU.SOFTWARE
for further information.






========> [LT89B2.POOT]AAAREADME.TXT;2 <========


This submission consists of 2 rather inconsequential command procedures. I
was asked to submit CBAR.COM in an L&T session when I mentioned I had such
a beast. I threw in DSR.COM because it was handy.

1)   CBAR.COM is an automatic change bar generator for runoff files. It
     takes three arguments: the current version of the runoff input file,
     an older version of the same runoff input file, and an output file
     name. The output is a runoff input file that is the same as that given
     as the first parameter with the exception that change bar commands
     have been added. Note that you must execute runoff with the "/CHANGE"
     qualifier to actually get the change bars.

     CBAR.COM isn't too smart, and it will try to flag changes to runoff
     commands with change bars (though if they don't produce output there
     will be no effect). A rather more serious shortcoming is that they
     don't respect .literal commands, and so will insert change bar
     commands into a block of literal text. The commands  will then be
     literally reproduced as part of the text...

     Having seen input for DOCUMENT, it seems like all that would be needed
     to use CBAR.COM with DOCUMENT would be to change the actual commands
     inserted, but I don't know for sure, as I don't know DOCUMENT.

2)   My other submission is a command procedure (DSR.COM) that I use to
     build documents with runoff. It automatically generates a table of
     contents and an index and then builds the entire document, all in one
     step. 

     It takes 1 required parameter, and 1 optional parameter. The optional
     parameter is described later. The required parameter is the FILE NAME
     ONLY, NO FILE TYPE of the document to be built. There are 3 supported
     file types .rnd, .rnm, and .rns. These produce output documents with
     the extensions .doc, .man, and .std, respectively. More can easily be
     added. DSR.COM looks a file with the supplied name and one of these
     extentions to be found in the current directory.

     Each document is built from 2 files. The file with the above extention
     contains the title page and .require commands for the table of
     contents, the actual document, and the index. I also usually put in
     commands between these pieces to control page numbering and the like.

     DSR.COM references CBAR.COM using the logical name "util", which will have
     to be defined or editted at the user's site.

     The other file is a file of the same name with file type .rno, located
     in the current directory. This is .require'd by the first file. This
     is the file that is processed to generate the index and table of
     contents, so it should contain the entire document starting at page 1
     and going to the end.

     I have included samples of the 2 files  for a skeleton document,
     ref.rnm and ref.rno. The command @dsr ref will build the output file
     ref.man, containing a title page, table of contents, a bit of text,
     and an index.

                                                                Page 2


     The optional second parameter, mentioned earlier, is the file spec of
     an older version of the .rno file. If this is supplied, CBAR.COM is
     used to generate a document with change bars showing the differences
     between the current .rno file and the file whose file spec is given as
     the second argument. 

     WARNING. The output of CBAR.COM when used by DSR.COM is the next
     version of your .rno file. This is then deleted after the document is
     built, but if you abort DSR, it could be left around. Also, be sure
     you have a version limit of at least 2, or you will lose your .rno
     file altogether! This is done this way so the file will be there for
     the .require command in your primary input file. I suppose a safer way
     would be to create a temp copy of that as well and change the .require
     to point at the change bar version of the source, then delete them
     both. This is left as an exercise to the reader.


I hope these are of some use to somebody.
--
Terry Poot (800)255-2762, in Kansas (913)776-4041
The McCall Pattern Company, 615 McCall Rd., Manhattan, KS 66502, USA
UUCP: rutgers!ksuvax1!mccall!tp   Internet: tp%mccall@ksuvax1.cis.ksu.edu





========> [LT89B2.STP]AAAREADME.TXT;1 <========


STP - Setpoint's Text Processor                                 November, 1989

This version of Setpoint's Text Processor is intended to run under VMS version
5.0 or greater.  This extension to DEC's EVE editor has been done by Paul 
Boudreaux with creative input from Kurt Mayer.  This extension is also 
distributed on an "as-is" basis.  However, if you find any problems please 
alert me to them, and when I get the chance I will fix them.  

In addition to this file, on-line help has been included.  This help 
may be accessed by typing HELP on the command line.  Typing HELP STP 
on the command line will bring you directly to the STP help section.
Because this help section is separated from the normal help library for
EVE, all help inquiries must begin with STP.  For example:

  Command:  HELP STP Column

This command would bring up help on the command Column.  Since Column is
in the STP help library, STP must proceed it on the command line.  However,
if HELP STP were issued first, and then Column were entered when being
prompted for a command for help on, the help for Column would be shown.

As this section file is distributed, the EDT keypad has been set on and
so has the STP keypad.  These both can be set off by the following commands:

        SET KEYPAD NOEDT
        SET KEYPAD NOSTP

Also, the cursor has been set to "free" movement and word-wrapping has been
set to off.  

The keys which are defined by the EDT keypad are the discussed in the 
documentation provided by DEC on EVE.  The keys defined in STP are
as follows:

        Key                 Function
        ---                 --------

        CTRL/Z              Fake Exit
        GOLD/SELECT         Rectangular select       
        GOLD/INSERT HERE    Rectangular insert here   
        GOLD/REMOVE         Rectangular remove        
        F20                 Attach                  
        F17                 Column                 
        F18                 Rectangular text fill  
        GOLD/F18            Rectangular change case
        F19                 Store Text
        GOLD/F19            Rectangular store text 
        KP3                 Next Window
        GOLD/KP3            One Window
        GOLD/R              Display Ruler     
        GOLD/DELETE         Delete Current Buffer     
        GOLD/UP             Enlarge window 3  
        GOLD/DOWN           Shrink window 3   
        GOLD/LEFT           Shift Left 40
        GOLD/RIGHT          Shift Right 40
                                                                Page 2


        GOLD/ENTER          Write file     
        ENTER               Get file
        GOLD/PREV SCREEN    Delete window
        GOLD/NEXT SCREEN    Split window   

In addition to the functions assigned to keys, the following functions
have been added:

        Number Lines
        Rectangular Change Case
        Eliminate Tabs
        Zap
        Trim Buffer     
        Fix CRLFs

The Number Lines function works with Rectangular selections.  Select
a rectangular region where the numbers are to be placed, then execute
this function.  Eliminate Tabs works from the cursor position to the
end of the file.  Trim Buffer works on the entire buffer.  If column 
is invoked from the Command: line with a number after it, it will move
the cursor to that column.  If it is invoked with out a number 
specified, it informs you about the cursor position.

