Follow-up Comment #1, bug #68261 (group groff):

In a follow-up message to the _groff_ list,
[https://lists.gnu.org/archive/html/groff/2026-04/msg00039.html I noted some
additional documentation changes that might be made].

Beyond what comment #0 covers, we might...

* add an admonition about the hazards of attempting inline changes of
typeface--beyond what's already documented--with hopeful leaps into the dark;
and

* summarize available full-service macro packages in the "Invoking groff"
chapter of our Texinfo manual.

> On page 10 of groff's Texinfo manual,[8] we document the groff command's
> `-m` option, which loads macro packages.  I see that we could add a list
> of "full-service" macro packages, with citations of man pages thereto--
> employing a syntax I had to invent for this Texinfo manual, the idea
> having evidently been unthinkable heretofore: just as an Emacs user
> never leaves Emacs, an info(1) user never leaves info(1).  We already do
> a similar thing in the synopsis of the `-T` option for selecting an
> output device, so I perceive no incongruity here.
> 
> And besides, the list of full-service macro packages is much shorter
> than the list of output devices.

Karl also offered another observation:

>> Indeed, it never occurred to me that
>> man pages would *not* be covered in the groff manual.

The _man_(7) macro interface *was* presented in _groff_'s Texinfo manual up
through the 1.22.4 release.

In _groff_ 1.23.0, it dropped that material in favor of this cross reference.


4.1 'man'
=========

The 'man' macro package is the most widely used and probably the most
important ever developed for 'troff'.  It is easy to use, and a vast
majority of manual pages ("man pages") are written in it.

   'groff''s implementation is documented in the 'groff_man(7)' man
page.  Type 'man groff_man' at the command line to view it.

* Menu:

* Optional man extensions::


...which seems to me to pretty clearly advise the reader where to look for
more information.


    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?68261>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/

Attachment: signature.asc
Description: PGP signature

Reply via email to