nano, but smaller
 
 
 
 
 
Go to file
Benno Schulenberg 91951ab22a input: don't bother putting a keycode into byte range
A keycode is either already in byte range (so there is nothing to do)
or it is not and it shouldn't be (so there is nothing to do either).
2016-07-30 12:19:47 +02:00
doc bump version numbers and add a news item for 2.6.2 2016-07-28 09:21:27 +02: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-07-28 09:38:30 +02:00
src input: don't bother putting a keycode into byte range 2016-07-30 12:19:47 +02:00
.gitignore build-sys: ignore the revision header file 2016-07-16 13:29:13 +02:00
AUTHORS Removing two SVN Id tags and a duplication. 2016-02-10 16:40:08 +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 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.6.2 2016-07-28 09:21:27 +02:00
Makefile.am docs: rename a file, to be less confusing 2016-06-17 11:12:37 +02:00
NEWS docs: tweak some spacing and spelling 2016-07-29 09:05:40 +02:00
README docs: use https for nano-editor.org, and drop the www 2016-06-23 19:51:01 +02:00
README.GIT remove the GNU marker from nano's name 2016-06-13 12:22:33 +02:00
THANKS remove the GNU marker from nano's name 2016-06-13 12:22:33 +02:00
TODO TODO: tidy up the punctuation 2016-05-05 13:00:20 +02:00
autogen.sh more svn->git updates 2016-04-17 23:39:07 -04:00
configure.ac bump version numbers and add a news item for 2.6.2 2016-07-28 09:21:27 +02:00
nano-regress 2014-05-29 Chris Allegretta <chrisa@asty.org> 2014-05-29 18:30:23 +00:00
nano.spec.in docs: bump pointers to the newest version available 2016-06-23 19:53:58 +02:00

README

	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

	https://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

	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.