Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > gnu.groff.bug > #1908
| From | Dave <INVALID.NOREPLY@gnu.org> |
|---|---|
| Newsgroups | gnu.groff.bug |
| Subject | [bug #58736] -me macros: footnote breaks two-column output |
| Date | 2020-07-20 06:40 -0400 |
| Message-ID | <mailman.212.1595241638.24492.bug-groff@gnu.org> (permalink) |
| References | (2 earlier) <20200718-040450.sv108747.46573@savannah.gnu.org> <20200718-143506.sv93119.23489@savannah.gnu.org> <20200718-231440.sv108747.58751@savannah.gnu.org> <20200719-105019.sv93119.74612@savannah.gnu.org> <20200720-054037.sv93119.38237@savannah.gnu.org> |
Follow-up Comment #6, bug #58736 (project groff):
Replying to myself:
[comment #5 comment #5:]
> Savannah unfortunately requires -me bugs be categorized under
> "Macro - others," so it's hard to tell how many are filed here.
> I've opened at least eight
I realize my prolific bug-opening is skewing these results, but for
comparison, currently mm has 8 open bugs, ms 4, man 7, mdoc 6, and mom 1. By
those numbers, adding a specific -me category to savannah seems justified.
-me is also the only full-service macro package lacking its own category.
> ones like this one and bug #58447, where merely describing how
> to trigger them requires an essay.
Perhaps a better thing for the -me documentation to include than complete
descriptions of these bugs is links to the savannah bug reports still open at
the time of the release.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?58736>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/
Back to gnu.groff.bug | Previous | Next | Find similar
[bug #58736] -me macros: footnote breaks two-column output Dave <INVALID.NOREPLY@gnu.org> - 2020-07-20 06:40 -0400
csiph-web