Re: REVISED groff 1.24.0 readiness status, and release notes

2024-11-18 Thread G. Branden Robinson
Hi onf, At 2024-11-18T21:43:24+0100, onf wrote: > > The alternative diff is simple: > > [...] > > + warning (WARN_SYNTAX, "not interpreting escaped '%1' in device" > > + " extension command request argument", char(c1)); > > + else > > + warning(WARN_SYNTAX, "

Re: REVISED groff 1.24.0 readiness status, and release notes

2024-11-18 Thread onf
Hi Branden, On Tue Nov 19, 2024 at 12:37 AM CET, G. Branden Robinson wrote: > At 2024-11-18T21:43:24+0100, onf wrote: > > [...] > > Just a small nitpick, but you should probably do s/(warning) /\1/. > > Yes, that was a code style goof. Thanks! Fixed. Hopefully the way I suggested... GNU's code

Re: REVISED groff 1.24.0 readiness status, and release notes

2024-11-18 Thread onf
On Mon Nov 18, 2024 at 5:30 PM CET, G. Branden Robinson wrote: > [...] > I solicit opinions, from anyone, on the foregoing. > > Here's the behavior of the `device` request after this change. > > $ printf '.device ps:exec A B\\~C\\ D\\0E\\|F\\^G\\h".5m"I\\v".5m"J\n' | > ./build/test-groff -Zww | gr

Re: REVISED groff 1.24.0 readiness status, and release notes

2024-11-18 Thread Deri
On Sunday, 17 November 2024 22:17:08 GMT G. Branden Robinson wrote: > Hi Deri, > > At 2024-11-17T20:35:34+, Deri wrote: > > On Sunday, 17 November 2024 04:42:47 GMT G. Branden Robinson wrote: > > > I have added 3 tickets to the release goals. > > > > > > https://savannah.gnu.org/bugs/?64484 >

Re: Code style and languages in the C family (was: REVISED groff 1.24.0 readiness status, and release notes)

2024-11-18 Thread Larry McVoy
On Mon, Nov 18, 2024 at 07:39:09PM -0600, G. Branden Robinson wrote: > At 2024-11-19T01:47:33+0100, onf wrote: > > On Tue Nov 19, 2024 at 12:37 AM CET, G. Branden Robinson wrote: > > > At 2024-11-18T21:43:24+0100, onf wrote: > > > > [...] > > > > Just a small nitpick, but you should probably do s/(

Re: Code style and languages in the C family (was: REVISED groff 1.24.0 readiness status, and release notes)

2024-11-18 Thread onf
On Tue Nov 19, 2024 at 4:14 AM CET, onf wrote: > #define min(x,y) ((x) < (y) ? (x) : (y)) > int i = 1; > printf("min = %s\n", min(i++, 3)); > which prints: > min = 2 s/%s/%d/. I wrote too much shell lately.

Code style and languages in the C family (was: REVISED groff 1.24.0 readiness status, and release notes)

2024-11-18 Thread G. Branden Robinson
At 2024-11-19T01:47:33+0100, onf wrote: > On Tue Nov 19, 2024 at 12:37 AM CET, G. Branden Robinson wrote: > > At 2024-11-18T21:43:24+0100, onf wrote: > > > [...] > > > Just a small nitpick, but you should probably do s/(warning) /\1/. > > > > Yes, that was a code style goof. Thanks! Fixed. > > H

Re: Best practice to create multi-line footer in letters?

2024-11-18 Thread Dave Kemper
On Wed, Nov 13, 2024 at 1:44 PM Oliver Corff via GNU roff typesetting system discussion wrote: > In me, adding a footer with .fo 'arg left'arg center'arg right' works as > expected, with the blatantly obvious limitation that the elements of the > footer should not contain line breaks. > > However,

Re: Code style and languages in the C family (was: REVISED groff 1.24.0 readiness status, and release notes)

2024-11-18 Thread onf
On Tue Nov 19, 2024 at 2:39 AM CET, G. Branden Robinson wrote: > [...] > Personally, I have a strong distaste for jamming parentheses up against > control structure keywords, like `if(` or `switch(`, though I know some > disciples of old-school Bell Labs code will cling to it unto death. > > I also

Re: REVISED groff 1.24.0 readiness status, and release notes

2024-11-18 Thread G. Branden Robinson
Hi Deri, Thanks for your reply--I think we are making some headway toward a meeting of the minds here. At 2024-11-18T13:52:01+, Deri wrote: > On Sunday, 17 November 2024 22:17:08 GMT G. Branden Robinson wrote: > > 1. What are your acceptance criteria for a 1.24.0 release > > candidate? >