public inbox for linux-man@vger.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@vger.kernel.org
Subject: Re: [PATCH v2 2/2] man.7: ffix
Date: Sat, 29 Jul 2023 15:20:53 +0200	[thread overview]
Message-ID: <329a3df7-de63-9ea9-2061-3423c6384482@kernel.org> (raw)
In-Reply-To: <64c4d17f.050a0220.3a505.03ec@mx.google.com>


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

Hi Branden,

On 2023-07-28 19:28, G. Branden Robinson wrote:
> v2: Use heading markup that doesn't confuse Git.

This is part of the commit message.  Since it's just context for
comparing to v1, it's better to have it outside of the commit message.
You could place it after the ---.

> 
> The `\c` escape sequence works in an argument to a macro call that is
> part of a paragraph tag with font style alternation macros, but not the
> ordinary font macros `B` and `I`.  This is because `TP`, `B`, and `I`
> all set up input traps; the six font style alternation macros do not.
> 
> The old formatting would, for some versions of some formatters, set the
> "[trailer]" text as part of the paragraph body, not the tag--like this.
> 
>        .UE    [trailer] Terminate the link text  of  the  preceding  .UR
>               macro,  with  the  optional trailer (if present, usually a
> (and so on)
> 
> This was a poorly understood--and undocumented--interaction of man(7)
> features until recently.  Gory details involving nroff on Unix Version 7
> (1979) running on a simulated PDP-11/45 are available.[1]
> 
> Here is a comparison of the former and new markup.
> 
> before
> ======
> groff 1.22.3: BAD
> groff 1.22.4: GOOD
> groff 1.23.0: BAD
> mandoc 1.14.6: BAD
> 
> now
> ===
> groff 1.22.3: BAD
> groff 1.22.4: GOOD
> groff 1.23.0: GOOD
> mandoc 1.14.6: GOOD
> 
> [1] https://savannah.gnu.org/bugs/?51468
>     https://lists.gnu.org/archive/html/groff/2022-06/msg00020.html
> 
> Signed-off-by: G. Branden Robinson <g.branden.robinson@gmail.com>

Patch applied.  Thanks!

> ---

Here you can write things that shouldn't go in the commit message.
Usually, comparison to vX.

Cheers,
Alex

>  man7/man.7 | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/man7/man.7 b/man7/man.7
> index 258ce25da..583fe354f 100644
> --- a/man7/man.7
> +++ b/man7/man.7
> @@ -249,7 +249,7 @@ .SS Hypertext link macros
>  .B .UE
>  macro as the link text.
>  .TP
> -.B .UE \c
> +.BR .UE \~\c
>  .RI [ trailer ]
>  Terminate the link text of the preceding
>  .B .UR

-- 
<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-07-29 13:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-28 17:28 [PATCH v2 2/2] man.7: ffix G. Branden Robinson
2023-07-29 13:20 ` 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=329a3df7-de63-9ea9-2061-3423c6384482@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox