Follow-up Comment #6, bug #61089 (project groff):
[comment #4 comment #4:] > [comment #3 comment #3:] > > There are reasons to believe it isn't the culprit though: > > I'd add (3) the newly introduced code path emits a warning, so we can tell if the code is following commit bcdf2f4c <http://git.savannah.gnu.org/cgit/groff.git/commit/?id=bcdf2f4c>'s path by whether the new warning occurs. And even with all warnings enabled, t/6.2-string-slugs.roff trips no new warnings in 1.23.0.rc1. > > (Running this code with all warnings on is still instructive, though, as it hints at syntax errors in ono.tmac, which emits several "unbalanced .el request" warnings.) I feel both vindicated and self-pwn3d. A git bisect reveals that the problematic commit is exactly the one I singled out. I will try to figure out WTF. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?61089> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
