Go to file
Benno Schulenberg d01dbbb284 rcfile: do not complain when "bright" is used with a background color
A background color *can* be bright (in the sense of lighter, shinier).
It's just that the background cannot be bold.  Only the typeface used
on the foreground can be bold (if the terminal supports it).  So, let
"bright", when used with a background color, simply mean "light".
2020-06-14 12:05:18 +02:00
doc docs: document the --indicator (-q) and 'set indicator' options 2020-06-04 18:52:28 +02:00
m4 tweaks: delete another pointless ChangeLog 2020-03-26 13:17:41 +01:00
po tweaks: delete a ChangeLog that is no longer updated and is incomplete 2020-03-26 13:17:21 +01:00
src rcfile: do not complain when "bright" is used with a background color 2020-06-14 12:05:18 +02:00
syntax rcfile: introduce the modifier "bold", for specifying bolding separately 2020-06-14 11:54:18 +02:00
.gitignore add support for gnulib 2017-03-06 11:56:02 +01:00
AUTHORS docs: note Marco as the original author of the bookmarking code 2020-04-16 11:05:14 +02:00
autogen.sh gnulib: update to its current upstream state 2020-03-17 09:56:54 +01:00
ChangeLog tweaks: fix twenty typos, in old Changelogs and in some comments 2020-03-25 16:57:43 +01:00
ChangeLog.1999-2006 tweaks: for each version, mention the changes to the PO files last 2020-03-26 12:18:22 +01:00
ChangeLog.2007-2015 tweaks: fix twenty typos, in old Changelogs and in some comments 2020-03-25 16:57:43 +01:00
configure.ac build: stop distributing a nano.spec file 2020-03-26 17:08:36 +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 docs: reduce the TODO file to a reference to the bug tracker on Savannah 2020-03-26 19:27:46 +01:00
Makefile.am build: stop distributing a nano.spec file 2020-03-26 17:08:36 +01:00
nano-regress 2014-05-29 Chris Allegretta <chrisa@asty.org> 2014-05-29 18:30:23 +00:00
NEWS docs: copy the 4.9.3 news item from the release branch 2020-05-24 09:01:53 +02:00
README docs: adjust the compilation instructions to two-digit version numbers 2019-10-27 19:21:55 +01:00
README.GIT docs: mention that gcc must be at least version 5.0 2019-09-23 13:50:51 +02:00
roll-a-release.sh bump version numbers and add a news item for the 4.9 release 2020-03-24 11:11:22 +01:00
THANKS tweaks: sort three translator names better 2019-06-06 15:22:02 +02:00
TODO docs: reduce the TODO file to a reference to the bug tracker on Savannah 2020-03-26 19:27:46 +01:00

          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) including extra functionality by default.

    Nowadays, nano wants to be a generally useful editor with sensible
    defaults (linewise scrolling, no automatic line breaking).

    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 latest nano source tarball, then:

        tar -xvf nano-x.y.tar.gz
        cd nano-x.y
        ./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.