Go to file
Benno Schulenberg 4761e00852 syntax: nanorc: don't color parts of valid strings as if invalid
It's better to color some invalid things as if valid than the other
way around.  So, as strings can validly contain any number of double
quotes, just accept *anything* between the delimiting double quotes
and demand that the closing quote is followed by whitespace or EOL.
2017-12-03 20:09:47 +01:00
doc bump version numbers and add a news item for the 2.9.1 release 2017-11-27 19:06:26 +01:00
m4 drop the glib fallback for snprintf/vsnprintf 2017-03-06 12:01:17 +01:00
po po: update translations and regenerate POT file and PO files 2017-11-27 19:21:00 +01:00
src tweaks: elide two variables that are used just once 2017-12-02 18:07:50 +01:00
syntax syntax: nanorc: don't color parts of valid strings as if invalid 2017-12-03 20:09:47 +01:00
.gitignore add support for gnulib 2017-03-06 11:56:02 +01:00
AUTHORS docs: update the list of who authored what 2017-04-25 20:32:05 +02:00
autogen.sh gnulib: pull in the fix for the missing stat include 2017-11-30 21:27:08 +01:00
ChangeLog bump version numbers and add a news item for the 2.9.1 release 2017-11-27 19:06:26 +01:00
ChangeLog.1999-2006 tweaks: fix some inconsistencies in an old Changelog 2017-04-07 21:22:55 +02: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.9.1 release 2017-11-27 19:06:26 +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 the 2.9.0 release 2017-11-18 11:33:28 +01:00
Makefile.am add support for gnulib 2017-03-06 11:56:02 +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.9.1 release 2017-11-27 19:06:26 +01:00
README copyright: update the years, use ranges, and explain this usage 2017-04-09 12:09:23 +02:00
README.GIT docs: make it clearer that a Signed-off-by is wanted on patches 2017-11-12 11:54:17 +01:00
THANKS restore the GNU marker in nano's name 2016-08-14 21:42:37 +02:00
TODO docs: update the list of who authored what 2017-04-25 20:32:05 +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

	Since version 2.5.0, GNU nano has abandoned the distinction between
	a stable and a development branch: it is now on a "rolling" release
	-- fixing bugs and adding new features go hand in hand.

Copyright Years

	When in any file of this package a copyright notice mentions a
	year range (such as 1999-2011), it is a shorthand for a list of
	all the years in that interval.