nano, but smaller
 
 
 
 
 
Go to file
David Lawrence Ramsey 9fff4e1a10 update maintenance information
git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@4210 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2007-12-20 18:41:04 +00:00
doc update maintenance information 2007-12-20 18:41:04 +00:00
m4 import the latest version of glib-2.0.m4 2007-01-01 14:25:58 +00:00
po 2007-12-09 Jordi Mallach <jordi@gnu.org> 2007-12-09 17:12:03 +00:00
src in print_opt_full(), use strlenpt() instead of strlen(), so that tabs 2007-12-18 22:00:17 +00:00
.cvsignore Get rid of config.rpath. 2004-11-20 00:39:02 +00:00
AUTHORS update maintenance information 2007-12-20 18:41:04 +00:00
BUGS more miscellaneous cosmetic fixes 2006-11-21 04:11:18 +00:00
COPYING convert to GPLv3 or later 2007-08-11 05:17:36 +00:00
COPYING.DOC convert documentation to GPLv3/GFDLv1.2 2007-08-23 04:34:35 +00:00
ChangeLog update maintenance information 2007-12-20 18:41:04 +00:00
ChangeLog.pre-2.1 fix changelog entry 2007-12-17 23:05:11 +00:00
Makefile.am convert documentation to GPLv3/GFDLv1.2 2007-08-23 04:34:35 +00:00
NEWS resync NEWS with NEWS from the 2.0 branch 2007-12-17 23:07:49 +00:00
README fork the 2.1 branch of nano 2007-01-29 12:40:48 +00:00
README.CVS fork the 2.1 branch of nano 2007-01-29 12:40:48 +00:00
THANKS Update Swedish credits. 2006-03-15 22:44:43 +00:00
TODO in TODO, add entries for fixing limitations with pasting text and 2007-04-23 15:39:01 +00:00
UPGRADE update UPGRADE to fix the description of +LINE,COLUMN 2006-07-22 15:57:28 +00:00
autogen.sh Make it much simpler by just using autoreconf. 2003-01-15 17:38:38 +00:00
configure.ac cosmetic fixes 2007-12-20 17:06:01 +00:00
nano.spec.in clean up nano.spec.in some more 2006-11-05 17:13:44 +00:00

README

	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 go
     to 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.
     
     If you configured with the "--enable-nanorc" option, after
     installation you might copy the doc/nanorc.sample to your home
     directory, rename it to ".nanorc", and then edit it according to
     your taste.

Web Page

	http://www.nano-editor.org/

Mailing List and Bug Reports

	Savannah hosts all the nano-related mailing-lists.

	+ info-nano@gnu.org is a very low traffic list
	  used to announce new nano versions or other important
	  information about the project.
	+ help-nano@gnu.org is for those seeking to get help without
	  wanting to hear about the technical details of its
	  development.
	+ nano-devel@gnu.org 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@gnu.org 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

	GNU nano has reached its third stable milestone, 2.0.x.
	Development of new features continues in the 2.1.x branch, while
	2.0.x versions are dedicated to bug-fixing and polishing.

$Id$