From: Chris Allegretta Date: Thu, 15 Feb 2001 00:25:17 +0000 (+0000) Subject: Use code instead of command in man page *shrug*. Add GNUish stuff X-Git-Tag: v0.9.99pre3~14 X-Git-Url: https://git.wh0rd.org/?a=commitdiff_plain;h=35ac99d0d4e98587188f302d9e4351fe3af8f8e1;p=nano.git Use code instead of command in man page *shrug*. Add GNUish stuff git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@535 35c25a1d-7b9e-4130-9fde-d3aeb78583b8 --- diff --git a/faq.html b/faq.html index 99911e3f..ab305d7c 100644 --- a/faq.html +++ b/faq.html @@ -1,6 +1,6 @@ -The nano editor FAQ +The GNU nano editor FAQ @@ -17,7 +17,7 @@
1.1 About this FAQ.
1.2. How do I contribute to it? -
1.3. What is nano? +
1.3. What is GNU nano?
1.4. What is the history behind nano?
1.5. Why the name change from @@ -28,7 +28,8 @@ of nano? without having to download the program!

-2. Where to get nano

+2. Where to get GNU +nano
2.1. FTP and WWW sites that carry nano. @@ -134,12 +135,13 @@ href="mailto:nano@nano-editor.org">nano@nano-editor.org and if it is useful enough it will be included in future versions.

-1.3. What is nano?

+1.3. What is GNU nano? -
Nano is designed to be a free replacement -for the Pico text editor, part of the PINE email suite from The -University of Washington.  It aims to "emulate Pico as closely -as possible and perhaps include extra functionality.
+
GNU Nano is designed to be a free +replacement for the Pico text editor, part of the PINE email suite from The University of +Washington.  It aims to "emulate Pico as closely as possible and +perhaps include extra functionality.

1.4. What is the history behind @@ -176,7 +178,11 @@ and hacked like a madman for many hours straight one weekend to make a The program could not be invoked without a filename, could not save files, had no help menu, spell checker, and so forth.  But over time it improved, and with the help of a few great coders it matured to the almost stable -state it is today. +state it is today. +

