Re: PDFPIC: un-explaned warning

On Tue, Oct 29, 2024 at 01:20:19AM +, Bjarni Ingi Gislason wrote: > File prof.PDFPIC: > > .ll 10n > .PDFPIC -I -\n[.l]u ?/gnu.pdf > .if !r stuff .tm stuff is not defined > > -.- > > The file "gnu.pdf" is in the attachment. > > -.- > > "test-groff.master" should be the same as "test-gro

Re: gropdf: warning when "mixed_pickles.pdf" is created

On Fri, Oct 25, 2024 at 09:20:16PM +, Bjarni Ingi Gislason wrote: > On Thu, Oct 24, 2024 at 11:26:58PM +0100, Deri wrote: > > On Thursday, 24 October 2024 20:46:32 BST Bjarni Ingi Gislason wrote: > > > GROFFcontrib/hdtbl/examples/mixed_pickles.pdf [...] [...] > > The message you quote com

Re: Comparison against backslash obtained via .substring

Hi onf, Parsing strings that contain escapes is something that an open groff bug report (http://savannah.gnu.org/bugs/?62264) seeks to make more consistent. Does the mechanism proposed in that report sound like it would solve the problem you're facing? (By default, the savannah bug tracker displ

Comparison against backslash obtained via .substring

Hi all, I have a bunch of macros which take flags like -c, -nr etc. I wrote a getopt-like parser macro which works something like this: caller: .getopt:setup c nr: .getopt:parse \\$@ .shift \\n[getopt:nshift] getopt:parse: .has-prefix - "\\$1" .while \\n[has-prefix?] \{\ . \" ... .