From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Helge Kreutzmann <debian@helgefjell.de>,
mario.blaettermann@gmail.com, linux-man@vger.kernel.org
Subject: Re: Issue in man page namespaces.7
Date: Sun, 22 Jan 2023 22:11:06 +0100 [thread overview]
Message-ID: <9a08e09f-6ecd-3e53-6d5f-613fdd720a7d@gmail.com> (raw)
In-Reply-To: <20230122210207.w25k5br5idyna3c2@illithid>
[-- Attachment #1.1: Type: text/plain, Size: 1296 bytes --]
Hi Branden,
On 1/22/23 22:02, G. Branden Robinson wrote:
> I would use \fP instead of \fR, this way you return to the "previous"
Ahh, yes, thanks for catching that! Sleeping 3 hours is definitely not good for
the brain :P
> font, not the roman style in the current family. This is important in
> (sub)section headings because they are normally set in boldface, so
> switching to roman explicitly would unintentionally put "directory" on a
> diet (i.e., cause it to lose [stroke] weight).
>
> With that correction, I'm +1.
>
> But I would also quote multi-word arguments to _any_ man(7) macro.
Why is it? I remember you mentioned that, but what's the win?
>
> Thus:
>
>> +.SS "The \fI/proc/sys/user\fP directory"
>
> Equivalently, if one doesn't care about portability to ancient
> formatters...
>
>> +.SS "The \f[I]/proc/sys/user\f[] directory"
Interesting. I'll consider that for the long term. However, for now I'll keep
\fP style.
>
> ...will suffice.
>
> (One might reasonably wonder why "\fI" doesn't cause a loss of stroke
> weight, too. In groff 1.22.4 and earlier, it does. In groff 1.23.0,
> the man(7) package remaps the "I" to "BI".)
>
> Regards,
> Branden
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-22 21:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-22 19:31 Issue in man page namespaces.7 Helge Kreutzmann
2023-01-22 20:17 ` Alejandro Colomar
2023-01-22 21:02 ` G. Branden Robinson
2023-01-22 21:11 ` Alejandro Colomar [this message]
2023-01-23 8:45 ` G. Branden Robinson
2023-01-24 16:08 ` Alex Colomar
-- strict thread matches above, loose matches on Subject: below --
2022-12-04 9:07 Helge Kreutzmann
2022-03-13 12:34 Helge Kreutzmann
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=9a08e09f-6ecd-3e53-6d5f-613fdd720a7d@gmail.com \
--to=alx.manpages@gmail.com \
--cc=debian@helgefjell.de \
--cc=g.branden.robinson@gmail.com \
--cc=linux-man@vger.kernel.org \
--cc=mario.blaettermann@gmail.com \
/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