ariadne
/
smol
2
1
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

docs: improve the title of the manual, away from the bare "nano" 

Also, suppress two unwanted blank lines in the HTML output, and
use a macro to avoid repeating the same three lines eight times.
master
Benno Schulenberg 2021-10-18 10:40:15 +02:00
parent 46f76ca8b8
commit 1f36d5411a
1 changed files with 20 additions and 22 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

42
doc/nano.texi
View File

@ -2,7 +2,7 @@
@c %**start of header @c %**start of header
@setfilename nano.info @setfilename nano.info
@settitle nano @settitle The GNU nano text editor
@c %**end of header @c %**end of header
@documentencoding UTF-8 @documentencoding UTF-8
@ -64,12 +64,19 @@ For suggesting improvements: @email{nano-devel@@gnu.org}
@end titlepage @end titlepage
@macro blankline
@iftex
@sp 1
@end iftex
@end macro
@ifnottex @ifnottex
@node Top @node Top
@top @top
This manual documents the GNU @command{nano} editor, version 5.9. This manual documents GNU @command{nano}, version 5.9.
@menu @menu
* Introduction:: * Introduction::
@ -109,25 +116,24 @@ If you want the old, Pico behavior back, you can use the
following options: @option{--breaklonglines}, following options: @option{--breaklonglines},
@option{--jumpyscrolling}, and @option{--emptyline} @option{--jumpyscrolling}, and @option{--emptyline}
(or @option{-bje}). (or @option{-bje}).
@sp 1
@blankline
Please report bugs via @url{https://savannah.gnu.org/bugs/?group=nano}. Please report bugs via @url{https://savannah.gnu.org/bugs/?group=nano}.
@sp 1
@blankline
For background information see @url{https://nano-editor.org/}. For background information see @url{https://nano-editor.org/}.
@node Invoking @node Invoking
@chapter Invoking @chapter Invoking
The usual way to invoke @command{nano} is: The usual way to invoke @command{nano} is:
@iftex @blankline
@sp 1
@end iftex
@example @example
@code{nano [FILE]} @code{nano [FILE]}
@end example @end example
@iftex @blankline
@sp 1
@end iftex
But it is also possible to specify one or more options (see the next But it is also possible to specify one or more options (see the next
section), and to edit several files in a row. Additionally, the cursor section), and to edit several files in a row. Additionally, the cursor
@ -144,15 +150,11 @@ of those letters: @code{C} and/or @code{R}. When the string contains spaces,
it needs to be enclosed in quotes. it needs to be enclosed in quotes.
A more complete command synopsis thus is: A more complete command synopsis thus is:
@iftex @blankline
@sp 1
@end iftex
@example @example
@code{nano [OPTION]@dots{} [[+LINE[,COLUMN]|+[crCR](/|?)STRING] FILE]@dots{}} @code{nano [OPTION]@dots{} [[+LINE[,COLUMN]|+[crCR](/|?)STRING] FILE]@dots{}}
@end example @end example
@iftex @blankline
@sp 1
@end iftex
Normally, however, you set your preferred options in a @file{nanorc} Normally, however, you set your preferred options in a @file{nanorc}
file (@pxref{Nanorc Files}). And when using @code{set positionlog} file (@pxref{Nanorc Files}). And when using @code{set positionlog}
@ -1864,9 +1866,7 @@ Or see the list at the end of the main internal help text (@kbd{^G}) instead.
Building @command{nano} from source is fairly straightforward if you are Building @command{nano} from source is fairly straightforward if you are
familiar with compiling programs with autoconf support: familiar with compiling programs with autoconf support:
@iftex @blankline
@sp 1
@end iftex
@example @example
tar xvzf nano-x.y.z.tar.gz tar xvzf nano-x.y.z.tar.gz
cd nano-x.y.z cd nano-x.y.z
@ -1874,9 +1874,7 @@ familiar with compiling programs with autoconf support:
make make
make install make install
@end example @end example
@iftex @blankline
@sp 1
@end iftex
The possible options to @code{./configure} are: The possible options to @code{./configure} are: