Follow-up Comment #7, bug #67380 (group groff): [comment #6 comment #6:] > *roffs flush output lines (to the top-level diversion) > as they go (that is, as they are "completed" and broken),
This is where groff behavior diverges from its forebears. A break seems
sufficient to flush in groff, but not in DWB or Heirloom troffs, going by the
results in bug #56500 comment 4. Perhaps those implementations wait until
some buffer fills up.
> and no known *roffs give `ab` any responsibilities
> regarding any pending output line.
That seems to be true. But I don't use .ab in real life; I'm merely going by
the examples posted so far.
Also, at least Plan 9 and neatroff would need to be tested before speaking of
all known roffs. But I don't think we need to document anything beyond how
groff works, and how it differs from AT&T troff.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?67380>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
signature.asc
Description: PGP signature
