Go to file
Benno Schulenberg b3bcc8eeac painting: make use of the multidata of the preceding line
When painting a line, the multidata of the line /before/ it is valid
in most cases: it was determined just a moment ago.  And it tells us
all we need to know: whether there is an unpaired start match before
the current line or not.

The only exception is when painting the first line of the screen:
the multidata of the line before it might be stale.  So for the
first screen line we will always have to do some backtracking.
But that is left for later.

This fixes https://savannah.gnu.org/bugs/?50121.
2017-02-12 18:24:49 +01:00
doc tweaks: fiddle with some wordings in the texinfo document 2017-02-12 12:06:44 +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 2017-01-10 11:35:00 +01:00
src painting: make use of the multidata of the preceding line 2017-02-12 18:24:49 +01:00
syntax syntax: html: be more precise with tags, and paint attribute names 2017-01-08 11:32:30 +01:00
.gitignore build-sys: ignore the revision header file 2016-07-16 13:29:13 +02:00
AUTHORS build: rename the sample config file, so it will be colored like a nanorc 2016-12-30 22:05:01 +01:00
autogen.sh more svn->git updates 2016-04-17 23:39:07 -04:00
ChangeLog bump version numbers and add a news item for the 2.7.4 release 2017-01-10 11:29:34 +01:00
ChangeLog.1999-2006 docs: rename the Changelogs to indicate which periods they cover 2017-01-04 16:01:50 +01:00
ChangeLog.2007-2015 docs: rename the Changelogs to indicate which periods they cover 2017-01-04 16:01:50 +01:00
configure.ac bump version numbers and add a news item for the 2.7.4 release 2017-01-10 11:29:34 +01: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
IMPROVEMENTS bump version numbers and add a news item for 2.7.2 2016-12-12 15:05:34 +01:00
Makefile.am build: include the old Changelogs in the tarball 2017-01-06 19:31:48 +01:00
nano-regress 2014-05-29 Chris Allegretta <chrisa@asty.org> 2014-05-29 18:30:23 +00:00
nano.spec.in build: rename the sample config file, so it will be colored like a nanorc 2016-12-30 22:05:01 +01:00
NEWS bump version numbers and add a news item for the 2.7.4 release 2017-01-10 11:29:34 +01:00
README build: rename the sample config file, so it will be colored like a nanorc 2016-12-30 22:05:01 +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

		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/sample.nanorc 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.