Update of bug #68271 (group groff):

                  Status:                    None => Fixed
             Open/Closed:                    Open => Closed

    _______________________________________________________

Follow-up Comment #1:

Hi Vincent,

[comment #0 original submission:]
> After the upgrade of the groff Debian packages from 1.23.0-10 to 1.24.1-1,
> the output with the use of the macro IP can be incorrect. This affects the
> perlfunc(1) man page for 4-letter functions without an argument, such as
> "fork" (this man page uses an indentation of 4 spaces).

This was a conscious change in _groff_ 1.24.0, announced in the "NEWS" file.

https://cgit.git.savannah.gnu.org/cgit/groff.git/tree/NEWS?h=1.24.0#n545


*  The an (man) macro package's `IP` macro no longer honors the formerly
   hard-coded 1n tag separation noted in the previous item.  This means
   that the first argument to the `IP` macro can abut the text of the
   paragraph with no intervening space.  If you use a word instead of
   punctuation or a list enumerator for `IP`'s first argument, consider
   migrating to `TP`.


In general, `IP` should not be used for paragraph marks that have semantic
value.  That's what the `TP` macro is for.
 
If too many packages are affected by the change to fix in a timely way, you
can add the following to your "man.local" file.  On Debian-based system, the
relevant file specification is "/etc/groff/man.local".  Here's an example
diff.


$ diff -u ~/groff-{1.24.1,HEAD}/share/groff/site-tmac/man.local
--- /home/branden/groff-1.24.1/share/groff/site-tmac/man.local  2026-04-23
21:40:05.057962304 -0500
+++ /home/branden/groff-HEAD/share/groff/site-tmac/man.local    2026-04-23
21:54:12.666452538 -0500
@@ -22,6 +22,9 @@
 .\" Set this register to configure which the `MR` macro uses.
 .\" .nr an*MR-URL-format 1
 .\"
+.am1 an*break-paragraph
+.  nr an*enforce-tag-separation 1
+..
 .\" Local Variables:
 .\" mode: nroff
 .\" fill-column: 72


While those are undocumented, internal register and macro names and therefore
not officially supported, I have no plans to change them.

Formerly, there was no documented, portable, and reliable means to achieve
zero spacing between a paragraph's mark and its text.

Resolving as invalid due to the issue being a deliberate, advertised change.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?68271>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to