nano, but smaller
 
 
 
 
 
Go to file
Chris Allegretta 44e73dfc96 Show two lines from previous page in help file when paging down
git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@211 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
2000-09-07 03:37:38 +00:00
intl Initial revision 2000-06-06 05:53:49 +00:00
po Show two lines from previous page in help file when paging down 2000-09-07 03:37:38 +00:00
ABOUT-NLS More RCS schtuff 2000-08-07 02:16:24 +00:00
AUTHORS More RCS schtuff 2000-08-07 02:16:24 +00:00
BUGS Assigned entire file cut a number, crediting Ken in BUGS instead of ChangeLog 2000-09-05 13:15:44 +00:00
COPYING Initial revision 2000-06-06 05:53:49 +00:00
ChangeLog Use raw mode if _POSIX_VDISABLE isn't available, to allow support under cygwin 2000-09-06 15:19:18 +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 off by one in toggle help code and set up for 0.9.17 release 2000-09-04 16:21:29 +00:00
README More RCS schtuff 2000-08-07 02:16:24 +00:00
TODO Doc updates 2000-08-16 02:52:44 +00:00
acconfig.h More RCS schtuff 2000-08-07 02:16:24 +00:00
aclocal.m4 Initial revision 2000-06-06 05:53:49 +00:00
config.h.in Changed _POSIX_VERSION checks in regex code to HAVE_REGEX_H, added check for regex.h in configure.in 2000-09-06 13:39:17 +00:00
configure Changed _POSIX_VERSION checks in regex code to HAVE_REGEX_H, added check for regex.h in configure.in 2000-09-06 13:39:17 +00:00
configure.in Changed _POSIX_VERSION checks in regex code to HAVE_REGEX_H, added check for regex.h in configure.in 2000-09-06 13:39:17 +00:00
cut.c Fix to cut.c for cutting entire file with marker 2000-09-05 13:09:56 +00:00
faq.html Changed version and files to CVS 2000-09-04 17:44:59 +00:00
files.c Testing RCS headers 2000-08-06 21:13:45 +00:00
global.c Changed _POSIX_VERSION checks in regex code to HAVE_REGEX_H, added check for regex.h in configure.in 2000-09-06 13:39:17 +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 Testing RCS headers 2000-08-06 21:13:45 +00:00
nano.1 Updated man pages for universal -T option 2000-08-04 02:05:44 +00:00
nano.1.html Updated man pages for universal -T option 2000-08-04 02:05:44 +00:00
nano.c Use raw mode if _POSIX_VDISABLE isn't available, to allow support under cygwin 2000-09-06 15:19:18 +00:00
nano.h Type in nano.h 2000-09-06 14:08:37 +00:00
proto.h Changed _POSIX_VERSION checks in regex code to HAVE_REGEX_H, added check for regex.h in configure.in 2000-09-06 13:39:17 +00:00
search.c Changed _POSIX_VERSION checks in regex code to HAVE_REGEX_H, added check for regex.h in configure.in 2000-09-06 13:39:17 +00:00
stamp-h.in Initial revision 2000-06-06 05:53:49 +00:00
utils.c Changed _POSIX_VERSION checks in regex code to HAVE_REGEX_H, added check for regex.h in configure.in 2000-09-06 13:39:17 +00:00
winio.c Show two lines from previous page in help file when paging down 2000-09-07 03:37:38 +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.asty.org/nano
     
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@asty.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$