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

Follow-up Comment #8, bug #64043 (project groff): So, are we talking about vertical space inside section 8, or vertical space right before section 11? Your screenshots showed the spacing difference for section 8, my screenshots showed the spacing difference right before section 11. In both cas

[bug #64022] [ms] document how to make your own cover page

Follow-up Comment #1, bug #64022 (project groff): [comment #0 original submission:] > Recent groff mailing list traffic Specifically, http://lists.gnu.org/r/groff/2023-04/msg00036.html and the next two replies in the thread (the thread is long and covers multiple topics, and the subject line give

[bug #63587] [troff] set .R register to maximum representable integer

Follow-up Comment #6, bug #63587 (project groff): [comment #2 comment #2:] > I have to update my enthusiasm level from "I like this" to "I'm OK with this," because I just discovered there _is_ a way to determine INT_MAX from within the roff language. Branden already knew this, having rewritten th

[bug #64032] typos in ms documentation

Update of bug #64032 (project groff): Status: Confirmed => Fixed Open/Closed:Open => Closed Planned Release:None => 1.23.0

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

Update of bug #63967 (project groff): Status: Confirmed => In Progress Planned Release:None => 1.24.0 ___ Reply to this item at:

[bug #60731] undocumented difference in .ce behavior between groff and traditional troff

Update of bug #60731 (project groff): Status: In Progress => None ___ Follow-up Comment #6: This is not in progress until I figure out bug #46914. _

[bug #52517] adjustment can cause overwritten text on lines using \~

Update of bug #52517 (project groff): Status: In Progress => Postponed ___ Follow-up Comment #3: I'm not actively working on this; it seems to be entangled with enough other stuff that I don't fe

Re: [bug #52517] adjustment can cause overwritten text on lines using \~

Hi Branden, On 4/14/23 22:08, G. Branden Robinson wrote: > Update of bug #52517 (project groff): > > Status: In Progress => Postponed > > ___ > > Follow-up Comment #3: > > I'm not actively worki

[bug #60957] adopt term "scaling unit" over "scaling indicator"

Update of bug #60957 (project groff): Summary: adopt terms "scaled width" and "scaling unit" => adopt term "scaling unit" over "scaling indicator" ___ Follow-up Comment #2: Much of this has been done. Here's a grep for ch

[bug #60957] adopt term "scaling unit" over "scaling indicator"

Follow-up Comment #3, bug #60957 (project groff): Whoops--the very first match, in gpinyin(1), is clearly bogus. ___ Reply to this item at: ___ Message

[bug #60957] adopt term "scaling unit" over "scaling indicator"

Follow-up Comment #4, bug #60957 (project groff): The context index entries in our Texinfo manual should be retained, to aid people familiar with the old terminology. ___ Reply to this item at: __

[bug #63587] [troff] set .R register to maximum representable integer

Follow-up Comment #7, bug #63587 (project groff): [comment #6 comment #6:] > When fixing it so that \n[.t] _really did_ return INT_MAX > in a diversion, things started to go wrong. So perhaps the fix is to insert the word "nearly" in the documentation before the phrase "the largest representable

[bug #63587] [troff] set .R register to maximum representable integer

Follow-up Comment #8, bug #63587 (project groff): [comment #7 comment #7:] > [comment #6 comment #6:] > > When fixing it so that \n[.t] _really did_ return INT_MAX > > in a diversion, things started to go wrong. > > So perhaps the fix is to insert the word "nearly" in the documentation before th

[bug #62695] [troff] requests `tag` and `taga` are undocumented

Update of bug #62695 (project groff): Status:None => In Progress Assigned to:None => gbranden Planned Release:None => 1.23.0 ___

[bug #62695] [troff] requests `tag` and `taga` are undocumented

Update of bug #62695 (project groff): Status: In Progress => Fixed Open/Closed:Open => Closed ___ Follow-up Comment #1: commit 80b6e1e2f5941