Version 2 of turbo routines contains:

1)New, improved error message parsing.  A bug in the C compiler that 
  generates bad ASM code can now be handled, even if usin CTMP files
  in ram:.  It will also read in #include files if there is an error
  found.
  
2)The "drag the mouse to highlight text" function has been re-written
  to allow dynamic highlighting of the text.  Text will be highlighted
  as you move the mouse, not just when you release the button.
  
One minor point on error message parsing.  Due to the inconsistancy 
between the errors generated by the C compiler and the assembler, 
parsing is done in such a way that filenames beginning with a numeric
value, if they generate an error, will not be auto-loaded back into
the editor.  Most file names are in the form of "file12" rather than
"12file".  By avoiding filenames that begin with a number, there is
no problem.  You may want to try rewriting the parsing routines, but 
the easiest way to correct this problem is for Manx to change the 
error message line number generated by the C compiler to contain a
leading space before the line number, as is done in the assembler
error messages.  Of course, filenames with embedded spaces are OK to
use in Amiga DOS, but I avoid them like the plague in real life.  I
haven't tried to compile a file with embedded spaces in its name.

Tom Althoff 2/28/87

/////////////////////////  Original readme follows  //////////////////////


Using Uedit (or almost any text program) without first running MicroSmiths
"FastFonts" program is like running your high performance sports car
on Sunoco 190 regular.  FastFonts provides a noticable and welcome speedup
to almost any text based program.

These are the files I use when running Uedit.  The file named "althoffdata!"
can be renamed data! and placed in the S: directory of your system.  The
latest version of Uedit supports command line declarations of which data!
file to use.  Typing "Uedit -Dalthoffdata!" will load my custom routines into
Uedit.  The source of my routines is included in the file "althoffconfig!" 
and may be copied into your own config! file.  Just make sure all menus
reflect the changes made to a config! file and that there is only one key
definition assigned to any one key. 

The "Turbo" routines were written for Manx Aztec C users.  They call make,
make with a makefile filename, cc, as, and ln.  If you don't have the
version of Aztec C which includes make, you might consider upgrading. It
is an extremely usefull tool, especially when compiling multi-moduled
programs.

Here is what happens when you select "make" from Uedit.  If you have made
any changes to any files in Uedit, they will be saved and closed from the
screen.  If you have a file on the screen and have made no changes to it,
and it is used in the make process, it is advisable to close the file 
manually before running make.  It is not necessary to do so, but if an 
error happens to occur in that particular file, it will ask you if you
want a read only copy.  I close all my files manually before running make
to save time.  Make will search for a file named "makefile" which contains
your rules for creating your program.  It will call cc, as, and ln as it 
builds your program.  If an error is generated by the C compiler or the
Assembler, the Turbo routines will parse the error message and load in the
offending source code and place the cursor at the point in the source code
that triggered the error. 

If you ever need to see the full error list or whatever messages ADOS 
returns to Uedit, select "show flags" from the buffers menu and buffer
n39 will always contain the last message received from ADOS.

There is a public domain program called CCHECK that I use in my Uedit menu
and have included on this disk (including source code).  This takes the
current file displayed on the screen and checks through the file for
missing braces, brackets, parentheses and comments.  It also does some
logical checks for if/then/else loops and checks for = instead of == in
if statements.  I find it a quick and dirty way to check for many of my
typing errors.  A lint it is not, but then again, that's good news in
itself!   Ccheck is a stand-alone program that can be invoked under CLI 
with a filename argument.

Also included is a dumb {}[]() checker called check1.  Source is also
included for this program, though I do not use it in Uedit.  One thing
about check1 is that it displays each line of text as is is processed
as well as the running total of braces,brackets and parentheses, left
and right.  

A few commands have been changed from the original Uedit config! file.
Not all of them are documented (they were added/changed over the past
year of 4 versions of Uedit).  I didn't like the invisible gadgets and
after Rick Stiles added vertical gadget separators, I included a message
that flashes the gadget commands every time you click the left mouse button.
This is a reminder of what the gadgets do.  Screen up, screen down, make
(and shifted/control commands related to it) and next file.  The original
Uedit did not have provisions for displaying line numbers and they are
now displayed over the 4th gadget on the right.  I set page length to 
1 to keep the page counter from incrementing and ruining the actual
file line count.  People using Uedit for wordprocessing would be better
off changing the page length to a reasonable number (66?).

One command I added is the Alt-help key.  This loads the ASCII table onto
the current screen.  The table has all the codes for decimal,hex,octal,
and binary.  Pressing help or Alt-help after displaying the table will
return you to your original text file.  In order to take advantage of
this command, the file ASCII.UEDIT must be placed in your system's S:
directory.

There are many commands not documented for Uedit, except in the manual.
There are ways to see the ASCII value of the character under the cursor,
total up columns of numbers and place the total anywhere in the text, and
convert a number in the text to/from hex/decimal.  

Uedit may seem difficult at first glance, simply from the documentation
alone.  I ignored the manual and just started to use Uedit from the first
day.  The basic commands are easy and it wasn't until I wanted to do 
something special that I needed the manual.  Anything I have done to
the config! file can be undone or added to by you.  A good $60 dollar
investment would be to send the $25 bucks in to Rick Stiles for his
manual and the latest version of Uedit and send $35 to Charlie Heath
of MicroSmiths's for his FastFonts program.  The FastFonts disk also
contains a screen blanking program to kill the screen during periods
of inactivity, and a program called funkeys to allow user definable
keys outside of the Uedit environment. I have not used Funkeys from
within Uedit, due to possible conflict of key assignments.

My current system is a CSA Turbo Amiga (14mhz 68020/68881), Microbotics
MAS20 20mb hard disk, 1.5mb 32bit CSA static ram, 2mb ASDG ram board
configured as a recoverable ram disk.  Booting is under KickBench to
allow for unmanned revovery from power loss.  I always boot using an
interlaced 640X400 (80col X 48line) screen with screen colors selected 
for black text on a green or blue pastel background to eliminate flicker.
I hate editing on 24 line screens when I can have 48!  FastFonts and 
mouseclock get run from my startup file.  Mouseclock is great for those
late night sessions when I tend to loose track of the time. (Mouseclock
is also included on this disk)

Give this disk (or archive if downloaded from a BBS) to anyone who
has Uedit.  I am a firm believer in public domain.  No charge is to
be made for these routines (nor will any donations be solicited nor
accepted by myself).

Thomas Althoff
c/o ABC/Capital Cities Inc.
    Video Tape Tech Support
    30 W. 67th Street Floor B1
    New York City, NY 10023
    (212) 887-4678
    


Uedit (latest version with full manual) is available for $25 from:  

Rick Stiles
PPE
2420 Summit Springs Dr              
Atlanta GA 30338                   
(404) 587-5396 



FastFonts is available for $37.95 from:

MicroSmiths Inc.
P.O. Box 561
Cambridge, MA 02140



Summary of Disk Contents:

Put the following in your S: directory:
althoffconfig! (Modified config! file containing source for the Turbo stuff)
althoffdata!   (Pre-compiled data! file for Turbo-charged Uedit)
ascii.uedit    (Text file of ASCII table)

Put the following in you C: directory:
ccheck


The remaining files are:
ccheck.c (Source for ccheck)
check1 (dumb {}[]() checker)
check1.c (source for check1)
mouseclock (turns mouse pointer into digital clock)

