NEdit Version 5.0.2, March 11, 1998
	     

PRODUCT DESCRIPTION

NEdit is a standard GUI (Graphical User Interface) style text editor for
programs and plain-text files.  Users of Macintosh and MS Windows based text
editors should find NEdit a familiar and comfortable environment.  NEdit
provides all of the standard menu, dialog, editing, and mouse support, as
well as all of the standard shortcuts to which the users of modern GUI based
environments are accustomed.  For users of older style Unix editors, welcome
to the world of mouse-based editing!

Please be sure to check the platform specific README files, i.e. README.sun
and README.ibm, for additional information about your particular system.

----------------------------------------------------------------------------

                             TERMS AND CONDITIONS
                             ====================

This software has been made freely available with a request for
collaborative input subject to standard Fermitools Terms and Conditions
given in full below.

----------------------------------------------------------------------------

AUTHORS

    Mark Edel, Joy Kyriakopulos, Arnulfo Zepeda-Navratil, Suresh Ravoor, Donna
    Reid, Jeff Kallenbach

    Fermi National Accelerator Laboratory - Mail Station 234
    P.O Box 500
    Batavia, IL 60510
    Internet: [email protected]

Fermilab Standard Government Sponsorship Notice

    This work was performed at Fermi National Accelerator Laboratory,
    which is operated by Universities Research Association, Inc., under
    contract DE-AC02-76CHO3000 with the U.S. Department of Energy.


ACKNOWLEDGEMENTS

    Syntax highlighting patterns were contributed by: Simon T. MacDonald, 
    Maurice Leysens, Matt Majka, Alfred Smeenk, Alain Fargues, Christopher
    Conrad, Scott Markinson, Konrad Bernloehr, Ivan Herman, Patrice Venant,
    Christian Denat, Philippe Couton, Max Vohlken, and Markus Schwarzenberg.

    Regular expression code by Henry Spencer
    
    Nedit incorporates an altered version of Henry Spencer's regcomp and
    regexec code adapted for NEdit.  Original copyright notice:

	Copyright (c) 1986 by University of Toronto. Written by Henry
	Spencer.  Not derived from licensed software.

	Permission is granted to anyone to use this software for any purpose
	on any computer system, and to redistribute it freely, subject to the
	following restrictions:

	1. The author is not responsible for the consequences of use of this
	software, no matter how awful, even if they arise from defects in it.

	2. The origin of this software must not be misrepresented, either by
	explicit claim or by omission.

	3. Altered versions must be plainly marked as such, and must not be
	misrepresented as being the original software.


VERSION 5.0.2

5.0.2 is a bug fix release with very little new functionality (double-click
selection of ranges of delimiters, $line, $column and $modified macro
variables, smart-indent for Python).  The full list of changes and fixes can be
found in the ReleaseNotes file in the distribution directory. 

Version 5.0 was significant upgrade to NEdit, completing the macro language and
adding, syntax highlighting, smart-indent, continuous wrap mode, language
sensitive preferences, and many other new features.

Please note that syntax highlighting patterns are mostly user-contributed, and
that syntax highlighting is relatively new to NEdit.  If you don't like the way
your particular language is being highlighted, the patterns are quite easy to
change.  We would like to make the default patterns as robust and correct as
possible, so if you see something wrong, please don't just grumble quietly to
yourself, send mail to [email protected].

As of this writing, there are no known bugs in this software, except for the
few noted in the Problems/Bugs section of the on-line help, or the FAQ file
and the ReleaseNotes file in the distribution directory.  Please report any
problems, even if you think they are trivial.


INSTALLATION

NEdit consists of a single, stand-alone executable file which does not
require any special installation beyond copying it to your system and making
it accessible to users.  