In February 2001, nano has been declared an +official GNU program by Richard Stallman. Nano is also nearing its 1.0 +release as of this writing (Valentine's Day 2001). +

1.5. Why the name change from TIP?

@@ -206,7 +212,7 @@ Okay, look here.

-2. Where to get nano

+2. Where to get GNU nano

2.1. FTP and WWW sites that carry diff --git a/nano.info b/nano.info index c26fe967..4be75c58 100644 --- a/nano.info +++ b/nano.info @@ -3,7 +3,7 @@ This is nano.info, produced by makeinfo version 4.0 from nano.texi.  File: nano.info, Node: Top, Next: Introduction, Prev: (dir), Up: (dir) - This manual documents nano, a small and friendly text editor. + This manual documents GNU nano, a small and friendly text editor. * Menu: @@ -21,7 +21,7 @@ File: nano.info, Node: Introduction, Next: Editor Basics, Prev: Top, Up: Top Introduction ************ - `nano' is a small and friendly text editor. Besides basic text + GNU `nano' is a small and friendly text editor. Besides basic text editing, `nano' offers many extra features like an interactive search and replace, goto line number, auto-indentation, feature toggles, internationalization support, and filename tab completion. @@ -377,20 +377,20 @@ consider the following command line options:  Tag Table: Node: Top69 -Node: Introduction373 -Node: Overview795 -Node: Command Line Options1375 -Ref: Expert Mode3098 -Node: Editor Basics3940 -Node: Entering Text4165 -Node: Special Functions4505 -Node: The Titlebar5359 -Node: The Statusbar6056 -Node: Shortcut Lists6636 -Node: Online Help7028 -Node: Feature Toggles7404 -Node: The File Browser8550 -Node: Pico Compatibility9259 -Node: Building and Configure Options11301 +Node: Introduction377 +Node: Overview803 +Node: Command Line Options1383 +Ref: Expert Mode3106 +Node: Editor Basics3948 +Node: Entering Text4173 +Node: Special Functions4513 +Node: The Titlebar5367 +Node: The Statusbar6064 +Node: Shortcut Lists6644 +Node: Online Help7036 +Node: Feature Toggles7412 +Node: The File Browser8558 +Node: Pico Compatibility9267 +Node: Building and Configure Options11309  End Tag Table diff --git a/nano.texi b/nano.texi index 67f44f9e..a9815c6d 100644 --- a/nano.texi +++ b/nano.texi @@ -17,16 +17,17 @@ @c end tex @titlepage -@title @command{nano} +@title GNU @code{nano} @subtitle a small and friendly text editor. @subtitle version 0.9.99pre2 @author Chris Allegretta @page -This manual documents @command{nano}, a small and friendly text editor. +This manual documents GNU @code{nano}, a small and friendly text +editor. -This manual is part of the @command{nano} distribution.@* +This manual is part of the GNU @code{nano} distribution.@* @sp4 Copyright (C) 1999, 2000, 2001 Chris Allegretta. @@ -57,7 +58,7 @@ e-mail: @email{chrisa@@asty.org}@* @node Top, Introduction, (dir), (dir) -This manual documents nano, a small and friendly text editor. +This manual documents GNU nano, a small and friendly text editor. @menu * Introduction:: @@ -72,8 +73,8 @@ This manual documents nano, a small and friendly text editor. @node Introduction, Editor Basics, Top, Top @chapter Introduction -@command{nano} is a small and friendly text editor. Besides basic -text editing, @command{nano} offers many extra features like an +GNU @code{nano} is a small and friendly text editor. Besides basic +text editing, @code{nano} offers many extra features like an interactive search and replace, goto line number, auto-indentation, feature toggles, internationalization support, and filename tab completion. @@ -86,13 +87,13 @@ completion. @node Overview, Command Line Options, Introduction, Introduction @section Overview -@command{nano} [GNU long option] [option] +LINE [ @var{ file ...} ] +@code{nano} [GNU long option] [option] +LINE [ @var{ file ...} ] -The original goal for @command{nano} was a complete bug-for-bug compatible +The original goal for @code{nano} was a complete bug-for-bug compatible emulation of Pico, but consistency is now a slightly higher priority. There is a flag to implement (nearly) complete Pico emulation, (option -p or GNU long option --pico). This can also be toggled from within -@command{nano} by typing Meta-P. @xref{Pico Compatibility}, for more +@code{nano} by typing Meta-P. @xref{Pico Compatibility}, for more info. Email bug reports to @email{nano@@nano-editor.org}. @@ -100,7 +101,7 @@ Email bug reports to @email{nano@@nano-editor.org}. @node Command Line Options, , Overview, Introduction @section Command Line Options -@command{nano} takes the following options from the command line: +@code{nano} takes the following options from the command line: @table @code @item -T [num, --tabsize=[num] @@ -143,13 +144,13 @@ Wrap lines at column #cols. By default this is the width of the screen, less eight. @item -s [prog], --speller=[prog] -Invoke [prog] as the spell checker. By default, @command{nano} uses its -own interactive spell checker that requires the @command{spell} program be +Invoke [prog] as the spell checker. By default, @code{nano} uses its +own interactive spell checker that requires the @code{spell} program be installed on your system. @item -t, --tempfile Do not ask whether or not to save the current contents of the file when -exiting, assume yes. This is most useful when using @command{nano} as the +exiting, assume yes. This is most useful when using @code{nano} as the composer of a mailer program. @anchor{Expert Mode} @@ -171,7 +172,7 @@ Do not wrap long lines at any length. This option overrides any value for -r. @item -z, --suspend -Enable suspend ability of @command{nano} using the system's suspend +Enable suspend ability of @code{nano} using the system's suspend keystroke (usually ^Z). @item +LINE @@ -191,8 +192,8 @@ Start at line number LINE instead of the default of line 1. @node Entering Text, Special Functions, Editor Basics, Editor Basics @section Entering Text -All key sequences in @command{nano} are entered using the keyboard. -@command{nano} is a "modeless" editor, all keys with the exception of +All key sequences in @code{nano} are entered using the keyboard. +@code{nano} is a "modeless" editor, all keys with the exception of Control and Meta key sequences will enter text into the file being edited. @@ -222,7 +223,7 @@ Escape key to generate Meta key sequences. The titlebar is the line displayed at the top of the editor. There are three sections: left, center and right. The section on the left displays -the version of @command{nano} being used. The center section displays the +the version of @code{nano} being used. The center section displays the current file name, or "New Buffer" if the file has not yet been named. The section on the right will display "Modified" if the file has been modified since it ws last saved or opened. @@ -254,7 +255,7 @@ is enabled. @xref{Pico Compatibility}, for more info. @node Online Help, Feature Toggles, Editor Basics, Top @chapter Online Help -The online help system in @command{nano} is available by pressing ^G. +The online help system in @code{nano} is available by pressing ^G. It is fairly self explanatory, documenting the various parts of the editor and available keystrokes. Navigation is via the ^Y (Page Up) and ^V (Page Down) keys. ^X exits the help system. @@ -351,9 +352,9 @@ string exists, for example. When writing a file, the previous filename will be displayed in the editable text portion of the editor. @item Interactive Replace and Spell Checker -It is worth noting that the @command{nano} replace function is interactive, +It is worth noting that the @code{nano} replace function is interactive, i.e. it does not stop after one search string is found and automatically -replace it. The @command{nano} implementation will stop at each search +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.