[bug #40967] [me] explain how package alters usual `sp` behavior

[G. Branden Robinson]

Update of bug #40967 (project groff):

                 Summary: numerous minor documentation fixes => [me] explain
how package alters usual `sp` behavior

    _______________________________________________________

Follow-up Comment #22:

[comment #21 comment #21:]
> [comment #19 comment #19:]
> > In 2017, around comment #9 or comment #10, the scope of this
> > ticket seems to have narrowed to the `me` package, because the
> > submitter regarded the rest as no longer applicable.
> 
> "No longer applicable" because they'd already been applied, in the string of
50 commits from fb539489
<http://git.savannah.gnu.org/cgit/groff.git/commit/?id=fb539489> to e1e920c7
<http://git.savannah.gnu.org/cgit/groff.git/commit/?id=e1e920c7> (all visible
on exactly one page of the log in the web interface:
http://git.savannah.gnu.org/cgit/groff.git/log/?ofs=3637).  Comment #3
mentioned this briefly but didn't provide detail.

Ahhhhh.  Okay.  I totally overlooked this.

> The 51st of them, which dealt with content rather than just cosmetics, did
malinger

Heh.  Or maybe even me(7)linger...

> into the next release cycle, so yes, depending on what you're measuring,
it's either a single -me patch, or a wide-ranging set of patches.

I admit, you make a good case, but I don't want to encourage anybody to file
50 different tickets like this for Item Group "Lint", so I'm sticking a
retrojective interpretation onto this ticket as essentially consisting of the
content-related issue.

...and updating the Summary accordingly.

I admit I'm indulging a bit of a mallet swing vis à vis pegs and holes.

And I would be remiss if I didn't mention that you get `sp`'s troff semantics
back on title pages created with me(7)'s `tp` request.  This is also now
documented (for the forthcoming groff 1.23.0) in meref.me _and_ groff_me(7). 
(It has long been noted, casually, in meintro.me.)

    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?40967>

_______________________________________________
  Message sent via Savannah
  https://savannah.gnu.org/