From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>, groff <groff@gnu.org>
Subject: Re: All caps .TH page title
Date: Fri, 22 Jul 2022 13:46:37 +0200 [thread overview]
Message-ID: <e4603be0-47f4-bc2b-b31e-52039ca63721@gmail.com> (raw)
In-Reply-To: <7a94b352-9ae5-a823-72c4-c526a0cc0e66@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 1816 bytes --]
Hi,
On 7/22/22 12:35, Alejandro Colomar (man-pages) wrote:
> BTW, I think I didn't reply (or if I did was very short) to your comment
> that other languages may find it difficult to mirror our use of
> subsections, since their main section is already a subsection (e.g.,
> 3pl). I'd say that since C is the native Unix language, and others are
> just... others?, I'd optimize for C, and let other languages find a way
> to document their things. It would be easy to say just go away, the man
> pages are for C, but I won't dare to say that, since I like man pages,
> and I'd like to see more documentation for languages that I sometimes
> have to use be in the form of man pages, so I'll try to come up with a
> more imaginative answer: how about using subsubsections of the form
> 3pl_type? At least it's a possibility. man(1) would handle them as any
> other subsection, but that's not a big problem. Maybe man(1) could
> develop a way to provide subsubsections... Colin, any ideas in this
> regard?
Or, maybe it's the time to write a whole new volume? I think there's a
comparable difference between 3type and 3 than between 2 and 3 or 1 and
8, so it would be merited. I didn't do it before for two reasons: it
might break software that assumes than Unix manuals use a single number
followed by an optional string (I'd say it's not a fair assumption to
say that man9 would be the last one ever used; if there's 9, there might
be a 10 some day), and because other projects had already used 3type.
But, that would start a clean namespace. Maybe it's worth it.
How would you feel if I inaugurate man10 for types, and later man11 for
non-function-like macros? :D
Cheers,
Alex
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-07-22 11:46 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 14:29 All caps .TH page name Alejandro Colomar
2022-07-21 18:36 ` G. Branden Robinson
2022-07-21 23:16 ` All caps .TH page title Alejandro Colomar
2022-07-22 0:22 ` Colin Watson
2022-07-22 1:34 ` G. Branden Robinson
2022-07-22 4:07 ` G. Branden Robinson
2022-07-22 14:44 ` Ingo Schwarze
2022-07-22 2:14 ` G. Branden Robinson
2022-07-22 10:35 ` Alejandro Colomar (man-pages)
2022-07-22 11:46 ` Alejandro Colomar [this message]
2022-07-22 19:03 ` G. Branden Robinson
2022-07-22 22:20 ` Alejandro Colomar
2022-07-23 19:29 ` Ingo Schwarze
2022-07-24 11:20 ` Alejandro Colomar (man-pages)
2022-07-24 14:57 ` Ingo Schwarze
2022-07-24 15:44 ` G. Branden Robinson
2022-07-24 17:07 ` FHS and packaging (was: All caps .TH page title) Alejandro Colomar
2022-07-27 16:05 ` All caps .TH page title Ingo Schwarze
2022-07-29 11:33 ` man0, man3head (was: All caps .TH page title) Alejandro Colomar
2022-07-29 12:31 ` Ingo Schwarze
2022-07-29 11:43 ` BSD and GPL " Alejandro Colomar
2022-07-24 16:17 ` man -M tcl " Alejandro Colomar
2022-07-27 15:32 ` Ingo Schwarze
2022-07-29 12:03 ` Alejandro Colomar
2022-07-29 13:22 ` Ingo Schwarze
2022-07-29 13:27 ` Alejandro Colomar
2022-07-22 16:19 ` All caps .TH page name Ingo Schwarze
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=e4603be0-47f4-bc2b-b31e-52039ca63721@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--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