At 2025-09-20T23:27:34+0200, Gioele Barabucci wrote: > From: Matthias Klose <[email protected]> [not a man page] > +See the bash manual page bash(1) for the handling of parameters (i.e. > +missing parameters). > +
A comma should follow this Latin abbreviation; better still, use English
words instead of Latin abbreviations.
I also think it is redundant to say "bash manual page bash(1)".
And I'd recast a bit.
+See bash(1) regarding parameter handling (as when they are missing).
+
> +.PP
> +See the description of the \fItest\fP builtin command (section SHELL
> +BUILTIN COMMANDS below) for the handling of parameters (i.e.
> +missing parameters).
Once again I'd use man(7) macros instead of roff(7) escape sequences.
Italics appear to be the wrong style choice for this page; the one
employment of the word "test" I can find as a literal uses bold.
---snip---
For example, to use the
.B test
binary found using
.SM
.B PATH
instead of the shell builtin version, run
.QN "enable \-n test" .
---end snip---
Chet sets his (sub)section cross references in full caps and small bold.
---snip---
(see
.SM
.B "SHELL GRAMMAR"
.ie \n(zZ=1 in \fIbash\fP(1)),
.el above),
---end snip---
Further lightly recasting, I'd say...
+.PP
+See the description of the
+.B test
+builtin command in
+.SM
+.B "SHELL BUILTIN COMMANDS"
+below
+regarding parameter handling
+(as when they are missing).
> +See the description of the @code{test} builtin command (section
> +@pxref{Bash Builtins} below) for the handling of parameters
> +(i.e. missing parameters).
> +
...and parallelize this language with the foregoing.
Regards,
Branden
signature.asc
Description: PGP signature
