Manual fixes
git-svn-id: svn://svn.savannah.gnu.org/nano/trunk/nano@532 35c25a1d-7b9e-4130-9fde-d3aeb78583b8master
parent
fb9cffe268
commit
882e145ebb
18
nano.info
18
nano.info
|
@ -294,16 +294,16 @@ Pico Compatibility
|
|||
differences apply to the default mode and Pico Compatibility mode:
|
||||
|
||||
`Displayed Shortcuts'
|
||||
By default, the following shortcuts are displayed by default in the
|
||||
Shortcut Lists:
|
||||
By default, the following shortcuts are displayed in the Shortcut
|
||||
Lists:
|
||||
|
||||
^G ^O ^\ ^Y ^K ^C
|
||||
^X ^R ^W ^V ^U ^T
|
||||
|
||||
Related functions are listed above or below each other by default.
|
||||
The Justify function is not listed, instead the "Replace"
|
||||
function is displayed. The "Read File" and "WriteOut" functions
|
||||
are also aligned for consistency.
|
||||
function is displayed. Also, he "Read File" and "WriteOut"
|
||||
functions are aligned for consistency.
|
||||
|
||||
In Pico Compatibility mode, the default Pico shortcuts are
|
||||
displayed:
|
||||
|
@ -316,8 +316,8 @@ differences apply to the default mode and Pico Compatibility mode:
|
|||
string, file name) will be placed on the statusbar, and is
|
||||
editable. This is done so there is consistency across all
|
||||
functions. For example: even if there is a previous replace
|
||||
string, it can always be deleted if the user wishes to perform an
|
||||
empty string replace at any point.
|
||||
string, it can always be deleted if one wishes to perform an empty
|
||||
string replace.
|
||||
|
||||
In Pico Compatibility Mode, the previously entered text in a
|
||||
search or replace will appear in brackets, and is not editable.
|
||||
|
@ -332,8 +332,8 @@ differences apply to the default mode and Pico Compatibility mode:
|
|||
automatically replace it. The `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 like
|
||||
in the Pico fashion.
|
||||
Note that these is no way to force these functions to behave in
|
||||
the Pico fashion.
|
||||
|
||||
|
||||
File: nano.info, Node: Building and Configure Options, Prev: Pico Compatibility, Up: Top
|
||||
|
@ -391,6 +391,6 @@ Node: Online Help7028
|
|||
Node: Feature Toggles7404
|
||||
Node: The File Browser8550
|
||||
Node: Pico Compatibility9259
|
||||
Node: Building and Configure Options11335
|
||||
Node: Building and Configure Options11301
|
||||
|
||||
End Tag Table
|
||||
|
|
11
nano.texi
11
nano.texi
|
@ -322,15 +322,14 @@ apply to the default mode and Pico Compatibility mode:
|
|||
|
||||
@table @code
|
||||
@item Displayed Shortcuts
|
||||
By default, the following shortcuts are displayed by default in the
|
||||
Shortcut Lists:
|
||||
By default, the following shortcuts are displayed in the Shortcut Lists:
|
||||
|
||||
^G ^O ^\ ^Y ^K ^C@*
|
||||
^X ^R ^W ^V ^U ^T
|
||||
|
||||
Related functions are listed above or below each other by default. The
|
||||
Justify function is not listed, instead the "Replace" function is
|
||||
displayed. The "Read File" and "WriteOut" functions are also aligned for
|
||||
displayed. Also, he "Read File" and "WriteOut" functions are aligned for
|
||||
consistency.
|
||||
|
||||
In Pico Compatibility mode, the default Pico shortcuts are displayed:
|
||||
|
@ -342,8 +341,8 @@ In Pico Compatibility mode, the default Pico shortcuts are displayed:
|
|||
By default, previously entered string for a function (search string,
|
||||
file name) will be placed on the statusbar, and is editable. This is
|
||||
done so there is consistency across all functions. For example: even if
|
||||
there is a previous replace string, it can always be deleted if the user
|
||||
wishes to perform an empty string replace at any point.
|
||||
there is a previous replace string, it can always be deleted if one
|
||||
wishes to perform an empty string replace.
|
||||
|
||||
In Pico Compatibility Mode, the previously entered text in a search or
|
||||
replace will appear in brackets, and is not editable. It is not a
|
||||
|
@ -357,7 +356,7 @@ 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
|
||||
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 like in the Pico fashion.
|
||||
to force these functions to behave in the Pico fashion.
|
||||
@end table
|
||||
|
||||
@node Building and Configure Options, , Pico Compatibility, Top
|
||||
|
|
Loading…
Reference in New Issue