Welcome to ne, the nice editor. Documentation (in the "doc" directory) is provided in the form of a texinfo file. It can be printed as a manual using TeX and GNU's texinfo.tex macro package, or turned into a hypertext document using GNU's makeinfo. You will then need info, the GNU hypertext reader, to read it. A ready-to-use hypertext version of the documentation is contained in the ne.info* files (just use "info -f ne" to read it) and in the html files (just read ne_toc.html with any browser). A PostScript file with an a4 ready-to-print version of the documentation that uses the standard Times and Courier fonts is also included. As a last chance, ne.txt is a purely ASCII version. The "terms" directory contains the terminfo sources for a couple of common terminals. They include a much larger number of key capabilities than usually found. They can be compiled locally with tic so to be able to use additional keys (such as the keypad home key). If you have a POSIX compliant machine with a terminfo database, a recompilation of ne's sources on your machine will suffice for making it work (just cd into the "src" directory and start make). If you have a termcap database, you should use the "termcap" target (i.e., type "make termcap"). It uses the GNU version of termcap, whose sources are included (no library is needed). In general, if a compilation fails you should try the following targets: none, "noposix", "termcap" and "termcapnoposix". They use slightly different #define's to overcome the slight differences among systems. If you have problem with the local compiler and have the GNU compiler installed, try CC=gcc, and possibly also OPTS=-ansi. If you are compiling under Cygwin or similar emulations of UN*X running under other operating systems, you can use the "ansi" target to build a copy of ne that will use built-in ANSI terminal control sequences if a terminal database cannot be found. This is very useful because you get a completely stand-alone ne (the "ansi" target uses the termcap database, so no library is necessary). If something does not work, please feel free to e-mail us. Compatibility problems are also discussed in the documentation. Don't be alarmed if you get a lot of warnings. If the symbol NODEBUG is not defined during the compilation, a number of assertions will be compiled into the program. This can be useful for the first tests, but should be avoided in common usage. seba (vigna@dsi.unimi.it) Todd (Todd_Lewis@unc.edu)
