nano

nano with my custom patches
git clone git://bsandro.tech/nano
Log | Files | Refs | README | LICENSE

commit 8c81d23a7e26ef8717e9b56600190aca2121fe44
parent 8d458043d1711171922d2146b9f6f3eb206566d8
Author: Chris Allegretta <chrisa@asty.org>
Date:   Wed, 16 Aug 2000 02:52:44 +0000

Doc updates


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

Diffstat:
MTODO | 1+
Mfaq.html | 4++--
2 files changed, 3 insertions(+), 2 deletions(-)

diff --git a/TODO b/TODO @@ -11,6 +11,7 @@ Current Version: - Rewrite edit_refresh, if at all possible [DONE] - Implement justify function [DONE] - Cut to end of line [DONE] +- Unjustify command (^U after ^J) For Next Version: - Undo/Redo key? diff --git a/faq.html b/faq.html @@ -300,7 +300,7 @@ isn't hard.&nbsp; Unpack the nano source with a command like:</font> <p><b><font color="#330000">tar -zxvf nano-x.y.z.tar.gz</font></b> <p><font color="#330000">If you get error messages about the -z option, try this:</font> -<p><b><font color="#330000">gunzip -d nano-x.y.z.tar.gz | tar xvf -</font></b> +<p><b><font color="#330000">gzip -dc nano-x.y.z.tar.gz | tar xvf -</font></b> <p><font color="#330000">(again, where x.y.z is the version number in question).&nbsp; Then you need to run configure with any options you might want (if any).</font> <p><font color="#330000">The average case is this:</font> @@ -473,7 +473,7 @@ also licensed under the GPL.</font></blockquote> their license?</font></h2> <blockquote><font color="#330000">You're really not asking the right person -here.&nbsp; I (Chris) waited along time to see if UW would change their +here.&nbsp; I (Chris) waited a long time to see if UW would change their license because of the amount of high quality software being released and developed under the GPL without being taken advantage of by malicious corporate entities or other baddies, but no such luck so far.</font></blockquote>