nano, but smaller
 
 
 
 
 
Go to file
Benno Schulenberg d2d0c665b1 display: force the cursor to reappear after a message (when using Slang)
For some reason, when running a tiny nano built with Slang on the bterm
of a Debian installer image, the cursor disappears when certain things
are written to the status bar.  Make the cursor reappear by rewriting
the two help lines with dummy items (and then rewriting it again with
the normal menu in the central loop).  Of course, this does not help
when the user uses -x or --nohelp to suppress the help lines, but at
least in the default setup the cursor doesn't get hidden now and then.

This mitigates https://savannah.gnu.org/bugs/?59091.

Bug existed since before version 2.2.4.
2020-09-10 18:46:48 +02:00
doc docs: add the customary (1) after the name of command-line programs 2020-09-05 19:43:51 +02:00
m4 tweaks: delete another pointless ChangeLog 2020-03-26 13:17:41 +01:00
po build: abort the update script if a PO file contains a control character 2020-09-09 16:38:39 +02:00
src display: force the cursor to reappear after a message (when using Slang) 2020-09-10 18:46:48 +02:00
syntax syntax: po: highlight embedded control codes that shouldn't be there 2020-09-08 19:38:55 +02:00
.gitignore tweaks: drop obsolete 'nano.spec' from .gitignore file, and reshuffle 2020-06-15 19:11:45 +02:00
AUTHORS docs: note Marco as the original author of the bookmarking code 2020-04-16 11:05:14 +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
ChangeLog bump version numbers and add a news item for the 5.2 release 2020-08-24 09:53:07 +02: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
IMPROVEMENTS bump version numbers and add a news item for the 5.1 release 2020-08-12 07:57:31 +02:00
Makefile.am build: stop distributing the README.GIT file 2020-08-24 09:29:05 +02:00
NEWS bump version numbers and add a news item for the 5.2 release 2020-08-24 09:53:07 +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
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
autogen.sh gnulib: back away from a commit that causes trouble when using clang 2020-08-23 10:52:20 +02:00
configure.ac build: to verify wide curses, probe for a function that cannot be a macro 2020-09-03 19:47:09 +02:00
nano-regress 2014-05-29 Chris Allegretta <chrisa@asty.org> 2014-05-29 18:30:23 +00:00
roll-a-release.sh bump version numbers and add a news item for the 5.2 release 2020-08-24 09:53:07 +02: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) 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.