Re: 1000+ warnings (was: groff_man.7.man.in: Some remarks and editorial changes for this man page)

2024-10-10 Thread G. Branden Robinson
Hi Deri, At 2024-10-11T00:06:10+0100, Deri wrote: > On Wednesday, 9 October 2024 16:33:21 BST G. Branden Robinson wrote: > > > If the warning was about the AT&T fontnames being deprecated but > > > no change to the font used (i.e. continue to use CR), even though > > > there would be 1000+ warning

Re: 1000+ warnings (was: groff_man.7.man.in: Some remarks and editorial changes for this man page)

2024-10-10 Thread Deri
On Wednesday, 9 October 2024 16:33:21 BST G. Branden Robinson wrote: > > If the warning was about the AT&T fontnames being deprecated but no > > change to the font used (i.e. continue to use CR), even though there > > would be 1000+ warnings, it would achieve your desire to drop support > > for the

Re: [PATCH] [pic] Add support for arbitrary polygons

2024-10-10 Thread Thomas DUPOND via
Hello Duncan, Le 2024-09-30 à 09:03, Duncan Losin via a écrit : Hi folks, I have written a patch to add support for drawing arbitrary polygons in pic using the existing syntax for multi-segment lines. They can be shaded and filled as expected of other closed objects. Examples attached in polyg

echo vs. printf (was: groff_man.7.man.in: Some remarks and editorial changes)

2024-10-10 Thread Douglas McIlroy
> echo is okay if no literal `\` appears in its argument list. > If one does, I need to switch to printf(1) Wise advice that I'd modify only by s/okay/right/. I believe I've never used printf(1), but if I were preparing tiny test scripts for groff I might well do so. Doug