From: Alejandro Colomar <alx.manpages@gmail.com>
To: Ingo Schwarze <schwarze@usta.de>,
"G . Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: All caps .TH page name
Date: Thu, 21 Jul 2022 16:29:21 +0200 [thread overview]
Message-ID: <66c19a09-ef0f-0d85-0380-37a67ac483dd@gmail.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 987 bytes --]
Hi Branden and Ingo!
I've never been convinced about the page title being in all caps in the
.TH line. From recent groff@ discussions, I guess that neither of you
are either.
I'd like to know why this has been the case historically, and any
opinions you might have about me changing the man-pages to use the same
caps as the actual identifier that I'm documenting (most of the time
that would mean lowercase). Basically, the same rules as within .SH NAME.
Also, does it have any functional implications? I'm especially
interested in knowing if that may affect in any way the ability of
man(1) to find a page when invoked as `man TIMESPEC` for example. I'm
not saying necessarily that I'd like to keep that behavior. I wouldn't
mind breaking it, if it means that users will be able to differentiate
upper- and lowercase pages. We're not in Windows (nor MacOS), anyway.
Cheers,
Alex
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2022-07-21 14:29 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-21 14:29 Alejandro Colomar [this message]
2022-07-21 18:36 ` All caps .TH page name 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
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=66c19a09-ef0f-0d85-0380-37a67ac483dd@gmail.com \
--to=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=schwarze@usta.de \
/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;
as well as URLs for NNTP newsgroup(s).