commit fb8fdcaa0a866f41d4f76242625d4aac34c33277
parent 7fac9ec51cd1c3ef634fe04f71a78dbe596fbdd7
Author: Benno Schulenberg <bensberg@justemail.net>
Date: Sun, 12 Feb 2017 12:06:44 +0100
tweaks: fiddle with some wordings in the texinfo document
Also, add two cross references: one in words, and one with a link.
Diffstat:
1 file changed, 9 insertions(+), 11 deletions(-)
diff --git a/doc/nano.texi b/doc/nano.texi
@@ -97,26 +97,24 @@ The usual way to invoke @code{nano} is:
@code{nano [FILE]}
@end quotation
-But it is also possible to specify one or more options, and to edit
-several files in a row. Additionally, the cursor can be put on a
-specific line of a file by adding the line number
+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
+can be put on a specific line of a file by adding the line number
with a plus sign before the filename, and even in a specific column by
-adding it with a comma.
-
-Also, if the first file specified is a dash, @code{nano} will read
-data from standard input.
-
-So a more complete command synopsis is:
+adding it with a comma. So a more complete command synopsis is:
@quotation
@code{nano [OPTION]@dots{} [[+LINE[,COLUMN]|+,COLUMN] FILE]@dots{}}
@end quotation
-But normally you would set your preferred options in your
-@file{.nanorc} file. And when the @code{positionlog} option is set
+Normally, however, you set your preferred options in a @file{.nanorc}
+file (see @xref{Nanorc Files}). And when using @code{set positionlog}
(making @code{nano} remember the cursor position when you close a file),
you will rarely need to specify a line number.
+As a special case: when the first file specified is a dash, @code{nano}
+will read data from standard input. Which means you can pipe the output
+of a command straight into a buffer.
@node Command-line Options
@chapter Command-line Options
