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
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.
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
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/(
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
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, "
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
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?
>
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
>
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
> > https://savannah.gnu.org/bugs/?66452
> > https://savannah.gnu.org/bugs/?66453
>
On Sunday, 17 November 2024 04:42:47 GMT G. Branden Robinson wrote:
> At 2024-11-17T00:44:50+, Deri wrote:
> > On Saturday, 16 November 2024 15:34:36 GMT G. Branden Robinson wrote:
> > > (Even if the in-band singaling was your invention, I have found that in
> > > no situation where I was looki
Hi Deri,
At 2024-11-16T13:02:02+, Deri wrote:
> On Thursday, 14 November 2024 17:44:55 GMT G. Branden Robinson wrote:
> You did commit to adding relevent info from the attached pdf regarding
> the significant changes to gropdf, is this still your intention?
>
> There is now also a gap in the
At 2024-11-17T00:44:50+, Deri wrote:
> On Saturday, 16 November 2024 15:34:36 GMT G. Branden Robinson wrote:
> > (Even if the in-band singaling was your invention, I have found that in
> > no situation where I was looking at pdf.tmac and failed to find
> > documentation I desired, did pdfmark.t
On Saturday, 16 November 2024 15:34:36 GMT G. Branden Robinson wrote:
> Hi Deri,
>
> At 2024-11-16T13:02:02+, Deri wrote:
> > On Thursday, 14 November 2024 17:44:55 GMT G. Branden Robinson wrote:
> > You did commit to adding relevent info from the attached pdf regarding
> > the significant cha
Hi Deri,
I forgot to reply to the first part of your message.
At 2024-11-16T13:02:02+, Deri wrote:
> You did commit to adding relevent info from the attached pdf regarding
> the significant changes to gropdf, is this still your intention?
Yes.
Regards,
Branden
signature.asc
Description: P
On Thursday, 14 November 2024 17:44:55 GMT G. Branden Robinson wrote:
> Hi folks,
>
> tl;dr: Please nominate items for the groff 1.24.0 release announcement!
Hi Branden,
You did commit to adding relevent info from the attached pdf regarding the
significant changes to gropdf, is this still your
On Thu Nov 14, 2024 at 11:12 PM CET, G. Branden Robinson wrote:
> At 2024-11-14T21:15:32+0100, onf wrote:
> > eqn
> > ---
> >
> > * The "gifont" primitive replaces "gfont" as the means of configuring
> >the global italic face in preprocessed equations. "gfont" remains
> >recognized as a
Thanks for the nominations, onf.
At 2024-11-14T21:15:32+0100, onf wrote:
> eqn
> ---
>
> * The "gifont" primitive replaces "gfont" as the means of configuring
>the global italic face in preprocessed equations. "gfont" remains
>recognized as a synonym for backward compatibility. The new
[self-follow-up: surprise! I want to correct myself]
At 2024-11-14T11:44:55-0600, G. Branden Robinson wrote:
> As with groff 1.23.0, I ask the readers of this list to nominate items
> for the release announcement. I can't put the whole 1.24 section of
> the NEWS file in--that would be too long.
On Thu Nov 14, 2024 at 6:44 PM CET, G. Branden Robinson wrote:
> Hi folks,
>
> tl;dr: Please nominate items for the groff 1.24.0 release announcement!
> [...]
eqn
---
* The "gifont" primitive replaces "gfont" as the means of configuring
the global italic face in preprocessed equations. "gfon
Hi folks,
tl;dr: Please nominate items for the groff 1.24.0 release announcement!
I'd like to soft-freeze[1] the groff "Core" code as Savannah puts it
(meaning the [gnt]roff commands and the "libgroff" internal static
library). I've achieved all of the goals (on a freshly shortened list)
that I
21 matches
Mail list logo
