On 3/20/22 15:23, G. Branden Robinson wrote: > Hi, Alex! > > At 2022-03-18T02:17:53+0100, Alejandro Colomar wrote: >> etc/groff/tmac/deadly.tmac is a file written by Branden, to make >> make groff(1) abort when it finds a style problem, which then >> causes make(1) to also abort. > > Oh, I'm glad to hear this worked out. I had on my to-do list a reply to > you at one point when it wasn't working for some reason. > >> Branden, I'm curious to learn how/if you're using it in your own >> Makefile in groff(1). > > Nothing sophisticated. :) > > I use it only in doc/doc.am, in the targets that generate compiled text > and PDF versions of all of the groff man pages[1]. These will be new > documents shipping in groff 1.23. Oh, now I remember... I'll soon attempt to satisfy your desire of having PDF Linux man-pages. That, and linting C programs within man pages will be my next 2 things to do. And I also want to add a 'dist'[1] make(1) target (and also a 'dist-deb' one, for which I'll require your old Debian skills :p). Expect a lot of additions to the Makefile. Regarding PDF pages, can you please share some advice? Can I build it incrementally as for example a .ar file made out of .o files, where you can build .o files as always with make(1), and then you just replace the necessary .o files in the archive? Is there something similar in the PDF world? Please tell me everything you can think of, since it will be the first time I build a multi-page PDF. [1]: <https://www.gnu.org/software/make/manual/html_node/Standard-Targets.html> > > I set the register `CHECKSTYLE` to "3" on the command line and > format the pages with "groff -mandoc". Any warnings come out on > standard error. I've recently seen some email in the groff@ list using -rCHECKSTYLE=5. Is that a thing? Should I use -rCHECKSTYLE=666 as a "give me everything" mode? > >> BTW, don't feel pressured by my premature usage of your unreleased >> feature to consider not changing it too much to avoid breaking this >> build system. I assume that it may change it the future when you >> release and will adapt if necessary. > > I appreciate that. I have no disruptive plans--indeed, no plans at all > for further development of the feature. I have thought of nothing else > do that is both feasible and helpful in fixing problems with groff's own > pages. (I acknowledge your talent at asking for things that are > NP-hard. ;-) ;-) Cheers, Alex > > Regards, > Branden > > [1] https://git.savannah.gnu.org/cgit/groff.git/tree/doc/doc.am#n232 -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/
