summaryrefslogtreecommitdiff
path: root/README
diff options
context:
space:
mode:
authorAnas Nashif <anas.nashif@intel.com>2012-11-05 12:55:17 -0800
committerAnas Nashif <anas.nashif@intel.com>2012-11-05 12:55:17 -0800
commit176336f2dedded583aa8d775e6f97ad25a293aa5 (patch)
tree35155f4aedb601ee1f5895b1e5aaa693c12d94df /README
downloadnano-176336f2dedded583aa8d775e6f97ad25a293aa5.tar.gz
nano-176336f2dedded583aa8d775e6f97ad25a293aa5.tar.bz2
nano-176336f2dedded583aa8d775e6f97ad25a293aa5.zip
Imported Upstream version 2.3.1upstream/2.3.1upstream
Diffstat (limited to 'README')
-rw-r--r--README72
1 files changed, 72 insertions, 0 deletions
diff --git a/README b/README
new file mode 100644
index 0000000..abbb892
--- /dev/null
+++ b/README
@@ -0,0 +1,72 @@
+
+ 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 is 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
+ perhaps providing other extra functionality.
+
+ The nano editor is now 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 zxvf 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 configured with the "--enable-nanorc" option, after
+ installation you might copy the doc/nanorc.sample to your home
+ directory, rename it to ".nanorc", and then edit it according to
+ your taste.
+
+Web Page
+
+ http://www.nano-editor.org/
+
+Mailing List and Bug Reports
+
+ Savannah hosts all the nano-related mailing-lists.
+
+ + info-nano@gnu.org is a very low traffic list
+ used to announce new nano versions or other important
+ information 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 nano-<name>-request@gnu.org with a
+ subject of "subscribe", where <name> is the list you want to
+ subscribe to.
+
+ For general bug reports, send a description of the problem to
+ nano@nano-editor.org or directly to the development list.
+
+Current Status
+
+ GNU nano has reached its third stable milestone, 2.0.x.
+ Development of new features continues in the 2.1.x branch, while
+ 2.0.x versions are dedicated to bug-fixing and polishing.
+
+$Id: README 4057 2007-01-29 12:40:48Z dolorous $