GNU nano 1.1.99pre2 release

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@1420 35c25a1d-7b9e-4130-9fde-d3aeb78583b8

ChangeLog

@@ -1,4 +1,4 @@
-CVS Code -
+GNU nano 1.1.99pre2 - 2003.02.03
 - General
 	- Changed some translatable debug messages to use %s 
 	  instead of the function name, and removed gettext from 

NEWS

@@ -1,3 +1,25 @@
+2003.02.03 - GNU nano 1.1.99pre2 "bugs in my pockets, bugs in my
+		shoes" is released.  There are, not suprisingly,
+		only bugfixes in this release as we move toward the
+		stable 1.2.0 release.  Fixes are included for
+		translable string format, subexpression replacement,
+		constant cursor position, invalid search regexes,
+		justify, screen state on SIGHUP and SIGTERM, cutting
+		to end cuts with long lines, many file browser and
+		operating directory bugs, memory and file descriptor
+		leaks, marker code, spell checker, the mouse code
+		with long lines, multiple buffers and non-file
+		open errors, replacement string length, and a 
+		silly but serious history message crash.  There is 
+		also a drastic improvement in CPU utliization for
+		the color regex code.  
+			Depending on the number of bugs found in this
+		release, there may be a 1.1.99pre3 or RC1, or just
+		a 1.2.0 release.  Most of the major bugs seem to have
+		been worked out, so if you are waiting for a good time
+		to test nano before the official 1.2.0 release, this
+		would be the one to use.  Happy bug hunting!
+
 2003.01.17 - GNU nano 1.1.99pre1 "enough already" has been released.
 		This release is, barring bug fixes and documentation
 		updates, what version 1.2.0 has looked like, feature

configure.ac

@@ -19,7 +19,7 @@
 #
 # $Id$
 
-AC_INIT([GNU Nano], [1.1.99pre1-cvs], [nano-devel@gnu.org], [nano])
+AC_INIT([GNU Nano], [1.1.99pre2], [nano-devel@gnu.org], [nano])
 AC_CONFIG_SRCDIR([nano.c])
 AM_INIT_AUTOMAKE
 AM_CONFIG_HEADER([config.h:config.h.in])

faq.html

@@ -77,7 +77,7 @@
 <h2><a name="1.5"></a>1.5. Why the name change from TIP?</h2>
 <blockquote><p>On January 10, 2000, TIP was officially renamed to nano because of a namespace conflict with another program called 'tip'. The original 'tip' program &quot;establishes a full duplex terminal connection to a remote host&quot;, and was included with many older Unix systems (and newer ones like Solaris). The conflict was not noticed at first because there is no 'tip' utility included with most GNU/Linux distributions (where nano was developed).</p></blockquote>
 <h2><a name="1.6"></a>1.6. What is the current version of nano?</h2>
-<blockquote><p>The current version of nano *should* be 1.1.99pre1. Of course you should always check the nano homepage to see what the latest and greatest version is.</p></blockquote>
+<blockquote><p>The current version of nano *should* be 1.1.99pre2. Of course you should always check the nano homepage to see what the latest and greatest version is.</p></blockquote>
 <h2><a name="1.7"></a>1.7. I want to read the man page without having to download the program!</h2>
 <blockquote><p>Jeez, demanding, aren't we? Okay, look <a href="http://www.nano-editor.org/dist/v1.1/nano.1.html">here</a>.</p></blockquote>
 <hr width="100%">

nano.texi

@@ -8,7 +8,7 @@
 @c Run `makeinfo' rather than `texinfo-format-buffer'.
 @smallbook
 @set EDITION 0.1
-@set VERSION 1.1.99pre1
+@set VERSION 1.1.99pre2
 @set UPDATED 17 Jan 2003
 
 @dircategory Editors
@@ -23,7 +23,7 @@
 @titlepage
 @title GNU @code{nano}
 @subtitle a small and friendly text editor.
-@subtitle version 1.1.99pre1
+@subtitle version 1.1.99pre2
 
 @author Chris Allegretta
 @page
@@ -387,7 +387,7 @@ are certain differences between the editors:
 
 @table @code
 @item Search and Replace History
-As of version 1.1.99pre1 of @code{nano}, text entered as search or replace
+As of version 1.1.99pre2 of @code{nano}, text entered as search or replace
 strings will be stored and can be accessed with the up/down
 arrow keys.  Previously, @code{nano} offered a more consistent, but incompatible
 with Pico, method for entering search and replace strings.  In the old
@@ -425,7 +425,7 @@ replace it.  The @code{nano} implementation will stop at each search
 string found and query whether to replace this instance or not.  The 
 internal spell checker operates similarly.  Note that these is no way 
 to force these functions to behave in the Pico fashion.  As of 
-version 1.1.99pre1, misspelled words are sorted and trimmed for 
+version 1.1.99pre2, misspelled words are sorted and trimmed for 
 uniqueness in the internal spell checker such that the words 'apple' 
 and 'Apple' will be prompted for correction separately.  
 @end table