Note that as made available in the open-sourced DWB 3.3, 'eqnchar' is
a valid troff file. It contains .EQ and .EN and troff comments, much
like groff's own eqnrc.
So technically, it would fail syntacially in an EQN 'include' statement
with an error along the lines of nested .EQ/.EN blocks.
So
>> May I be excused some pride in our delivery of over 400 bug
>> fixes and 150 automated tests?
>
> Fully justified. I'm glad it's finally out in the world. Thank you
> for your tireless work in making groff more featureful, more
> portable, better documented, and less buggy.
Yeah, c
As an ordinary user and lurker on this list, it has been extraordinary to
watch this release come together. Congratulations!
Robert Goulding
Sent from my phone
On Wed, Jul 5, 2023, 10:36 PM Steve Izma wrote:
> On Wed, Jul 05, 2023 at 07:31:50PM -0500, Dave Kemper wrote:
> > Subject: Re: a morse
On Wed, Jul 05, 2023 at 07:31:50PM -0500, Dave Kemper wrote:
> Subject: Re: a morsel of groff 1.23.0 status
>
> On 7/5/23, G. Branden Robinson wrote:
> > May I be excused some
> > pride in our delivery of over 400 bug fixes and 150 automated tests?
>
> Fully justified. I'm glad it's fin
Hi Branden,
On Wed, 5 Jul 2023, G. Branden Robinson wrote:
In your new eqn user's guide, you might spell out the fact that "wig" is
short for "wiggle". My brain failed to come up with that expansion, and
struggled to figure out how characterizing a tilde as a "wig" over
another glyph was e
On Wed, Jul 05, 2023, Dave Kemper wrote:
> On 7/5/23, G. Branden Robinson wrote:
> > May I be excused some
> > pride in our delivery of over 400 bug fixes and 150 automated tests?
>
> Fully justified. I'm glad it's finally out in the world. Thank you
> for your tireless work in making g
On 7/5/23, Damian McGuckin wrote:
> Looking at the ticket, I understand why my search did not bring it up.
Yeah, it's rather light on info itself. The email thread it points to
is plenty detailed, but that won't help with a search. I had an
advantage in finding it because I faintly recalled tha
Hi Damian,
At 2023-07-06T05:56:40+1000, Damian McGuckin wrote:
> On Wed, 5 Jul 2023, G. Branden Robinson wrote:
>
> > > As far as I can tell, the EQN
> > >
> > > include
> > >
> > > does not honour the GROFF_TMAC_PATH search path. I think I would
> > > to see it default to
> > >
> > > . :
On 7/5/23, G. Branden Robinson wrote:
> May I be excused some
> pride in our delivery of over 400 bug fixes and 150 automated tests?
Fully justified. I'm glad it's finally out in the world. Thank you
for your tireless work in making groff more featureful, more portable,
better documente
On Wed, 5 Jul 2023, Dave Kemper wrote:
Should I put this into Savannah?
Sure. This has come up before.[1]
[1] https://lists.gnu.org/archive/html/groff/2022-03/msg00016.html
It even has a Savannah ticket already: http://savannah.gnu.org/bugs/?62932
Silly me
Damian, Savannah lets you add
At 2023-07-05T23:31:54+0200, Bertrand Garrigues wrote:
> I've pushed tag 1.23.0 and published the archive on
> https://ftp.gnu.org/gnu/groff/
Rock and roll, and good times!
> For the announcement email I'll send the mail to info-...@gnu.org as you
> don't have the official maintainer title yet.
Hi Branden,
On dim., juil. 02 2023 at 01:09:41 , "G. Branden Robinson"
wrote:
> At 2023-07-02T19:44:32+0200, Bertrand Garrigues wrote:
>> If no, I'll tag the official 1.23.0 on the latest sha
>> (198346d187de9e340bbf9d4f80c2dc4d42f5f74e), in a few days (let's say
>> in 2-3 days).
>
> Great news-
On 7/5/23, G. Branden Robinson wrote:
> At 2023-07-05T17:35:05+1000, Damian McGuckin wrote:
>> The groff_char(7) special character \(-+ which if read out loud would
>> be "minus or plus" does not work. I only use that in an equation and
>> in EQN, I can get around it by defining
>>
>> define
Hi Branden,
On Wed, 5 Jul 2023, G. Branden Robinson wrote:
As far as I can tell, the EQN
include
does not honour the GROFF_TMAC_PATH search path. I think I would to see it
default to
. : the site-tmac directory : the standard tmac directory
but that might be a dumb idea. W
Hi Branden,
On Wed, 5 Jul 2023, G. Branden Robinson wrote:
I think not, and in fact I have a notion rumbling around in my head to
move many/all of the predefined macros into "eqnrc" to make it more
straightforward for people to (1) see how they're defined; (2) replace
them; and (3) develop th
On Wed, 5 Jul 2023, G. Branden Robinson wrote:
At 2023-07-05T17:35:05+1000, Damian McGuckin wrote:
The groff_char(7) special character \(-+ which if read out loud would
be "minus or plus" does not work. I only use that in an equation and
in EQN, I can get around it by defining
define -
Hi Damian,
At 2023-07-05T14:25:01+1000, Damian McGuckin wrote:
> Should I advocate for the 'eqnchar' symbols to be automatically
> included at 'eqn' startup. After all, namespace pollution for those
> who need none of those symbols is a bad thing.
I think not, and in fact I have a notion rumbling
Hi Damian,
At 2023-07-05T17:35:05+1000, Damian McGuckin wrote:
> The groff_char(7) special character \(-+ which if read out loud would
> be "minus or plus" does not work. I only use that in an equation and
> in EQN, I can get around it by defining
>
> define -+ % { + back 76 up 32 - } %
>
The groff_char(7) special character \(-+ which if read out loud would be
"minus or plus" does not work. I only use that in an equation and in EQN,
I can get around it by defining
define -+ % { + back 76 up 32 - } %
so it is not stopping me doing anything.
Should I put this into Sava
19 matches
Mail list logo
