Follow-up Comment #14, bug #63581 (project groff):
[comment #13 comment #13:]
> You're right about the manpage. I doubt many read it. Still,
> it should include mentioning the nroff "sort of incompatibility".
Right, I wasn't trying to suggest the manpage _not_ include this, merely that
it shouldn't be the only place.
> As to sticking a .tm into om.tmac, it won't help in the case of
> the OP's terminal freeze, but it is the best solution.
Yeah, the only ways to help the terminal freeze are (1) having mom reject
nroff as an output format entirely (which you point out is too extreme, even
if terminals are beyond mom's design parameters), or (2) someone volunteering
to root-cause the infinite loop and submit a patch.
But as long as the package emits the warning as part of its startup, then even
if the terminal freezes later, there will at least be that message visible
giving some hint why it might have happened. (I presume mom's code path is
making it past initialization, since the freeze is document-specific.) This
circumvents the problem cited in comment #8, that the user thought the bug was
in his own code and spent some time trying to debug that.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?63581>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
