minor fixes for the README

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@1618 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
This commit is contained in:
David Lawrence Ramsey 2004-01-10 06:02:05 +00:00
parent 606dfda47a
commit f0b3009400
2 changed files with 23 additions and 15 deletions

View File

@ -1,4 +1,7 @@
CVS code - CVS code -
- README:
- Reformat to 72 characters per line, fix wording in one spot,
and fix spacing in several spots. (DLR)
GNU nano 1.3.1 - 2004.01.09 GNU nano 1.3.1 - 2004.01.09
- General: - General:

35
README
View File

@ -7,18 +7,19 @@ Overview
wonderfully easy-to-use and friendly Pico text editor. wonderfully easy-to-use and friendly Pico text editor.
First and foremost is its license: the Pine suite does not use the First and foremost is its license: the Pine suite does not use the
GPL or a GPL-friendly license, and has unclear restrictions on GPL or a GPL-friendly license, and has unclear restrictions on
redistribution. Because of this, Pine and Pico are not included with redistribution. Because of this, Pine and Pico are not included
many GNU/Linux distributions. Also, other features (like goto line with many GNU/Linux distributions. Also, other features (like goto
number or search and replace) were unavailable until recently or line number or search and replace) were unavailable until recently
require a command line flag. Yuck. or require a command line flag. Yuck.
nano aims to solve these problems by emulating the functionality of nano aims to solve these problems by emulating the functionality of
Pico as closely as possible while addressing the problems above and Pico as closely as possible while addressing the problems above and
perhaps providing other extra functionality. perhaps providing other extra functionality.
The nano editor is now an official GNU package. For more information The nano editor is now an official GNU package. For more
on GNU and the Free Software Foundation please see http://www.gnu.org. information on GNU and the Free Software Foundation please see
http://www.gnu.org.
How to compile and install nano How to compile and install nano
@ -29,7 +30,7 @@ How to compile and install nano
make make
make install make install
It's that simple. Use --prefix with configure to override the It's that simple. Use --prefix with configure to override the
default installation directory of /usr/local. default installation directory of /usr/local.
Web Page Web Page
@ -39,26 +40,30 @@ Web Page
Mailing List and Bug Reports Mailing List and Bug Reports
Savannah hosts all the nano-related mailing-lists. Savannah hosts all the nano-related mailing-lists.
+ info-nano@gnu.org is a very low traffic list + info-nano@gnu.org is a very low traffic list
used to announce new Nano versions or other important information used to announce new Nano versions or other important
about the project. information about the project.
+ help-nano@gnu.org is for those seeking to get help without + help-nano@gnu.org is for those seeking to get help without
wanting to hear about the technical details of its wanting to hear about the technical details of its
development. development.
+ nano-devel@gnu.org is the list used by the people + nano-devel@gnu.org is the list used by the people
that make Nano and a general development discussion list, with that make Nano and a general development discussion list, with
moderate traffic. 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 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. subscribe to.
For general bug reports, send a description of the problem to For general bug reports, send a description of the problem to
nano@nano-editor.org or directly to the development list. nano@nano-editor.org or directly to the development list.
Current Status Current Status
GNU nano has reaching its second major milestone, 1.2.x. Development GNU nano has reached its second major milestone, 1.2.x.
of new features will continue in the 1.3.x branch, while 1.2.x Development of new features will continue in the 1.3.x branch,
versions will be dedicated to bugfixing and polishing. while 1.2.x versions will be dedicated to bugfixing and
polishing.
Chris Allegretta (chrisa@asty.org) Chris Allegretta (chrisa@asty.org)