nano, but smaller
 
 
 
 
 
Go to file
Chris Allegretta d55655f23a Reordered --help usage listing by alpha
git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@428 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2000-12-27 03:36:47 +00:00
intl Ick, I left out libintl.h. 2000-11-28 17:04:51 +00:00
po nano 0.9.24 release 2000-12-19 02:59:43 +00:00
.cvsignore Added configure and Makefile.in. Yell at me :) 2000-12-19 23:01:24 +00:00
ABOUT-NLS More RCS schtuff 2000-08-07 02:16:24 +00:00
AUTHORS Added Rocco to AUTHORS 2000-11-21 02:20:42 +00:00
BUGS Give the read file error segfault a bug # in BUGS 2000-12-18 20:18:37 +00:00
COPYING Initial revision 2000-06-06 05:53:49 +00:00
ChangeLog Reordered --help usage listing by alpha 2000-12-27 03:36:47 +00:00
INSTALL More RCS schtuff 2000-08-07 02:16:24 +00:00
Makefile.am Added Id to Makefile.am 2000-08-08 16:59:04 +00:00
Makefile.in New libm test for slang 2000-08-08 01:49:55 +00:00
NEWS Update docs for .24 release 2000-12-19 02:51:06 +00:00
README Changing addresses again 2000-09-27 03:16:11 +00:00
TODO Add request for backup saves. 2000-12-20 01:06:39 +00:00
acconfig.h Added --disable-help, moved hold pointer declaration 2000-12-10 17:03:25 +00:00
aclocal.m4 Initial revision 2000-06-06 05:53:49 +00:00
config.h.in Added --disable-help, moved hold pointer declaration 2000-12-10 17:03:25 +00:00
configure Back to CVS version 2000-12-19 03:01:00 +00:00
configure.in Back to CVS version 2000-12-19 03:01:00 +00:00
cut.c Added --disable-help, moved hold pointer declaration 2000-12-10 17:03:25 +00:00
faq.html Corrected some typos and small errors. 2000-12-19 22:58:00 +00:00
files.c Fix segfault when read_file encounters an error opening the file 2000-12-18 01:09:07 +00:00
global.c Fix lots of compiler warnings 2000-12-18 07:05:27 +00:00
install-sh Initial revision 2000-06-06 05:53:49 +00:00
missing Initial revision 2000-06-06 05:53:49 +00:00
mkinstalldirs Initial revision 2000-06-06 05:53:49 +00:00
move.c removed update_line call in do_up, fix for marker set update? 2000-11-23 01:19:58 +00:00
nano.1 Added -b, -e and -f compatibility flags, updated man pages, added Alt-Alt-x functionality 2000-12-18 02:23:50 +00:00
nano.1.html Added -b, -e and -f compatibility flags, updated man pages, added Alt-Alt-x functionality 2000-12-18 02:23:50 +00:00
nano.c Reordered --help usage listing by alpha 2000-12-27 03:36:47 +00:00
nano.h Took out help from spell_list and changed SPELL_LIST_LEN to 1 2000-11-29 23:57:20 +00:00
proto.h Fix lots of compiler warnings 2000-12-18 07:05:27 +00:00
search.c Rocco fixes 2000-12-05 11:36:41 +00:00
stamp-h.in Initial revision 2000-06-06 05:53:49 +00:00
utils.c uncutting at filebot magic line fix and new_magicline totsize increment 2000-12-10 05:54:27 +00:00
winio.c Fix help menu keypad issues 2000-12-18 05:03:16 +00:00

README

	The nano editor (Nano's ANOther editor) by Chris Allegretta
                                      
Manifesto

     Nano is the editor formerly known as TIP (TIP Isn't Pico).
     The nano project was started because of three main problems with the
     wonderfully easy-to-use and friendly Pico text editor:
     
     - It's license is not the GNU GPL, and hence some Linux
     distributions, including Debian (my favorite) don't always
     include it/don't include binaries.  This is not necessarily a
     problem, but an issue nonetheless.
     
     - Until recently, it had no ability to go to a line # from within
     the editor. There was the +number command line option, but who wants
     to exit a file to go to a specific line number? When I want to go to
     a line, since I have to exit anyway, I just call up vi temporarily.
     
     - No search and replace feature. Well, apparently there is a flag
     that lets you do a search and replace (-b in newer versions) but,
     well, I still dont like it.
     
     nano aims to solve these problems by emulating the functionality of
     Pico as closely as possible while adressing the problems above and
     perhaps providing other extra functionality.
     
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 to override the default installation
     directory of /usr/local.
     
Web Page

	http://www.nano-editor.org
     
Mailing List and Bug Reports

	SourceForge hosts all the nano-related mailing-lists.
	+ nano-announce@lists.sourceforge.net is a very low traffic list
	  used to announce new Nano versions or other important information
	  about the project.
	+ nano-devel@lists.sourceforge.net 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@lists.sourceforge.net
	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

     nano is currently at version 0.9.x, and it will probably remain there
     for awhile. This reflects the adage that the last 10% of a project
     takes 90% of the time. Version 1.0 will be released when there are
     no unresolved bugs, and not before. I am also currently looking for
     patches for all things listed in the TODO file. If you have a
     comment or suggestion, please let me know, all help is appreciated.

     Warning:  This program can and possibly will corrupt your data in
     its current form!  It is beta software, so treat it as such!  
     Thank you.
     
     Note that the primary aim of nano is to emulate Pico while adding a
     few key "missing" features. I do NOT want just a GPL'ed Pico clone,
     nor do I want something that strays too far from the Pico design
     (simple and straightforward). If you don't like this, feel free to
     fork my code at any time, but please call your editor something
     else, believe it or not I struggled awhile before coming up with
     the name nano (and before that TIP), and it would be much easier for
     everyone if there weren't five versions of the same program. As you
     can guess, I'm not much of an emacs fan ;)
     
   Chris Allegretta (chrisa@asty.org)

$Id$