[bug #51003] "test-groff" can't find doc-macros in the "tmac/mdoc" directory

[G. Branden Robinson]

Follow-up Comment #7, bug #51003 (project groff):

In groff 1.22.3, a subdirectory of tmac called mdoc is shipped and populated
with the files that are being sourced:


$ dpkg -L groff-base|grep 'tmac.*doc'
/usr/share/groff/1.22.3/tmac/andoc.tmac
/usr/share/groff/1.22.3/tmac/doc-old.tmac
/usr/share/groff/1.22.3/tmac/doc.tmac
/usr/share/groff/1.22.3/tmac/mandoc.tmac
/usr/share/groff/1.22.3/tmac/mdoc
/usr/share/groff/1.22.3/tmac/mdoc/doc-common
/usr/share/groff/1.22.3/tmac/mdoc/doc-ditroff
/usr/share/groff/1.22.3/tmac/mdoc/doc-nroff
/usr/share/groff/1.22.3/tmac/mdoc/doc-syms
/usr/share/groff/1.22.3/tmac/mdoc.tmac


I'll see if we're still doing that.  I'll also play around with
GROFF_TMAC_PATH to see if I can get those .mso requests to complain when they
should be.

I'm not giving up on this yet because I really want to be able to A/B changes
to groff_mdoc (or the macro package itself, for that matter) in built trees
without having to do an install.

Without the patch, that's totally unreasonable.  If you run the commands in my
earlier comments, you get vast quantities of unholy spew.


$ groff -t -M build/tmac -mdoc build/tmac/groff_mdoc.7 2>&1 >/dev/null | head
Usage: .Sh section_name ... (#115)
Usage: .Sh section_name ... (#245)
Usage: .Ss not callable by other macros (#261)
Usage: .Li argument ... (#313)
Usage: .Li argument ... (#316)
Usage: .Li argument ... (#320)
Usage: .Li argument ... (#322)
build/tmac/groff_mdoc.7:325: warning: macro `doc-first-parameter' not defined
(possibly missing space after `do')
build/tmac/groff_mdoc.7:325: warning: macro `doc-get-width' not defined
(possibly missing space after `do')
build/tmac/groff_mdoc.7:325: warning: macro `doc-get-arg-width' not defined
(possibly missing space after `do')

[literally ONE THOUSAND MORE LINES of stderr snipped]

I may end up agreeing with you, but I'm not willing to admit defeat yet. 

    _______________________________________________________

Reply to this item at:

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

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