[bug #63967] [eqn] add "gifont" as synonym of "gfont"

Update of bug #63967 (project groff): Status: Need Info => Confirmed Assigned to:None => gbranden ___ Follow-up Comment #3: We seem to have

[bug #64043] mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT troff

Update of bug #64043 (project groff): Summary: regression introduced with bug #62688: [ms] inter-display distance accumulates with other vertical space--it should not => mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT

[bug #64043] regression introduced with bug #62688: [ms] inter-display distance accumulates with other vertical space--it should not

Update of bug #64043 (project groff): Status:None => Rejected Assigned to:None => gbranden ___ Follow-up Comment #1: > the changes made

[bug #64043] regression introduced with bug #62688: [ms] inter-display distance accumulates with other vertical space--it should not

Update of bug #64043 (project groff): Open/Closed:Open => Closed ___ Reply to this item at: ___

[bug #64043] mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT troff

Follow-up Comment #4, bug #64043 (project groff): Also failing to see where that's mixing formatting requests with macro calls... .nr PS 1v .nr DD 0v .LP 1 .NH 2 .EQ 3 .EN .NH 4 .LP 5 .DS 6 .DE .NH 7 .LP 8 ___ Reply to this item at:

[bug #64043] mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT troff

Follow-up Comment #2, bug #64043 (project groff): In your screenshots I see 13 pixels vs. 26 pixels of vertical space before "Rule: Braces can always be..." - this seems significant to me (and I thought that difference was obvious enough). I fail to see the relevance of "the equation at lines

[bug #64043] mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT troff

Follow-up Comment #3, bug #64043 (project groff): Attached screenshots ms-1.png and ms-2.png show vertical space of 25 pixels vs 12 pixels - also seems significant and quite obvious to see. (file #54622, file #54623) ___ Additional Item

[bug #64043] mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT troff

Follow-up Comment #7, bug #64043 (project groff): Oh, I forgot to mention after that long detour through Lesk's 1979 tmac.s... Even though your display distance is 0, there is still vertical space after the equation in your small sample document because a section heading follows. I predict, but

[bug #64043] mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT troff

Follow-up Comment #5, bug #64043 (project groff): Assuming for the sake of argument that the same "anonymous" is replying as filed the initial report... [comment #2 comment #2:] > In your screenshots I see 13 pixels vs. 26 pixels of vertical space > before "Rule: Braces can always be..." -

[bug #64043] mixing formatting requests with macro calls produces different unspecified behavior with groff than with AT troff

Follow-up Comment #6, bug #64043 (project groff): [comment #3 comment #3:] > Attached screenshots ms-1.png and ms-2.png show vertical space of 25 pixels vs 12 pixels - also seems significant and quite obvious to see. > > (file #54622, file #54623) [comment #4 comment #4:] > Also failing to see

[bug #64043] regression introduced with bug #62688: [ms] inter-display distance accumulates with other vertical space--it should not

URL: Summary: regression introduced with bug #62688: [ms] inter-display distance accumulates with other vertical space--it should not Group: GNU roff Submitter: None Submitted: Thu 13 Apr