Follow-up Comment #4, bug#65190 (group groff):
Hi Dave,
[comment #3 comment #3:]
> This seems like a specific case of the general enhancement bug #61453
seeks.
Possibly we could do some ticket merging here (a manual process involving
"closing" as "duplicate", adding cross references in both dire
Follow-up Comment #5, bug#65190 (group groff):
Those steps will solve the problem in the man/mdoc domain. Which is maybe all
you care about for now. It is an easier problem. My point is that bug #61453
is looking for a general solution for continuous rendering that works for all
nroff output --
Follow-up Comment #6, bug#65190 (group groff):
Hi Dave,
[comment #5 comment #5:]
> Those steps will solve the problem in the man/mdoc domain.
Right.
> Which is maybe all you care about for now. It is an easier problem.
For now, yes, because this is a problem that is provoking user complaints
Follow-up Comment #7, bug#65190 (group groff):
[comment #6 comment #6:]
> I've heard no demand expressed for continuously rendered
> ms/me/mm/mom documents.
The act of filing #61453 might be said to constitute demand. ;-)
Granted, for me it's low priority: I have a solution that works, albeit on
Follow-up Comment #2, bug#64344 (group groff):
The thread starting at http://lists.gnu.org/r/groff/2024-01/msg00091.html
(continued under a different subject line, so not linked to that one, at
http://lists.gnu.org/r/groff/2024-01/msg00100.html) points out a language,
Tibetan, where groff's lack o
