"G. Branden Robinson" <invalid.nore...@gnu.org> writes:

[...]
> Support for email-transported replies to Savannah tickets is a
> relatively new feature, a year or two old.  Dave Kemper and I seem to
> have done some service as its guinea pigs.

> I understand if you don't want to bother with these requirements.

Ah, okay, I will be lazy for now, although I will probably regret it
later when I want to respond to something else and I'm still not properly
set up. :)

> Anywhere after the `TH` call and before the first line break in body
> text that would occur in the rendered document.

Okay, I have removed ".if n .ds AD l" from the document preamble and now
have, immediately after the .TH macro:

.\" For nroff, turn off justification. Always turn off hyphenation. String
.\" and register settings are required by groff 1.23.0 and later.
.if n .ds AD l
.if n .ad l
.nr HY 0
.nh

Some of my test infrastructure wanted the .nh command to be last, and this
was easier than adjusting it. I have confirmed this continues to work as
expected with groff 1.23.0.

If you would like to test with the output of the new podlators to be (not
that this is expected or should be necessary, I hope), you can do
something like the following:

    git clone https://git.eyrie.org/git/perl/podlators.git
    cd podlators
    perl Makefile.PL
    make
    perl -I blib/lib blib/script/pod2man scripts/pod2man > pod2man.1

to generate an *roff document for testing. The last argument can be
replaced with any other file name containing POD source.

I hope to make a new release in the next few days.

> On the gripping hand, decades of perlpod-generated man pages in the
> field have presumptively forced some robustness into _makewhatis_(8) and
> _mandb_(8) implementations.

I have been including a few commands and a comment immediately after .TH
for a while, so hopefully the addition of a couple more commands won't
make any difference.

-- 
Russ Allbery (ea...@eyrie.org)             <https://www.eyrie.org/~eagle/>

Reply via email to