nano

commit 2c19345e58ddc0def4f4cb0e65ea249519cb43f2
parent 69a7dd86ec3052211b33817f78321cf70e8789f4
Author: Benno Schulenberg <bensberg@telfort.nl>
Date:   Sun, 30 Apr 2023 17:24:23 +0200

docs: in a synopsis, use braces around a choice of required parts

This seems to be the convention.  For an example, see `man tar`.

This addresses https://savannah.gnu.org/bugs/?64125.
Reported-by: Eric S. Raymond <esr@thyrsus.com>

Diffstat:
M
doc/nano.1
 | 
2
+-
M
doc/nano.texi
 | 
2
+-

2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/doc/nano.1 b/doc/nano.1
@@ -28,7 +28,7 @@ nano \- Nano's ANOther editor, inspired by Pico
 .B nano
 .RI [ options "] [" file [\fB: line [\fB: column "]]]..."
 .sp
-.BR nano " [" \fIoptions "] [[" + [ crCR ]( / | ? ) \fIstring "] " \fIfile ]...
+.BR nano " [" \fIoptions "] [[" + [ crCR ]{ / | ? } \fIstring "] " \fIfile ]...
 
 .SH DESCRIPTION
 \fBnano\fP is a small and friendly editor.  It copies the look and feel
diff --git a/doc/nano.texi b/doc/nano.texi
@@ -163,7 +163,7 @@ A more complete command synopsis thus is:
 
 @blankline
 @example
-@code{nano [OPTION]@dots{} [[+LINE[,COLUMN]|+[crCR](/|?)STRING] FILE]@dots{}}
+@code{nano [OPTION]@dots{} [[+LINE[,COLUMN]|+[crCR]@{/|?@}STRING] FILE]@dots{}}
 @end example
 @blankline