-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Justification regression with groff 1.23.0 (?) #23
Comments
Yeah, I noticed this too and it does seem to be related to |
This is because of the addition of:
to the BTW, I believe the intent of this AD macro is that you can set |
Ah, thanks for the investigation! I've now set MANROFFOPT in my environment to get a uniform style, although it would indeed be best if what pod2man generates could be formatted as before. :) |
Branden agreed that this is a regression and a fix has been committed to the groff repository for the next release. We're currently discussing what, if anything, Pod::Man should do in the meantime, which depends on release schedules, etc. I'd also kind of like to support the I'm trying to talk Branden into making the default ragged right under nroff for all man pages. That's a big change since groff has always defaulted to full justification, but older UNIX nroff did default to ragged right. Discussion is in the thread starting at https://lists.gnu.org/archive/html/groff/2024-03/msg00078.html |
Hi!
I recently noticed that in Debian unstable, manual pages generated from pod, are no longer left aligned everywhere. They are at the beginning, but for example once there are options the justification gets set to both. I think this is a regression in combination with groff 1.23.0, but I've not tested the current stuff from Debian unstable with an older groff (only verifyied that bookworm behaves as expected), nor know whether this is a problem in groff (some kind of regression) or in podlators (some misuse or wrong assumption for some macro perhaps).
Just wanted to file this to not forget.
The text was updated successfully, but these errors were encountered: