Commit 9fa5fbd3 authored by Chris Allegretta's avatar Chris Allegretta
Browse files

nano.texi - Updates for the most recent and not so recent changes

git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@1346 35c25a1d-7b9e-4130-9fde-d3aeb78583b8
No related merge requests found
Showing with 45 additions and 48 deletions
+45 -48
...@@ -210,6 +210,7 @@ Changes ...@@ -210,6 +210,7 @@ Changes
with HTML 4.01 Transitional. (DLR and David Benbennick) with HTML 4.01 Transitional. (DLR and David Benbennick)
- nano.texi: - nano.texi:
- Typo fixes and updates. (David Benbennick) - Typo fixes and updates. (David Benbennick)
- Updates for the most recent and not so recent changes.
- TODO - TODO
- Added some wishlist stuff. - Added some wishlist stuff.
- THANKS: - THANKS:
......
...@@ -94,11 +94,9 @@ internationalization support, and filename tab completion. ...@@ -94,11 +94,9 @@ internationalization support, and filename tab completion.
@code{nano} +LINE [GNU long option] [option] [ @var{file ...} ] @code{nano} +LINE [GNU long option] [option] [ @var{file ...} ]
The original goal for @code{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. emulation of Pico, but nano's main goal is to be as compatible as
There is a flag to implement (nearly) complete Pico emulation, (option -p possible while offering a superset of Pico's functionality.
or GNU long option @code{--pico}). This can also be toggled from within Also see @xref{Pico Compatibility}, for other differences.
@code{nano} by typing Meta-P. @xref{Pico Compatibility}, for more
info.
Email bug reports to @email{nano@@nano-editor.org}. Email bug reports to @email{nano@@nano-editor.org}.
...@@ -186,9 +184,9 @@ running under the X window system). ...@@ -186,9 +184,9 @@ running under the X window system).
Set operating directory. Makes @code{nano} set up something similar to a Set operating directory. Makes @code{nano} set up something similar to a
chroot. chroot.
@item -p, --pico @item -p, --preserve
Emulate Pico as closely as possible, sacrificing consistency for correct Preserve the ^Q (XON) and ^S (XOFF) sequences so data being sent to the editor
emulation. @xref{Pico Compatibility}, for more info. can be can be stopped and started.
@item -r [#cols], --fill=[#cols]. @item -r [#cols], --fill=[#cols].
Wrap lines at column #cols. By default this is the width of the screen, Wrap lines at column #cols. By default this is the width of the screen,
...@@ -304,9 +302,7 @@ the statusbar. ...@@ -304,9 +302,7 @@ the statusbar.
@section Shortcut Lists @section Shortcut Lists
The Shortcut Lists are the two lines at the bottom of the screen which The Shortcut Lists are the two lines at the bottom of the screen which
show some of the more commonly used functions in the editor. The exact show some of the more commonly used functions in the editor.
functions which are displayed depend on whether Pico Compatibility
mode is enabled. @xref{Pico Compatibility}, for more info.
@node Online Help, Feature Toggles, Editor Basics, Top @node Online Help, Feature Toggles, Editor Basics, Top
@chapter Online Help @chapter Online Help
...@@ -349,8 +345,7 @@ toggles the -m (@code{--mouse}) command line flag. ...@@ -349,8 +345,7 @@ toggles the -m (@code{--mouse}) command line flag.
toggles the -M (@code{--mac}) command line flag. toggles the -M (@code{--mac}) command line flag.
@item Pico Mode Toggle (Meta-P) @item Pico Mode Toggle (Meta-P)
toggles the -p (@code{--pico}) command line flag. toggles the -p (@code{--preserve}) command line flag.
@xref{Pico Compatibility}, for more info.
@item Smooth Scrolling Toggle (Meta-S) @item Smooth Scrolling Toggle (Meta-S)
toggles the -S (@code{--smooth}) command line flag. toggles the -S (@code{--smooth}) command line flag.
...@@ -390,42 +385,40 @@ statusbar and the file browser is exited. ...@@ -390,42 +385,40 @@ statusbar and the file browser is exited.
@node Pico Compatibility, Building and Configure Options, The File Browser, Top @node Pico Compatibility, Building and Configure Options, The File Browser, Top
@chapter Pico Compatibility @chapter Pico Compatibility
nano does not completely emulate Pico by default. The following @code{nano} attempts to emulate Pico as closely as possible, but there
differences apply to the default mode and Pico Compatibility mode: are certain differences between the editors:
@table @code @table @code
@item Displayed Shortcuts @item Search and Replace History
By default, the following shortcuts are displayed in the Shortcut List: As of version 1.1.99pre1 of @code{nano}, text entered as search or replace
strings will be stored and can be accessed with the up/down
@multitable @columnfractions .1 .1 .1 .1 .1 .1 arrow keys. Previously, @code{nano} offered a more consistent, but incompatible
@item ^G @tab ^O @tab ^\ @tab ^Y @tab ^K @tab ^C with Pico, method for entering search and replace strings. In the old
@item ^X @tab ^R @tab ^W @tab ^V @tab ^U @tab ^T method, previous entries would be displayed by default as editable text
@end multitable in front of the cursor, as opposed to being bracketed and uneditable as
it is in Pico. The old behavior could be made compatible with Pico via the
Related functions are listed above or below each other by default. The @code{-p} flag, but recent versions of Pico use the @code{-p} flag
Justify function is not listed, instead the ``Replace'' function is to preserve the XON and XOFF sequences within the editor. Since with the new
displayed. Also, the ``Read File'' and ``WriteOut'' functions are aligned method search and replace strings can still be edited by simply hitting the
for consistency. up arrow key once, the old method was removed completely.
In Pico Compatibility mode, the default Pico shortcuts are displayed:
@item Writing or Appending Selected Text to Files
@multitable @columnfractions .1 .1 .1 .1 .1 .1 Text selected using the Control-Caret (^^) key can be written out or
@item ^G @tab ^O @tab ^R @tab ^Y @tab ^K @tab ^C appended to a new or existing file using the Writeout key (^O).
@item ^X @tab ^J @tab ^W @tab ^V @tab ^U @tab ^T
@end multitable @item Toggles
Many options which alter the functionality of the program can be
@item Previous String Text "toggled" on or off using Meta key sequences, meaning the program does
By default, the previously entered string for a function (search string, not have to be restarted to turn a particular feature of the editor
file name) will be placed on the statusbar, and is editable. This is on or off. Please see the internal help function (^G) for a list of
done so there is consistency across all functions. For example: even if what functions can be toggled for a particular version of
there is a previous replace string, it can always be deleted if one @code{nano}.
wishes to perform an empty string replace.
@item Cursor Position Display
In Pico Compatibility Mode, the previously entered text in a search or The output of the "Display Cursor Position" in @code{nano} displays
replace will appear in brackets, and is not editable. It is not a the given column position, as well as the row and total character
simple matter to do an empty string replace when a previous replace position of the cursor.
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 @item Interactive Replace and Spell Checker
It is worth noting that the @code{nano} replace function is interactive, It is worth noting that the @code{nano} replace function is interactive,
...@@ -433,7 +426,10 @@ i.e. it does not stop after one search string is found and automatically ...@@ -433,7 +426,10 @@ i.e. it does not stop after one search string is found and automatically
replace it. The @code{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 string found and query whether to replace this instance or not. The
internal spell checker operates similarly. Note that these is no way internal spell checker operates similarly. Note that these is no way
to force these functions to behave in the Pico fashion. to force these functions to behave in the Pico fashion. As of
version 1.1.99pre1, 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 @end table
@node Building and Configure Options, , Pico Compatibility, Top @node Building and Configure Options, , Pico Compatibility, Top
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment