From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: Douglas McIlroy <douglas.mcilroy@dartmouth.edu>,
linux-man@vger.kernel.org
Subject: Re: syntax of options in man1
Date: Thu, 16 Jul 2026 10:55:44 -0500 [thread overview]
Message-ID: <20260716155544.o7fx7ecnpjj5sdai@illithid> (raw)
In-Reply-To: <aljtsrJVLTN6qlxP@devuan>
[-- Attachment #1: Type: text/plain, Size: 1472 bytes --]
Hi Alex,
At 2026-07-16T16:45:16+0200, Alejandro Colomar wrote:
> On 2026-07-16T09:46:25-0400, Douglas McIlroy wrote:
> > Here's a typical option heading (from tail(1))
> > * -n, --lines=[+]NUM*
> >
> > It is tempting to assume (incorrectly) that the short alternative is
> > -n=4. As far as I can tell, the convention that "=" is part of only
> > the long alternative is described nowhere.
>
> Agree. I've had that concern for a long time.
That's why I recommend a somewhat different presentation format.
Illustration:
$ cat ATTIC/tail.man
.TH tail 1 2026-07-16 "groff test suite"
.SH Name
tail \- a porcine corkscrew
.SH Description
Print the last 10 lines of each
.I file
to standard output.
.SH Options
.TP
.BR \-\-lines= [ + ]\c
.IR num
.TQ
.BR \-n\~ [ + ]\c
.IR num
Print the last
.I num
lines instead.
.
Prefixing
.I num
with
.RB \[lq] + \[rq]
prints all lines from
.I num
forward.
Rendering:
$ nroff -rLL=72n -P -c -man ATTIC/tail.man
tail(1) General Commands Manual tail(1)
Name
tail - a porcine corkscrew
Description
Print the last 10 lines of each file to standard output.
Options
--lines=[+]num
-n [+]num
Print the last num lines instead. Prefixing num with “+”
prints all lines from num forward.
groff test suite 2026‐07‐16 tail(1)
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2026-07-16 15:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAKH6PiXDGL658h1t_bstW0Z+MjjJfcNmcde-DA3QNOYKc0TTGg@mail.gmail.com>
2026-07-16 14:45 ` syntax of options in man1 Alejandro Colomar
2026-07-16 15:55 ` G. Branden Robinson [this message]
2026-07-16 16:20 ` Alejandro Colomar
2026-07-16 17:05 ` G. Branden Robinson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260716155544.o7fx7ecnpjj5sdai@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.org \
--cc=douglas.mcilroy@dartmouth.edu \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox