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

tweaks: fiddle with some wordings in the texinfo document 

Also, add two cross references: one in words, and one with a link.
master
Benno Schulenberg 2017-02-12 12:06:44 +01:00
parent 7fac9ec51c
commit fb8fdcaa0a
1 changed files with 9 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/nano.texi
View File

@ -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