"src/files.c" did not exist on "6fe61499e8809a9b34a337379f9e47a39dae27f8"
All the updates that I've been waiting all weekend to commit, no desc, tough
Chris Allegretta authored
git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@668 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
6fe61499
Name Last commit Last update
intl Back to the 1.0 version of gettext, I can't figure this one out to save my life =(
po All the updates that I've been waiting all weekend to commit, no desc, tough
.cvsignore
ABOUT-NLS More RCS schtuff
AUTHORS Added Rocco to AUTHORS
BUGS Add BUG #60
COPYING Initial revision
ChangeLog All the updates that I've been waiting all weekend to commit, no desc, tough
INSTALL More RCS schtuff
Makefile.am Add color changes, undocumented and ugly, but hey maybe people want to see what chap I wrote so far
Makefile.in I'm back to the older gettext, sync these files too
NEWS Various spelling updates by David Lawrence Ramsey
README Various spelling updates by David Lawrence Ramsey
TODO All the updates that I've been waiting all weekend to commit, no desc, tough
acconfig.h Add color changes, undocumented and ugly, but hey maybe people want to see what chap I wrote so far
aclocal.m4 I'm back to the older gettext, sync these files too
color.c I should actually add the file to the tree
config.guess Newer config.guess and config.sub
config.h.in I'm back to the older gettext, sync these files too
config.sub Newer config.guess and config.sub
configure New Russian translation by Sergey A. Ribalchenko.
configure.in New Russian translation by Sergey A. Ribalchenko.
cut.c Changed all string allocations to charalloc(), new function designed to take nmalloc argument but call calloc based on (char *) size.
faq.html Various spelling updates by David Lawrence Ramsey
files.c All the updates that I've been waiting all weekend to commit, no desc, tough
global.c
install-sh
missing
mkinstalldirs
move.c
nano.1
nano.1.html
nano.c
nano.h
nano.info
nano.texi
proto.h
rcfile.c
search.c
stamp-h.in
texinfo.tex
utils.c
winio.c
	GNU nano - an enhanced clone of the Pico text editor.

Overview

     The nano project was started because of a few "problems" with the
     wonderfully easy-to-use and friendly Pico text editor.

     First and foremost is its license: the Pine suite does not use the
     GPL or a GPL-friendly license, and has unclear restrictions on 
     redistribution.  Because of this, Pine and Pico are not included with
     many GNU/Linux distributions.  Also, other features (like goto line
     number or search and replace) were unavailable until recently or
     require a command line flag.  Yuck.

     nano aims to solve these problems by emulating the functionality of
     Pico as closely as possible while addressing the problems above and
     perhaps providing other extra functionality.

     The nano editor is now an official GNU package.  For more information
     on GNU and the Free Software Foundation please see http://www.gnu.org.
     
How to compile and install nano

     Download the nano source code, then:
     tar zxvf nano-x.y.z.tar.gz
     cd nano-x.y.z
     ./configure
     make
     make install
     
     It's that simple. Use --prefix with configure to override the 
     default installation directory of /usr/local.
     
Web Page

	http://www.nano-editor.org
     
Mailing List and Bug Reports

	SourceForge hosts all the nano-related mailing-lists.
	+ nano-announce@lists.sourceforge.net is a very low traffic list
	  used to announce new Nano versions or other important information
	  about the project.
	+ nano-devel@lists.sourceforge.net is the list used by the people
	  that make Nano and a general development discussion list, with
	  moderate traffic.
	To subscribe, send email to nano-<name>-request@lists.sourceforge.net
	with a subject of "subscribe", where <name> is the list you want to
	subscribe to.
	For general bug reports, send a description of the problem to
	nano@nano-editor.org or directly to the development list.

Current Status

	This is the 1.1 or unstable branch of nano.  New features
	will be added and things will be changed around and basically
	stabiliity is not guaranteed.  If this is not what you're
	interested in, please use the latest 1.0.x release of nano.

   Chris Allegretta (chrisa@asty.org)

$Id$