From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org,
g.branden.robinson@gmail.com
Subject: Re: [RFC] memusage.1, uri.7, user-keyring.7, user-session-keyring.7, ld.so.8, tzselect.8: srcfix: Replace \f markup by .
Date: Mon, 16 Nov 2020 11:36:21 +0100 [thread overview]
Message-ID: <ecb73c46-ba70-5f9f-7a68-960fdb1f902b@gmail.com> (raw)
In-Reply-To: <ace3f6d0-3c8b-1fb2-443c-628b421d9e36@gmail.com>
Hi ALex,
On 11/16/20 1:33 AM, Alejandro Colomar (man-pages) wrote:
> Hi Michael,
>
> On 11/15/20 9:54 PM, Michael Kerrisk (man-pages) wrote:
[...]
> So, except for zic.8, zdump.8, and bpf-helpers.7,
> what do you think about the current usage of \f?
>
> I've seen a lot of appearances (many thousands),
> and many of them should probably be fixed.
>
> I think a script to fix them might be a bit difficult,
> but a small C program might be easier to write.
My preference is to avoid \f in favor of .I/.B/etc where possible,
since I find the latter form is often easier to read in the source.
But, as you note, that's not easy in some cases. Every now and then,
when I'm edit some part of a page that uses \f, I'll switch over
to .I/.B/etc.
But, I would prefer not to have a global edit, since:
* Nothing is really broken.
* It's a lot of churn.
* There's the possibility of errors in the change.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
next prev parent reply other threads:[~2020-11-16 11:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-15 16:52 [RFC] memusage.1, uri.7, user-keyring.7, user-session-keyring.7, ld.so.8, tzselect.8: srcfix: Replace \f markup by Alejandro Colomar
2020-11-15 20:54 ` Michael Kerrisk (man-pages)
2020-11-16 0:33 ` Alejandro Colomar (man-pages)
2020-11-16 10:36 ` Michael Kerrisk (man-pages) [this message]
2020-11-16 8:26 ` Michael Kerrisk (man-pages)
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=ecb73c46-ba70-5f9f-7a68-960fdb1f902b@gmail.com \
--to=mtk.manpages@gmail.com \
--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