[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #66103] manpage-10n project: issues in man pages
From: |
G. Branden Robinson |
Subject: |
[bug #66103] manpage-10n project: issues in man pages |
Date: |
Wed, 11 Sep 2024 04:40:46 -0400 (EDT) |
Follow-up Comment #3, bug #66103 (group groff):
Looks like Savane got angry with me.
Here's what I *tried* to reply with via email:
Subject: Re: [bug #66103] manpage-10n project: issues in man pages
[self-follow-up]
I had a wordo here.
At 2024-09-11T04:33:41-0400, G. Branden Robinson wrote:
> Yes. These are all deliberate. The idea is to have the synopsis
> synopsize, and to keep it in parallel with the command's usage message,
> which does describe each option in detail.
...does _NOT_ describe each option in detail.
Some commands do employ long usage messages, for those I would recommend
a similar practice as groff(1): give people self-documenting argument
names in the synopsis, since some users require only an aide-mémoire,
and terser ones when presenting the semantics of an option.
> {savane: user = 108747; tracker = bugs; item = 66103}
Regards,
Branden
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66103>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
- [bug #66103] manpage-10n project: issues in man pages, G. Branden Robinson, 2024/09/11
- Message not available
- Message not available
- Message not available
- [bug #66103] manpage-10n project: issues in man pages,
G. Branden Robinson <=
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available
- Message not available