All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: linux-man@vger.kernel.org
Subject: Re: [RFC] Various pages: srcfix. Replace .PD 0 with .TQ.
Date: Sat, 21 May 2022 18:36:23 +0200	[thread overview]
Message-ID: <da6caa45-590a-ed28-905d-741d8e8b27e5@gmail.com> (raw)
In-Reply-To: <20220521152824.knp272wwl7qzpjmg@illithid>

Hi Branden,

On 5/21/22 17:28, G. Branden Robinson wrote:
> I am uncertain about this change.  I like the idea of getting rid of
> `PD` calls, but I think there in value in having `TQ` possess semantics
> of "here is another tag that is related to the previous one after a TP
> call".

Agree.  I prefer to keep the meaning of TQ as a continuation of TP.

> You are (ab)using TQ here to avoid inter-paragraph space.  As I noted in
> a message of a few minutes ago on the groff mailing list[1], it might be
> better to wait for what settles out of a discussion of the `BL` /`EL`
> macro pair I have (not yet formally) proposed for a post-1.23.0 groff
> man(7) extension.

I tend to agree with the necessity for a list macro, and I never liked 
lists written as

.TP
item1
.TQ
item2
.TQ
item3

Because that looks like an abuse of tagged paragraph macros, where they 
completely lost their original meaning (there aren't even paragraphs in 
that list!).  And yet we have that code in the Linux man-pages.

I like your idea of BL/EL[1].  Will wait for your release :)

Regards,

Alex


[1]: <https://git.savannah.gnu.org/cgit/groff.git/tree/man/groff.7.man#n225>

-- 
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/

      reply	other threads:[~2022-05-21 16:36 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-05-21 15:00 [RFC] Various pages: srcfix. Replace .PD 0 with .TQ Alejandro Colomar
2022-05-21 15:28 ` G. Branden Robinson
2022-05-21 16:36   ` 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=da6caa45-590a-ed28-905d-741d8e8b27e5@gmail.com \
    --to=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 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.