From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: groff <groff@gnu.org>, linux-man <linux-man@vger.kernel.org>
Subject: Re: Manual page sections shouting
Date: Sat, 7 Jan 2023 01:34:21 +0100 [thread overview]
Message-ID: <7e17cc0f-c6c8-276a-7d2a-efc3af814de2@gmail.com> (raw)
In-Reply-To: <4ab3e3aa-9b05-765a-ba44-06bf39994d81@gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 800 bytes --]
On 1/7/23 01:25, Alejandro Colomar wrote:
> Hi Branden,
>
> I agree with you that I'd prefer that section headings didn't shout at the
> reader. However, I've waited to do such a change, because I'm not sure about
> it. There's a good thing about having them in uppercase: references to them are
> also in uppercase, and that makes it easy to grep for them (I need to do that
> from time to time).
>
> Do you have any opinion on that?
Also, when referring to the section within a page, would you refer in lowercase,
or the first-upper-then-lower? Using uppercase is unambiguous, while using
lowercase might need "section" next to the section name. Maybe it's not so easy
to do the change.
>
> Cheers,
>
> Alex
>
--
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-07 0:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-07 0:25 Manual page sections shouting Alejandro Colomar
2023-01-07 0:34 ` Alejandro Colomar [this message]
2023-01-07 10:17 ` G. Branden Robinson
2023-01-07 12:04 ` Alejandro Colomar
2023-01-10 17:21 ` Lennart Jablonka
2023-01-10 19:08 ` modal man(7) extensions for groff and man-db man(1) (was: Manual page sections shouting) G. Branden Robinson
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=7e17cc0f-c6c8-276a-7d2a-efc3af814de2@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