Go to file
Benno Schulenberg a19a7820f9 color: recompile the file-probing regexes a little faster with REG_NOSUB
When the filename, header-line, and magic regexes are first compiled
while reading in the rc files (to check their validity), REG_NOSUB is
used, but for some reason this wasn't done when each of these regexes
gets recompiled in order to be used.  Fix this oversight.  It shaves
some twenty percent off of each of these regexes' compiling time.
2021-01-21 12:35:16 +01:00
doc docs: correct the word order for Alt+D in the cheat sheet -- it changed 2021-01-20 19:25:29 +01:00
m4
po po: update translations and regenerate POT file and PO files 2021-01-14 11:21:21 +01:00
src color: recompile the file-probing regexes a little faster with REG_NOSUB 2021-01-21 12:35:16 +01:00
syntax
.gitignore
AUTHORS
autogen.sh gnulib: update to its current upstream state 2021-01-07 15:20:45 +01:00
ChangeLog bump version numbers and add a news item for the 5.5 release 2021-01-14 11:08:05 +01:00
ChangeLog.1999-2006
ChangeLog.2007-2015
configure.ac bump version numbers and add a news item for the 5.5 release 2021-01-14 11:08:05 +01:00
COPYING
COPYING.DOC
IMPROVEMENTS bump version numbers and add a news item for the 5.5 release 2021-01-14 11:08:05 +01:00
Makefile.am
nano-regress
NEWS bump version numbers and add a news item for the 5.5 release 2021-01-14 11:08:05 +01:00
README
README.GIT
roll-a-release.sh bump version numbers and add a news item for the 5.5 release 2021-01-14 11:08:05 +01:00
THANKS
TODO

          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, and then:

        tar -xvf nano-x.y.tar.gz
        cd nano-x.y
        ./configure
        make
        make install

    You will need the header files of ncurses installed for ./configure
    to succeed -- get them from libncurses-dev (Debian) or ncurses-devel
    (Fedora) or a similarly named package.  Use --prefix with ./configure
    to override the default installation directory of /usr/local.

    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.

    The archives of the development and help mailing lists are here:

        https://lists.gnu.org/archive/html/nano-devel/
        https://lists.gnu.org/archive/html/help-nano/

Bug Reports

    If you find a bug, please file a detailed description of the problem
    on nano's bug tracker: https://savannah.gnu.org/bugs/?group=nano.

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.