To Install NEdit on Unix Systems:

    1) Copy the appropriate archive file to your system using ftp in binary
       mode, and use gunzip and tar to expand the archive.  For example:
       
           % gunzip nedit_sgi.tar.gz
           % tar xvf nedit_sgi.tar

       If you don't have gzip, the GNU compression utility, fetch the files
       instead from the "individual" directory.  The README file there explains
       which files are necessary and how to install them on your system.

    2) Copy the files, nedit and nc, to a directory which is referenced in
       the paths of all users.  /usr/local/bin is the customary location for
       optional third-party software on many systems.  Alternatively, you can
       create a command alias to refer to nedit and nc in this or any other
       directory, or add the directory containing nedit to your path.  In
       other words, it doesn't matter how or where you install nedit, as long
       as it gets executed somehow.
    
To Install NEdit on VMS Systems:

    1) Copy the appropriate backup saveset to your system using ftp in
       binary mode.

	   FTP> binary

    2) After copying the backup save set to your VMS system, you must re-set
       the file attributes so that backup can restore the file properly.  To
       do this use the SET FILE/ATTRIBUTE command:

           $ SET FILE/ATTRIBUTE=(RFM:FIX,LRL:32256)
       
    3) Use backup to expand the saveset.
       
    4) Copy nc.exe and nedit.exe to the directory where you want them to
       reside, and define foreign commands (either in login.com for
       yourself, or in sys$manager: sylogin.com for all users) to invoke
       each executable.  For example, if nedit.exe were in the directory
       mydir on the disk called mydev, adding the following line to your
       login.com file would define the nedit command:

            $ ned*it :== $mydev:[mydir]nedit.exe

These instructions are repeated in the README file included in each archive.
Also check the platform specific README files, i.e. README.sun and README.ibm,
for additional information about your particular system.


RUNNING NEDIT

If you are accessing a host Unix system from a remote workstation or X terminal,
you need to set the Unix environment variable for your display:

	% setenv DISPLAY devicename:0
	
where devicename is the network node name of the workstation or X terminal
where you are typing.  On VMS systems, the equivalent command is:

	$ set display/create/node=devicename

To run NEdit, simply type "nedit", optionally followed by the name of a file or
files to edit.  On-line help is available from the pulldown menu on the far
right of the menu bar.  For more information on the syntax of the nedit command
line, look under the heading of "NEdit Command Line."


COMPATIBILITY WITH PREVIOUS VERSIONS

Existing .nedit Files

NEdit 5.0.2 is backward-compatible with .nedit files from older versions
(unless you wrote a .nedit file from the 5.0 beta-test version, or the
experimental syntax highlighting version, as discussed below).  However, if you
are upgrading from a pre-5.0 version, you should check your font settings, and
consider upgrading the original default macro menu entries as discussed below.

If you have been using a font other than the default for the text portion of
your NEdit windows, be sure to check the Preferences -> Default Settings ->
Text Font dialog, and select highlighting fonts which match your primary font
in size.  Matching in height is desirable, but not essential, and sometimes
impossible to achive on some systems.  When fonts don't match in height,
turning on syntax highlighting will cause the window size to change slightly. 
NEdit can handle unmatched font sizes (width), but leaving them unmatched means
sometimes columns and indentation don't line up (as with proportional fonts).

Most macros written for previous versions will function properly under 5.0's
new macro language.  The most common problems with old macros is lack of a
terminating newline on the last line of the macro, and the addition of "<" and
">" to the regular expression syntax.  These characters must now be escaped
with \ (backslash).

The default macros written from 4.0 versions all work under 5.0, with the
exception of "Unquote Mail Reply", which will fail because it uses the ">"
character in a regular expression, which now must be escaped with "\".  If you
wrote a .nedit file from 4.0, you will have the old version of the macro, which
needs to be updated.

The 5.0 defaults for macro menu entries also contain some worthwhile new
commands, and improvements to existing macros.  To see what these new macros
look like, you can temporarily re-name your existing .nedit file and run NEdit
without one.

