@dmnks commented on this pull request.


> +Put distinct operational modes to their own subsections.
+
+Typographic conventions:
+- Use bold for literal values such as command name and options:
+*cmd* does X, with option *--do-this* does Y instead
+- Use underline uppercase to denote user arguments: _ARGUMENT_
+- Use underline for literal file names: _hello-1.0-1.noarch.rpm_
+- Put an empty line before a new section/option/etc
+- Put text immediately below a section/option/etc (ie without an empty line)
+- Put optional elements into [] brackets
+- Put one-of-many choices into <val1|val2|val3> lists
+- Do not emphasize separators like ",", "=", "[]", "|"
+
+When in doubt, consult *man-pages*(7).
+
+# OPTIONS

Ack. In that case, I wonder if this should be made clear in the template. The 
thing is, it's a *template* alright, so it's meant to contain the skeleton for 
writing an actual man page but then, it does contain placeholder content too, 
obviously, and that's sometimes not that obvious :sweat_smile: But I guess 
let's just leave it like this.

-- 
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/3639#discussion_r1984740155
You are receiving this because you are subscribed to this thread.

Message ID: <rpm-software-management/rpm/pull/3639/review/2666719...@github.com>
_______________________________________________
Rpm-maint mailing list
Rpm-maint@lists.rpm.org
https://lists.rpm.org/mailman/listinfo/rpm-maint

Reply via email to