Go to file
Benno Schulenberg 856322b01e main: interpret only a double slash (//) as quoting, not a single one
Otherwise the first line of a multiline /*...*/-comment would be
seen as quoted and thus *not* as the first line of a paragraph.

In the code, use "/{2}" to prevent the remainder of the line
getting colored as a comment.
2018-06-01 09:21:03 +02:00
doc main: interpret only a double slash (//) as quoting, not a single one 2018-06-01 09:21:03 +02: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 2018-05-15 09:14:23 +02:00
src main: interpret only a double slash (//) as quoting, not a single one 2018-06-01 09:21:03 +02:00
syntax syntax: makefile: color all keywords that GNU make recognizes 2018-05-30 11:29:08 +02:00
.gitignore add support for gnulib 2017-03-06 11:56:02 +01:00
AUTHORS docs: thank Kamil for his bug fixes, and update an email address 2018-05-16 09:57:02 +02:00
autogen.sh gnulib: update to its current upstream state 2018-05-29 11:08:55 +02:00
ChangeLog bump version numbers and add a news item for the 2.9.7 release 2018-05-15 08:48:00 +02: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 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.7 release 2018-05-15 08:48:00 +02: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.7 release 2018-05-15 08:48:00 +02: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: fix the source URL in the spec file 2018-01-29 09:46:47 +01:00
NEWS bump version numbers and add a news item for the 2.9.7 release 2018-05-15 08:48:00 +02:00
README tweaks: indenting text files with tabs is not a good idea 2018-01-09 16:51:16 +01:00
README.GIT tweaks: use for git the more faithful "less -x1,5" suggested by Brand 2017-12-30 16:38:19 +01:00
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

          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.