All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man <linux-man@vger.kernel.org>
Subject: Re: .sp 1 in strerror.3 (and probably more pages)
Date: Sun, 13 Aug 2023 22:00:29 +0200	[thread overview]
Message-ID: <7e28216b-fd36-e332-e492-0db9b5ecad0d@kernel.org> (raw)
In-Reply-To: <20230813162004.bknsqbfvpewbee7f@illithid>


[-- Attachment #1.1: Type: text/plain, Size: 1273 bytes --]

Hi Branden,

On 2023-08-13 18:20, G. Branden Robinson wrote:
[...]

>> 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.

I had a terminal where I had nicely prepared a lot of stuff to show you,
but it seems I completely forgot about it.  I had a lot more than that.  :/

> 
>> 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

Yeah, that's what I suspected.  I've killed them now.  The only pages with
call now are the tz ones and bpf-helpers.7 (generated from .rst, itself
generated from kernel headers).

Cheers,
Alex

> 
> 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

-- 
<http://www.alejandro-colomar.es/>
GPG key fingerprint: A9348594CE31283A826FBDD8D57633D441E25BB5


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2023-08-13 20:00 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
2023-08-13 20:00       ` Alejandro Colomar [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=7e28216b-fd36-e332-e492-0db9b5ecad0d@kernel.org \
    --to=alx@kernel.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.