Follow-up Comment #3, bug #67372 (group groff): At 2025-07-28T12:28:38-0400, Ingo Schwarze wrote: > Follow-up Comment #1, bug #67372 (group groff): > > Originally, i intended to file a separate issue for a \w regression, > but now i realize it may be related, so i'll add it here.
Thanks. I, too, would bet that your observations in your follow-up
comment have the same root cause as those in comment #0.
> With the same mnemonics, consider the same two input files,
> with no changes except using \w instead of \A:
>
> .ds v did
> \w\*vs
>
> .nr v 121
> \w\nvs
>
> With groff-1.22.4, the output is "24s" in both cases
> because with nroff, the width of a character is 24u.
>
> With groff-1.23.0, the output is "72" with no trailing "s", and there is a
> bogus message
> troff:tmp.roff:2: warning: missing closing delimiter in width computation
> escape sequence (got a newline)
In _groff_ Git HEAD, I get:
$ ./build/test-groff -aww ATTIC/67372c.groff
troff:ATTIC/67372c.groff:2: warning: missing closing delimiter in identifier
validation escape sequence; expected character 'd', got a newline
<beginning of page>
1
> The result 72 might indicate that the \w parser consumes three characters.
> The last of the three might be the "s", because after that we get the
> complaint about the newline.
> The middle one might be the "i" and "2".
> So maybe "\*" and "\n" are mis-parsed as a first character, instead of
> evaluating them?
> But admittedly, in this last paragraph, i'm merely guessing.
It certainly seems weird.
I'll follow-up with the results of a bisection, I hope later today.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67372>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
