groff
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2] tzfile.5: Fix indentation


From: G. Branden Robinson
Subject: Re: [PATCH v2] tzfile.5: Fix indentation
Date: Sun, 17 Mar 2024 14:24:29 -0500

[looping in groff mailing list to pitch a terminological reform]

Hi Alex,

At 2024-03-17T19:56:10+0100, Alejandro Colomar wrote:
> You already gained the first two spaces from the previous RS, in which
> you're nested.  Remember that we have
> 
>  .RS "\w'  'u"
>  .IP \(bu "\w'\(bu  'u"
> 
> a few lines above.  The second RS, by default, does the same as the
> previous IP, that is, "\w'\(bu  'u".

I see that I need to clarify the groff_man(7) page in this department.
In fact, I suspect Doug McIlroy's term "prevailing indent" was
tailor-made for expressing this behavior.  But I want to amend it, in
documentation and the "an.tmac" source file, to "prevailing _inset_",
because "indentation" is overloaded to also refer to the additional
spacing applied to (at least some) lines of an `IP`, `TP`, or
(deprecated) `HP` paragraph.

The resulting concept is simple.

prevailing inset = base paragraph inset + sum of relative insets

Equivalently:

prevailing inset = value of `BP` register[1] + amounts in `RS` calls[2]

Regards,
Branden

[1] forthcoming in groff 1.24

[2] for each active inset, if specified; if not, the indentation of the
    previous paragraph in the (sub)section is used, and if none (as with
    `P` and its synonyms), then the value of the `IN` register

I _think_ I've got that right.

Attachment: signature.asc
Description: PGP signature


reply via email to

[Prev in Thread] Current Thread [Next in Thread]