nano, but smaller
 
 
 
 
 
Go to file
David Lawrence Ramsey 87fbe24283 docs: add info about Slang to README.GIT, and improve info about glib2
For UTF-8 support under Slang, at least Slang 2.0 is needed.
And glib2 is also used for snprintf() if it's unavailable.
2016-11-29 12:28:23 +01:00
doc syntax: avoid using black colors 2016-11-23 21:08:59 +01:00
m4 Compiling with warnings enabled by default, to help prevent 2014-03-24 13:31:37 +00:00
po po: update translations and regenerate POT file and PO files 2016-10-29 11:53:44 +02:00
src files: give feedback when restricted mode prevents overwriting a file 2016-11-29 12:08:39 +01:00
.gitignore build-sys: ignore the revision header file 2016-07-16 13:29:13 +02:00
AUTHORS bump version numbers and add a news item for 2.7.1 2016-10-29 11:11:33 +02: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 tweaks: add a reporter's name 2016-06-25 20:03:25 +02:00
ChangeLog.pre-2.1 all: eradicate SVN's $Id$ tags 2016-04-05 14:59:12 +02:00
IMPROVEMENTS bump version numbers and add a news item for 2.7.1 2016-10-29 11:11:33 +02:00
Makefile.am docs: rename a file, to be less confusing 2016-06-17 11:12:37 +02:00
NEWS bump version numbers and add a news item for 2.7.1 2016-10-29 11:11:33 +02:00
README docs: harmonize the indentation of the README, and tweak some wordings 2016-11-13 20:35:19 +01:00
README.GIT docs: add info about Slang to README.GIT, and improve info about glib2 2016-11-29 12:28:23 +01:00
THANKS restore the GNU marker in nano's name 2016-08-14 21:42:37 +02:00
TODO docs: brush up the TODO list 2016-09-08 12:11:38 +02:00
autogen.sh more svn->git updates 2016-04-17 23:39:07 -04:00
configure.ac configure: fix ncurses lib symbol checking 2016-11-23 14:26:03 -05:00
nano-regress 2014-05-29 Chris Allegretta <chrisa@asty.org> 2014-05-29 18:30:23 +00:00
nano.spec.in restore the GNU marker in nano's name 2016-08-14 21:42:37 +02: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 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 xvzf 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 file to
	your home directory, rename it to ".nanorc", and then edit it
	according to your taste.

Web Page

	https://nano-editor.org/

Mailing Lists

	There are three nano-related mailing-lists.

	+ info-nano@gnu.org is a very low traffic list used to announce
	  new nano versions or other important info 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.

Bug Reports

	To report a bug, please file a description of the problem on nano's
	bug tracker (https://savannah.gnu.org/bugs/?group=nano -- hover on
	"Bugs", then click "Submit new").  The issue may have already been
	reported, so please look first.

Current Status

	GNU nano has reached its seventh milestone, 2.6.x.  Since 2.5.0, it
	is a "rolling" release: bug fixing and development go hand in hand.