"G. Branden Robinson" <[email protected]> writes: > At 2026-06-19T03:07:34+0200, Guillem Jover wrote:
>> Hmm, this seems unrelated though? Or I don't understand the relation >> between CW/CR and .IP? (Just in case, I tried to call pod2man with >> --fixed=CR but that did not seem to fix this problem?) > There are multiple changes queued up in pod2man. Yes, the font name > selection issue is separate from the indentation applied to paragraphs > populated with the `IP` man(7) macro. I have not made any changes in podlators in Git related to the .IP macro. This is the first that I've heard of this backwards-incompatible change in groff. > The change in `IP` handling is known in _groff_ upstream, and documented > in the groff 1.24.0 release notes. > NEWS: > * 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`. What was the motivation for making this change? Nothing about the handling of .IP has changed in podlators since 2001 and I don't remember encountering this problem before. It seems strictly worse than the previous behavior? > If by "upstream" you meant pod2man, it's worth exploring whether that > tool is generating `TP` macros for things like definition lists, or > `IP`. `TP` is a better choice and it is going to become increasingly > important given changes expected in groff 1.25 and planned for the > future. I suppose I can do this if I have to, but to say that I'm annoyed at being asked to change something that was working fine because groff decided to break existing manual pages is putting it mildly. -- Russ Allbery ([email protected]) <https://www.eyrie.org/~eagle/>
