Follow-up Comment #5, bug #67363 (group groff): [comment #1 comment #1:] > Utter madness. > > In manual pages, just switch adjustment and hyphenation off globally for > everyone without supporting any way to switch it back on, and be done with > it, then delete all the fragile, overengineered, and likely bug ridden code > in the macro sets related to it. > > I believe that's the only sustainable option. You are obviously in way over > your head and have produced such a massive amount of regressions with the > groff-1.23 release that it has taken me two years to sort it all out. I'm > now almost done; only three regressions remain to be dealt with, and one > (simple) feature improvement where mandoc needs to catch up. And i got these > massive amounts of dysfunctionality even though i switch off whatever > overengineering i can. I have no idea what users may be suffering who > actually try to _use_ any of that overengineered stuff. > > I believe the only chance to get all this into a better shape and make it > less painful and more stable is massively cutting back on the complexity and > the overengineering such that you get a better chance of actually > understanding what you are doing. Piling more and more and more useless > complication on top is not buying you anything but lots of bugs, and dealing > with that is very painful for any downstream system that cares about software > quality and reliability. I don't think it's fair to build more and more > elaborate castles in the sky and let downstreams sort out the consequences > and suffer the resulting havoc.
Here's an alternative, and shorter, way of answering your charges above.
I ran a bunch of _mandoc_(1)'s tests through my _groff_ working copy before
and after the four commits that implement the fix for this bug.
$ history 20
2825 2025-07-28 00:46:48-0500 make -C build -j check
...
2829 2025-07-28 00:48:53-0500 nroff -mandoc -Tascii -P -cbou
~/src/CVS/mandoc/regress/{man,mdoc}/*/*.in >/tmp/67363-1-before.out
2>/tmp/67363-1-before.err
...
2833 2025-07-28 00:50:09-0500 git rebase --continue
2834 2025-07-28 00:50:11-0500 make -C build -j check
...
2836 2025-07-28 00:50:46-0500 nroff -mandoc -Tascii -P -cbou
~/src/CVS/mandoc/regress/{man,mdoc}/*/*.in >/tmp/67363-2-after.out
2>/tmp/67363-2-after.err
...
2838 2025-07-28 00:51:01-0500 cksum /tmp/67363-[12]*.out
2839 2025-07-28 00:51:09-0500 cksum /tmp/67363-[12]*.err
$ cksum /tmp/67363-[12]*.out
1421672357 16953 /tmp/67363-1-before.out
1421672357 16953 /tmp/67363-2-after.out
$ cksum /tmp/67363-[12]*.err
3348792180 109935 /tmp/67363-1-before.err
3348792180 109935 /tmp/67363-2-after.err
If the changes under discussion in this ticket cause regressions, it looks to
me like they're not ones that _mandoc_(1)'s test harness catches.
How this creates work for you, you'll need to explain to me.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67363>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
