Go to file
Benno Schulenberg 3de2c704ef Adding a linter definition to four of the syntax files.
Patch by Mark Oteiza.


git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@5203 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2015-04-18 11:35:23 +00:00
doc Adding a linter definition to four of the syntax files. 2015-04-18 11:35:23 +00:00
m4 Compiling with warnings enabled by default, to help prevent 2014-03-24 13:31:37 +00:00
po GNU nano 2.4.1 release 2015-04-14 18:03:44 +00:00
src Arranging the movement keys in the File Browser in the order of 2015-04-17 10:06:03 +00:00
.gitignore Ignoring the autotools 'compile' file. Patch by Mike Frysinger. 2015-02-16 20:13:29 +00:00
AUTHORS Until someone else wants the job 2014-02-07 14:57:49 +00:00
autogen.sh Make it much simpler by just using autoreconf. 2003-01-15 17:38:38 +00:00
ChangeLog Adding a linter definition to four of the syntax files. 2015-04-18 11:35:23 +00:00
ChangeLog.pre-2.1 fix changelog entry 2007-12-17 23:05:11 +00:00
configure.ac GNU nano 2.4.1 release 2015-04-14 18:03:44 +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
Makefile.am Stopping to distribute the obsolete BUGS file, and removing it from SVN. 2014-06-27 20:20:14 +00:00
nano-regress 2014-05-29 Chris Allegretta <chrisa@asty.org> 2014-05-29 18:30:23 +00:00
nano.spec.in 2015-02-09 Chris Allegretta <chrisa@asty.org> 2015-02-09 19:53:29 +00:00
NEWS GNU nano 2.4.1 release 2015-04-14 18:03:44 +00:00
README Go even farther on the bug report front in README and only mention 2015-04-14 16:07:23 +00:00
README.SVN Building nano from svn does not require ssh. 2014-04-15 12:13:04 +00:00
THANKS Giving the file a neater layout, plus two table headers. 2015-04-07 15:37:07 +00:00
TODO GNU nano 2.2.5 release 2010-08-06 01:20:51 +00:00
UPGRADE 2009-12-01 David Lawrence Ramsey <pooka109@gmail.com> 2009-12-02 03:36:22 +00:00

	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 was 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
     providing other extra functionality.

     The nano editor is 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 haven't configured with the "--disable-nanorc" option, after
     installation you may want to 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 Lists 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 <name>-request@gnu.org with a
	subject of "subscribe", where <name> is the list you want to
	subscribe to.

	For general bug reports, please file a description of the problem
	on the Savannah bug tracker page for nano
	(https://savannah.gnu.org/bugs/?group=nano).  The issue may have
	already been reported, and we are better able to track the state
	of the issue and whom to notify when fixed, the more the bug
	tracker is used.

Current Status

	GNU nano has reached its fifth stable milestone, 2.4.x.
	Development of new features will continue in the 2.5.x branch,
	while 2.4.x versions are dedicated to bug-fixing and polishing.