Go to file
Benno Schulenberg d7a5bacf15 po: update translations and regenerate POT file and PO files 2019-03-24 12:47:41 +01:00
doc bump version numbers and add a news item for the 4.0 release 2019-03-24 12:14:12 +01:00
m4
po po: update translations and regenerate POT file and PO files 2019-03-24 12:47:41 +01:00
src tweaks: adjust indentation after previous change, and rename a parameter 2019-03-24 09:42:57 +01:00
syntax syntax: nanorc: stop coloring 'unset fill ...' as if it were valid 2019-03-09 09:27:08 +01:00
.gitignore
AUTHORS docs: register Marco as the author of the filtering feature 2018-06-01 10:00:08 +02:00
COPYING
COPYING.DOC
ChangeLog bump version numbers and add a news item for the 4.0 release 2019-03-24 12:14:12 +01:00
ChangeLog.1999-2006 credits: sort the names roughly according to amount of influence 2018-05-16 12:05:40 +02:00
ChangeLog.2007-2015 tweaks: remove two superfluous assignments 2018-06-02 19:32:54 +02:00
IMPROVEMENTS bump version numbers and add a news item for the 4.0 release 2019-03-24 12:14:12 +01:00
Makefile.am
NEWS bump version numbers and add a news item for the 4.0 release 2019-03-24 12:14:12 +01:00
README tweaks: reword the description of the disadvantages of Pico 2019-01-25 11:00:51 +01:00
README.GIT
THANKS docs: thank Kamil for his bug fixes, and update an email address 2018-05-16 09:57:02 +02:00
TODO docs: mark the filtering of text through an external command as done 2018-05-27 19:33:04 +02:00
autogen.sh gnulib: update to its current upstream state 2019-03-11 08:29:50 +01:00
configure.ac bump version numbers and add a news item for the 4.0 release 2019-03-24 12:14:12 +01:00
nano-regress
nano.spec.in
roll-a-release.sh build: ensure that also new PO files are committed to git 2019-03-24 12:40:05 +01:00

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.