[bug #64869] [bjarnigroff] master branch, is the version from "nroff -v" always the same as from "groff -v"?

Update of bug #64869 (project groff): Status: Need Info => Invalid Assigned to:None => barx Open/Closed:Open => Closed

[bug #64719] tmac/www.tmac.in: missing a word in a comment

Update of bug #64719 (project groff): Severity: 3 - Normal => 2 - Minor ___ Reply to this item at: ___ Messag

[bug #64889] warnings from new texinfo, version 7.1

URL: Summary: warnings from new texinfo, version 7.1 Group: GNU roff Submitter: bjarniig Submitted: Sun 12 Nov 2023 11:15:38 PM UTC Category: Utilities Severit

[bug #64889] warnings from new texinfo, version 7.1

Follow-up Comment #1, bug #64889 (project groff): [comment #0 original submission:] > Overfull \hbox (13.73018pt too wide) in paragraph at lines 18510--18510 > [][] @texttt This paragraph is marked with a margin character. |[] > > Overfull \hbox (13.73018pt too wide) in paragraph at line

[bug #64889] doc/groff.texi: warnings from texinfo 7.1

Update of bug #64889 (project groff): Category: Utilities => Core Severity: 3 - Normal => 2 - Minor Summary: warnings from new texinfo, version 7.1 => doc/groff.texi: warnings from texinfo

[bug #64869] [bjarnigroff] master branch, is the version from "nroff -v" always the same as from "groff -v"?

Follow-up Comment #4, bug #64869 (project groff): [comment #3 comment #3:] > [comment #2 comment #2:] > > This report can be closed a "resolved". > > "Resolved" isn't one of the choices; "Fixed" is the closest, but as far as I know that status is only applied to bugs that result in git commits.

[bug #64869] [bjarnigroff] master branch, is the version from "nroff -v" always the same as from "groff -v"?

Follow-up Comment #5, bug #64869 (project groff): Sorry--attached the wrong screenshot. (file #55322) ___ Additional Item Attachment: File name: savannah-groff-status-definitions.png Size:145 KB