Hi Branden, On 12/28/25 23:36, G. Branden Robinson wrote:
Hi Bernhard,At 2025-12-28T23:26:11+0100, Bernhard Voelker wrote:This triggers a 'make check' error: env GROFF=groff ../build-aux/man-lint.sh . find.1 check_manpages_format_without_error_messages ( find.1): OK check_manpages_with_groff_checkstyle_2 ( find.1): FAILED an.tmac:./find.1:23: style: use of deprecated macro: .HP make[3]: *** [Makefile:3112: findutils-check-manpages] Error 1 Should we replace .HP by a simple .P? Or better just remove it?I would leave it and ignore the error, unless you want to adopt the groff man(7) SY/YS extension macros. The synopsis won't look as good or traditional if you use an ordinary paragraphing macro (P, LP, PP) there.
'make check' now calls build-aux/man-lint.sh which in turn calls
${GROFF} -t -z -ww -rCHECKSTYLE=2 -man ...
Therefore, it's a bit hard to just ignore the deprecation warning
for .HP.
Well, until now we didn't have the groff check, and I could skip the
whole man-lint logic by setting GROFF=true.
I've un-deprecated the `HP` macro for the forthcoming groff 1.24.0 release. commit d483834af930eeec2cc9f77441af5d581fe18c50 Author: G. Branden Robinson <[email protected]> Date: Tue Jul 30 22:02:58 2024 -0500 tmac/an.tmac: Silence `HP` deprecation warning. * tmac/an.tmac (HP): The `mS` extension register has changed its meaning (commit f680c55d38, 13 June) such that it is no longer a reliable indicator of whether the deprecation warning for this macro should be suppressed, so stop suppressing a deprecation warning based on its value. In fact, stop issuing the deprecation warning altogether. (See <https://lists.gnu.org/archive/html/bug-ncurses/2024-04/ msg00027.html>.)Likewise here:[...]an.tmac:./locate.1:18: style: use of deprecated macro: .HP
hmm, it will take a while until the new version hits the developer systems. Therefore, I'd prefer an easy replacement ... like ".TP"? You see I'm not very much into such formatting details, and therefore would rather keep it simple. Personally, I'd rather like to avoid redundant documentation in both the man pages and the Texinfo files of findutils in long-term. Other GNU packages generate the man pages from --help output via help2man. But also changing to that pattern would be quite some effort, a) to re-organize the Texinfo manual better before b) merging the information from the man page which might not yet be included on Texinfo side, and c) pimp the usage functions to produce better output. Sigh. Have a nice day, Berny