There are several ways to integrate macros from the new version into an
old .nedit file.  If you have not added new macros of your own, simply remove
the line beginning "nedit.macroCommands" and all of the indented lines which
follow it from your existing .nedit file, and NEdit will re-generate the Macro
menu from its stored defaults.

If you have added macros of your own:

   1) Temporarily re-name your existing .nedit file
   2) Generate a new .nedit file by choosing Save Defaults from the
      Preferences menu.
   3) Copy and paste the new macros from the newly generated .nedit
      file into the "nedit.macroCommands" resource in your old .nedit file.

Beta 5.0 .nedit Files

If you wrote a .nedit file from the beta-test version of 5.0, you will be
missing one or two highlight styles used by default highlight patterns for
Perl, Verilog, and NEdit Macro, and you will get an error on the FORTRAN
highlight patterns, because the name has changed to "Fortran".  If you want to
preserve your existing .nedit file, you can edit it by hand to change the two
occurences of "FORTRAN" to "Fortran", and either remove the section beginning
"nedit.styles", or if you have made changes to styles that you want to
preserve, re-name your .nedit file, write a new one, and integrate the
new styles into your existing file.

Experimental Syntax Highlighting Version .nedit Files

If you wrote a .nedit file using the experimental syntax highlighting version
(color_nedit.tar), the syntax of the languageModes resource has changed, and is
not readable with 5.0.  If you want to preserve the .nedit file, you will have
to edit it by hand to remove the line beginning "nedit.languageModes", and all
of the indented lines that follow.  If you made significant changes to language
mode information which you don't want to re-enter via the Language Modes
dialog, you can edit each line of the resource by hand to conform to the new
spec by adding colons to the end).


FURTHER INFORMATION

More information is available in the file nedit.doc in this kit, from NEdit's
on-line help system, and from the enclosed FAQ file.  There is also a web page
for NEdit at: http://www-pat.fnal.gov/nirvana/nedit.html, or find out more
about Fermilab: http://www.fnal.gov, or information on other publicly available
Fermilab software: http://www.fnal.gov/fermitools.  For discussion with other
NEdit users, or to receive notification of new releases and news about news,
you can subscribe to one or both of the official nedit mailing lists.  You'll
find information on subscribing in the NEdit on-line help under Mailing Lists.  


SUPPORT

Help with the installation or use of NEdit is available by sending mail to

                        [email protected]

which is auto-forwarded to the group in charge of NEdit support at Fermilab.

This software is furnished by Fermilab on an "as is" basis as a service 
to the wider community with the goal of stimulating collaborative use and 
further development.

Provision of the software implies no commitment of support by Fermilab.

The Fermilab Computing Division is open to discussing other levels of 
support for use of the software with responsible and committed users and 
collaborators.

Use of the software in experiments at Fermilab will be assured of a level 
of support as agreed to through the standard Memorandum Of Understanding 
process.

Users may send mail to the mail address given above, with the expectation 
that it will be read and noted.

Fermitools Special Products

Because of the special support needed for a few selected products Fermilab 
is only able to support the software under special agreement. The support 
offered will be discussed and negotiated on an individual basis and may be 
different for different users.  To initiate discussions send mail to the 
mail address given above.


----------------------------------------------------------------------------

                         TERMS AND CONDITIONS IN FULL
                         ============================

----------------------------------------------------------------------------
    Fermitools Software Legal Information - October 16, 1997
----------------------------------------------------------------------------

COPYRIGHT STATUS:  Fermi National Accelerator Laboratory (FNAL) documents are
sponsored by the U.S. Department of Energy under Contract No.
DE-AC02-76CH03000.  Therefore, the U.S. Government retains a non-exclusive,
royalty-free license to publish or reproduce these documents or software for
U.S. Government purposes.  All documents and software available from this
server are protected under the U.S. and Foreign Copyright Laws, and FNAL
reserves all rights.

Terms and Conditions
--------------------
When a User distributes or otherwise obtains a software package included in
the Fermilab Software Tools Program, the user agrees to abide by the Terms and
Conditions of the Program below:

