From: "G. Branden Robinson" <g.branden.robinson@gmail.com>
To: Alejandro Colomar <alx@kernel.org>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: .sp 1 in strerror.3 (and probably more pages)
Date: Sun, 13 Aug 2023 11:20:04 -0500 [thread overview]
Message-ID: <20230813162004.bknsqbfvpewbee7f@illithid> (raw)
In-Reply-To: <60420364-2a68-a6b8-d7ca-7fe6a1384d64@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 1546 bytes --]
Hi Alex,
At 2023-08-13T18:06:15+0200, Alejandro Colomar wrote:
> On 2023-08-13 17:28, G. Branden Robinson wrote:
> > At 2023-08-13T17:19:59+0200, Alejandro Colomar wrote:
> >> While trying to apply a patch that touches some table, I found an
> >> '.sp 1' after a table.
> >>
> >> I tried removing it to see what it does, but it seems nothing
> >> changed.
> >>
> >> However, in the PDF version, there's some change (using .sp 1
> >> produces a larger space before the next section heading).
> >>
> >> Should we keep that thing, should we replace it by something else,
> >> or should we remove it?
> >
> > I would take it out.
>
> Okay. But I'd like to understand why Michael used it. Since we already
> have a blank without it, why would have he added it? Or did 1.22.4 have
> a bug that didn't produce that blank?
>
> Here's what Michael's commit says:
>
> # ".sp 1" ==> ensure a blank line before the next section heading
>
> (c466875ecd64 ("Various pages: Improve formatting in ATTRIBUTES"))
Thanks for the context; it helps.
> Yep, it explains the difference, although it doesn't explain why
> Michael added it.
Since the Linux man-pages "ATTRIBUTES" section uses a boxed table, I'm
betting it was working around Savannah #49390.
https://savannah.gnu.org/bugs/index.php?49390
The overprinting was invisible if there was no text on the line after
the table, but it would _look_ like the omission of the space that
normally precedes a subsequent section heading.
Regards,
Branden
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-13 16:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-13 15:19 .sp 1 in strerror.3 (and probably more pages) Alejandro Colomar
2023-08-13 15:28 ` G. Branden Robinson
2023-08-13 16:06 ` Alejandro Colomar
2023-08-13 16:20 ` G. Branden Robinson [this message]
2023-08-13 20:00 ` Alejandro Colomar
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=20230813162004.bknsqbfvpewbee7f@illithid \
--to=g.branden.robinson@gmail.com \
--cc=alx@kernel.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