[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug #62801] [me] doc/meref.me.in: `2c`'s first argument can be empty
From: |
G. Branden Robinson |
Subject: |
[bug #62801] [me] doc/meref.me.in: `2c`'s first argument can be empty |
Date: |
Thu, 6 Oct 2022 23:21:20 -0400 (EDT) |
Update of bug #62801 (project groff):
Status: Need Info => Fixed
Assigned to: None => gbranden
Open/Closed: Open => Closed
Planned Release: None => 1.23.0
_______________________________________________________
Follow-up Comment #9:
Fixed in retrospect. I'll add a ChangeLog entry for it.
commit 1ddbb51d0331b2357b861395ebd1740726d31fa3
Author: G. Branden Robinson <g.branden.robinson@gmail.com>
Date: Wed Oct 5 16:49:41 2022 -0500
doc/meref.me.in: Fix content and style nits.
* Annotate empty default arguments more consistently.
* Prefer active voice.
* Mark footnote overflow as a topic that should get more explanation,
but is blocked by bugs.
* Generalize commentary on styling/decoration macros; not all have to do
with font styles. Refer to what happens at the end of an input line
as a "word break". Hard to express that economically: it's a
potential break when filling is enabled and a mandatory break when
it's not.
* Clarify use of `.TS H`.
* Say "front matter", not "front material".
* Clarify issue of AT&T device-independent troff extensions.
_______________________________________________________
Reply to this item at:
<https://savannah.gnu.org/bugs/?62801>
_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/