[bug #56499] adjacent trap behavior undocumented and probably undesirable

Follow-up Comment #4, bug #56499 (group groff): In bug #24050, Dave observed, "Bug #56499 also exists across at least three troffs (DWB troff is not surveyed over there, but Plan 9 troff is)." I therefore modified the document to use only AT&T _troff_ syntax, and reproduced the problem with DWB 3

[bug #56499] adjacent trap behavior undocumented and probably undesirable

Follow-up Comment #3, bug #56499 (project groff): [comment #2 comment #2:] > [comment #1 comment #1:] > > ...I believe _wrongly assume_ that there will be only one next > > trap to be sprung. > > Interesting that this logic error seems to have been made independently in both AT&T troff and groff.

[bug #56499] adjacent trap behavior undocumented and probably undesirable

Follow-up Comment #2, bug #56499 (project groff): [comment #1 comment #1:] > ...I believe _wrongly assume_ that there will be only one next > trap to be sprung. Interesting that this logic error seems to have been made independently in both AT&T troff and groff. (Plan 9 and Heirloom, I believe,

[bug #56499] adjacent trap behavior undocumented and probably undesirable

Update of bug #56499 (project groff): Severity: 3 - Normal => 4 - Important Status:None => Confirmed ___ Follow-up Comment #1: I think I have nearly

[bug #56499] adjacent trap behavior undocumented and probably undesirable

URL: Summary: adjacent trap behavior undocumented and probably undesirable Project: GNU troff Submitted by: barx Submitted on: Sat 15 Jun 2019 05:54:01 AM CDT Category: Core