Update of bug #66031 (group groff):
Status: In Progress => Fixed
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #2:
commit 1203119417c83d0067a1f6a41007d4a79281c3ae
Author: G. Branden Robinson <[email protected]>
Date: Tue Jan 27 13:43:43 2026 -0600
doc/groff.texi.in: Apply `@g@` prefix to document.
* doc/groff.texi.in: Adapt manual content to the configured groff
command prefix. If the build is configured without a leading
"g"--omitting it has been groff's default for many years, possibly
forever--then our Texinfo manual now omits that prefix when mentioning
the affected commands (all replacements for AT&T troff commands).
This way, if you select a command prefix, say "limbo", and rebuild the
Texinfo manual, the manual reflects the prefix used by your build
configuration, and talks about "limboeqn", "limbotroff", "limborefer",
and so on.
Fixes <https://savannah.gnu.org/bugs/?66031>.
NEWS: Add item.
Also:
* Use Texinfo @command command to mark executable command names, not
@code.
* Break input lines in a *roff-friendly way.
* Replace a semicolon with a more appropriate colon. (I couldn't help
myself.)
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?66031>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
