nano, but smaller
 
 
 
 
 
Go to file
David Lawrence Ramsey ce0451348c make do_prev_word() work with multibyte strings, and update various
comments in do_next_word() and do_prev_word()


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@2273 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2005-01-15 00:34:57 +00:00
doc update more documentation dealing with double-Escape and verbatim input 2005-01-03 20:07:26 +00:00
m4 in m4/Makefile.am, add glib-2.0.m4 to EXTRA_DIST, so that nano builds 2004-11-11 14:35:31 +00:00
po Updated Italian translation. 2004-12-15 19:42:07 +00:00
src make do_prev_word() work with multibyte strings, and update various 2005-01-15 00:34:57 +00:00
.cvsignore Get rid of config.rpath. 2004-11-20 00:39:02 +00:00
AUTHORS Update stable/development series maintainership in the AUTHORS file 2003-08-12 02:37:01 +00:00
BUGS DLR and DB fixes mega-merge 2002-07-19 01:08:59 +00:00
ChangeLog make do_prev_word() work with multibyte strings, and update various 2005-01-15 00:34:57 +00:00
Makefile.am in m4/Makefile.am, add glib-2.0.m4 to EXTRA_DIST, so that nano builds 2004-11-11 14:35:31 +00:00
NEWS GNU nano 1.3.5 2004-11-22 17:55:17 +00:00
README minor capitalization fixes 2004-03-03 01:25:46 +00:00
README.CVS documentation fix: list sh as an example of a Bourne shell 2004-11-21 18:51:30 +00:00
THANKS Update docs about Chinese contributor. 2004-06-01 15:29:31 +00:00
TODO implement verbatim input for the statusbar prompt 2005-01-02 21:26:53 +00:00
UPGRADE Sigh. It's nanorc.sample... 2003-03-24 13:09:26 +00:00
autogen.sh Make it much simpler by just using autoreconf. 2003-01-15 17:38:38 +00:00
configure.ac massive updates to multibyte/wide character support; deal with multibyte 2005-01-12 03:25:57 +00:00
nano.spec.in tweak the spec file to properly package the "rnano" symlink 2004-08-01 22:00:29 +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 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

	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 second major milestone, 1.2.x.
	Development of new features will continue in the 1.3.x branch,
	while 1.2.x versions will be dedicated to bugfixing and
	polishing.

   Chris Allegretta (chrisa@asty.org)

$Id$