From: Ingo Schwarze <schwarze@usta.de>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Alejandro Colomar <alx.manpages@gmail.com>,
linux-man <linux-man@vger.kernel.org>
Subject: Re: All caps .TH page name
Date: Fri, 22 Jul 2022 18:19:44 +0200 [thread overview]
Message-ID: <YtrOIMPXksaGs0lu@asta-kit.de> (raw)
In-Reply-To: <20220721183620.hdvgwwef66hmrgln@illithid>
Hi Branden,
G. Branden Robinson wrote on Thu, Jul 21, 2022 at 01:36:20PM -0500:
> I would take a jaundiced view toward any software project
> that distinguished its man page names, whether internally or from
> others' solely by a difference in lettercase.
Inside one project, causing such clashes is certainly a bad idea.
But just as same-case clashes sometimes happen accidentally -
consider this on OpenBSD with the "mono" package installed -
$ man mdoc | sed -n 4p
mdoc - semantic markup language for formatting manual pages
$ man 1 mdoc | sed -n 4p
mdoc - Mono documentation management tool
different-case clashes also happen occasionally:
$ man -T ascii err | sed -n '4p;5p'
err, verr, errc, verrc, errx, verrx, warn, vwarn, warnc,
vwarnc, warnx, vwarnx - formatted error messages
$ man -T ascii ERR | sed -n '4p'
ERR - OpenSSL error codes
$ man -T ascii sha256 | sed -n '4p;5p'
md5, sha1, sha256, sha512 - calculate a message digest (checksum)
for a file
$ man -T ascii SHA256 | sed -n '4p;5p;6p;7p'
SHA1, SHA1_Init, SHA1_Update, SHA1_Final, SHA224, SHA224_Init,
SHA224_Update, SHA224_Final, SHA256, SHA256_Init, SHA256_Update,
SHA256_Final, SHA384, SHA384_Init, SHA384_Update, SHA384_Final,
SHA512, SHA512_Init, SHA512_Update, SHA512_Final - Secure Hash
Algorithm
Admittedly, these clashes are extremely rare, so it's not a big issue
either way, at least not for practical purposes.
Yours,
Ingo
prev parent reply other threads:[~2022-07-22 16:19 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
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 ` Ingo Schwarze [this message]
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=YtrOIMPXksaGs0lu@asta-kit.de \
--to=schwarze@usta.de \
--cc=alx.manpages@gmail.com \
--cc=g.branden.robinson@gmail.com \
--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