Hi Ingo,
thanks for confirming this.
On Tue Oct 28, 2025 at 8:00 PM CET, Ingo Schwarze wrote:
> onf wrote on Sat, Oct 18, 2025 at 03:05:55AM +0200:
> [...]
> Also note the bogus warning printed by groff:
>
> mdoc warning: Using a macro as first argument cancels effect of .Dv (#8)
Yes, this warning is what lead me to notice it in the first place.
> The roff(7) language does not predefine many strings as far as i'm aware,
That is true. As groff(7) correctly says:
Only one string is predefined by the language.
\*[.T] Contains the name of the output device (for example, “utf8”
or “pdf”).
> so i also tested with one of the strings predefined by manual page
> macro sets: \*(Ba prints a vertical bar as expected, but a macro
> argument "Ba" prints simply "Ba" rather than a vertical bar.
> So the bug seems unique to .T.
> [...]
That is interesting. I assumed this bug would be due to groff doing
something like
.if d\\$1
without differentiating between mdoc macros and the rest.
That's really odd.
Cheers,
onf