o   Any redistribution of the software shall be accompanied by this
    INFORMATION/LICENSE file and the product's ORIGIN file.

o   The User shall acknowledge the origin of the software as set forth 
    below:

        "This work was performed at Fermi National Accelerator Laboratory, 
        operated by Universities Research Association, Inc., under contract 
        DE-AC02-76CH03000 with the U.S. Department of Energy."

o   The user is asked to feed back problems, benefits, and/or suggestions 
    about the software to the Fermilab Software Providers and/or Fermitools 
    management.

o   Any distribution of the software available from this server shall be at
    no charge, except for nominal media and distribution costs.  To obtain a
    license to commercialize any of the software programs available from this
    server, contact FNAL's Office of Research and Technology Applications,
    P.O. Box 500, MS-200, Batavia, IL 60510-0500.


Indemnification by User of Third Party Claims and Disclaimer of Liability
-------------------------------------------------------------------------
The User, his/her directors, officers, employees, and agents hereby release
and waive all claims against Universities Research Association, Inc. (URA)
operator of Fermi National Accelerator Laboratory, its trustees, overseers,
directors, officers, employees, agents, subcontractors, successors and
assigns, for any and all liability and damages arising from the reproduction,
use or other disposition of the software.  The User shall indemnify URA and
the U.S. Government for all damages, costs or expenses, including attorney's
fees, arising from the utilization of the software, including, but not limited
to, the making, using, selling or exporting of products, processes or services
derived from the Software.  The User agrees to indemnify, hold harmless and
defend URA, its trustees, overseers, directors, officers, employees, agents,
subcontractors, successors and assigns, against any and all liability, damage,
loss, cost, charge, claim, demand, fee or expense of every nature and kind
which may at any time hereafter, be sustained by URA by reason of claims of
third parties arising out of alleged acts or omissions of the User in the
reproduction, use or other disposition of the Software.  

The User agrees that URA, its trustees, overseers, directors, officers,
employees, agents, subcontractors, successors and assigns shall not be liable
under any claim, charge, or demand, whether in contract, tort, criminal law,
or otherwise, for any and all loss, cost, charge, claim, demand, fee, expense,
or damage of every nature and kind arising out of, connected with, resulting
from or sustained as a result of the use of the software programs available
from this server.  In no event shall URA be liable for special, direct,
indirect or consequential damages, losses, costs, charges, claims, demands,
fees or expenses of any nature or kind.

Disclaimer of Warranties
------------------------
The software is provided on an "as is" basis only.  URA makes no
representations, express or implied.  URA MAKES NO REPRESENTATIONS OR
WARRANTIES OF MERCHANTABILITY OR FITNESS FOR ANY PARTICULAR PURPOSE, or
assumes any legal liability or responsibility for the accuracy, completeness,
or usefulness of any information, apparatus, product or process disclosed, or
represents that the Software will not infringe any privately held patent,
copyright, or trademark.  The entire risk as to the results and the
performance of this software is assumed by the User.

Disclaimer of Endorsement
-------------------------
Reference herein to any specific commercial products, process, or service by
tradename, trademark, manufacturer or otherwise, does not constitute or imply
its endorsement, recommendation, or favoring by the United States Government,
U.S. Department of Energy or URA.  The views and opinions of individuals
expressed herein do not necessarily state or reflect those of the United
States Government, U.S. Department of Energy or URA and shall not be used for
advertising or product endorsement purposes.

Liabilities of the Government
-----------------------------
This software is provided by URA, independent from its Prime Contract with the
U.S. Department of Energy.  URA is acting independently from the Government
and in its own private capacity and is not acting on behalf of the U.S.
Government, nor as its contractor nor its agent.  Correspondingly, it is
understood and agreed that the U.S. Government has no connection to this
software and in no manner whatsoever shall be liable for nor assume any
responsibility or obligation for any claim, cost, or damages arising out of or
resulting from the use of the software available from this server.