At 2024-03-04T15:29:16-0600, G. Branden Robinson wrote:
> At 2024-03-04T14:22:34-0500, Peter Schaffter wrote:
> > > The other thing to ask is of Peter: assuming you are among the
> > > non-horrified, would you like me to prepare a patch to om.tmac to
> > > migrate it to this new `pdf:lookup` macro?
Hi Lennart,
At 2024-03-04T20:35:24+, Lennart Jablonka wrote:
> With commit 7b47855abd65 ("Update gnulib submodule."), groff doesn’t
> build anymore with OpenBSD yacc, even with the std::atexit thing
> fixed.
>
> Gnulib headers pretending to be C standard library headers
> (lib/sys/types.h and
Hi Doug, Dave, and Peter,
Thank you for the swift feedback, gentlemen.
At 2024-03-04T11:36:55-0500, Douglas McIlroy wrote:
> > (pdfbookmark, pdf*href-M): Use the new mechanism to record a
> > bookmark tag if `PRINTSTYLE` (a mom(7) macro) is _not_ defined
>
> This feels backwards to me. I underst
Hi Branden!
With commit 7b47855abd65 ("Update gnulib submodule."), groff
doesn’t build anymore with OpenBSD yacc, even with the std::atexit
thing fixed.
Gnulib headers pretending to be C standard library headers
(lib/sys/types.h and the like) started requiring to be included
after config.h.
Branden --
> The other thing to ask is of Peter: assuming you are among the
> non-horrified, would you like me to prepare a patch to om.tmac to
> migrate it to this new `pdf:lookup` macro?
Assuming the migration in no way interferes with the status quo of
mom, yes, please prepare a patch and send
On 3/4/24, G. Branden Robinson wrote:
> The following change could probably use some additional eyeballs. It's
> one of the things Deri and I disagreed about.
Is Deri's view archived anywhere?
On 3/2/24, G. Branden Robinson wrote:
> Often in *roff typesetting, things like tables of contents come at the
> end of the document because it is only then that enough information is
> known to format them correctly. This can be true of cover sheets too if
> some reason they require information
On 2/23/24, Larry Kollar wrote:
> But in the case of groff, there’s at least twice as many years of inertia
> (compared to XML) to consider. It really does make sense that an -mm
> based book file should invoke the macro package(s) it needs, but so
> many of us are automatically going to put that
Haha. I hate to turn down accolades, but this isn't my crusade alone:
http://en.wikipedia.org/wiki/Wikipedia:It_should_be_noted
(But I do love that the Hamilton College Writing Center's page
"Eliminating Wordiness"
(http://www.hamilton.edu/academics/centers/writing/writing-resources/eliminating-w
> (pdfbookmark, pdf*href-M): Use the new mechanism to record a bookmark
> tag if `PRINTSTYLE` (a mom(7) macro) is _not_ defined
This feels backwards to me. I understand pdf.tmac to be a low-level macro
package that other packages can invoke. It shouldn't have to know what
packages are going to use
Hi folks,
The following change could probably use some additional eyeballs. It's
one of the things Deri and I disagreed about.
First, I'd like to know if it horrifies anyone, or if anyone has
concerns about the performance hit. I'm willing to pay a little bit of
performance if I can buy robustn
11 matches
Mail list logo
