You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Benno Schulenberg 11aa191bdc tweaks: rename a variable, to distinguish it from a browser function 6 hours ago
doc docs: put the 'set guidestripe' option into its alphabetical position 6 days ago
m4 drop the glib fallback for snprintf/vsnprintf 2 years ago
po po: update translations and regenerate POT file and PO files 1 week ago
src tweaks: rename a variable, to distinguish it from a browser function 6 hours ago
syntax syntax: c: change the highlighting of preprocessor directives 2 weeks ago
.gitignore add support for gnulib 2 years ago
AUTHORS docs: register Marco as the author of the filtering feature 10 months ago
COPYING convert to GPLv3 or later 11 years ago
COPYING.DOC convert documentation to GPLv3/GFDLv1.2 11 years ago
ChangeLog bump version numbers and add a news item for the 4.1 release 1 week ago
ChangeLog.1999-2006 credits: sort the names roughly according to amount of influence 11 months ago
ChangeLog.2007-2015 tweaks: remove two superfluous assignments 10 months ago
IMPROVEMENTS bump version numbers and add a news item for the 4.0 release 4 weeks ago
Makefile.am add support for gnulib 2 years ago
NEWS bump version numbers and add a news item for the 4.1 release 1 week ago
README tweaks: reword the description of the disadvantages of Pico 2 months ago
README.GIT tweaks: use for git the more faithful "less -x1,5" suggested by Brand 1 year ago
THANKS docs: thank Kamil for his bug fixes, and update an email address 11 months ago
TODO docs: mark the filtering of text through an external command as done 11 months ago
autogen.sh gnulib: update to its current upstream state 1 week ago
configure.ac bump version numbers and add a news item for the 4.1 release 1 week ago
nano-regress 2014-05-29 Chris Allegretta <chrisa@asty.org> 4 years ago
nano.spec.in build: fix the source URL in the spec file 1 year ago
roll-a-release.sh build: be more specific and avoid committing accidentally changed files 6 days ago

README


GNU nano -- a simple editor, inspired by Pico

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, and (before using the Apache License) it had unclear
restrictions on redistribution. Because of this, Pine and Pico
were not included in many GNU/Linux distributions. Furthermore,
some features (like go-to-line-number or search-and-replace) were
unavailable for a long time or require a command-line flag. Yuck.

Nano aimed to solve these problems by: 1) being truly free software
by using the GPL, 2) emulating the functionality of Pico as closely
as is reasonable, and 3) include extra functionality by default.

Nowadays, nano wants to be a generally useful editor, with default
settings that do not change the file contents automatically.

The nano editor is an official GNU package. For more information on
GNU and the Free Software Foundation, please see https://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.