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
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
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
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-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
