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 <linux-man@vger.kernel.org>
Subject: Re: Rationale for .PD 0 in old commit
Date: Fri, 13 Nov 2020 08:17:48 +0100 [thread overview]
Message-ID: <cb2b9421-fd39-cb5b-8af4-2ef1c197698a@gmail.com> (raw)
In-Reply-To: <7b38be67-711a-fd8e-539a-bf946b3ee87f@gmail.com>
Hi ALex,
On 11/12/20 11:30 PM, Alejandro Colomar (man-pages) wrote:
>
>
> On 11/12/20 11:26 PM, Alejandro Colomar (man-pages) wrote:
>> Hello Michael,
>>
>> I'd like to know, if you happen to remember it,
>> the rationale for using [.PD 0] + [.RS] + [.TP 24]
>> in perf_event_open.2.
>>
>> It was added in commit 2b538c3e5380cbe81a5c053cd183788e3a13f0cb.
>>
>> I guess it's related to the fact that
>> there are too many levels of indentation,
>> but is it really needed?
>> I think everything fits correctly in an 80-column terminal
>> without needing that workaround.
>>
>> Is it maybe for other than terminals?
>>
>> May I remove those in my attempt to simplify and standardize the markup?
>>
>> Thanks,
>>
>> Alex
>>
>
>
> Ahhhh, It removes some unwanted blank lines, doesn't it?
Yes.
Thanks,
Michael
--
Michael Kerrisk
Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/
Linux/UNIX System Programming Training: http://man7.org/training/
prev parent reply other threads:[~2020-11-13 7:18 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-12 22:26 Rationale for .PD 0 in old commit Alejandro Colomar (man-pages)
2020-11-12 22:30 ` Alejandro Colomar (man-pages)
2020-11-13 7:17 ` Michael Kerrisk (man-pages) [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=cb2b9421-fd39-cb5b-8af4-2ef1c197698a@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=alx.manpages@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