Update of bug #51003 (project groff):

                  Status:                    None => Need Info              
             Assigned to:                    None => gbranden               

    _______________________________________________________

Follow-up Comment #5:

I think actually Bjarni was right here.  Scrubbing those pointless mdoc/
prefixes from the arguments to the .mso calls makes it straightforward to just
run groff (even a system groff) on the built groff_mdoc.7 with the macros from
the build.

This works for out-of-tree builds:


groff -t -M build/tmac -mdoc build/tmac/groff_mdoc.7 2>&1 >/dev/null


And in-tree ones:


groff -t -M tmac -mdoc tmac/groff_mdoc.7 2>&1 >/dev/null


This happens to fix the test-groff case with no extra effort.


./build/test-groff -t -mdoc ./build/tmac/groff_mdoc.7 2>&1 > /dev/null # out
of tree
./test-groff -t -mdoc ./tmac/groff_mdoc.7 2>&1 > /dev/null # in tree


Now, the question that really animates me is why .mso wasn't screaming to
stderr when it couldn't find mdoc/whatever.  It's supposed to; I was just
hacking on input.cpp:macro_source() the other day.  But that's a separate
bug.

Proposed fix attached.  Ingo, please comment if you have a moment.


(file #45421)
    _______________________________________________________

Additional Item Attachment:

File name: 51003.diff                     Size:0 KB


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?51003>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/


_______________________________________________
bug-groff mailing list
bug-groff@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-groff

Reply via email to