Re: groff maintainership, release, and blockers

[Ingo Schwarze]

Hi Branden,

G. Branden Robinson wrote on Sat, Aug 27, 2022 at 06:55:13AM -0500:
> At 2022-08-27T12:49:05+0200, Ingo Schwarze wrote:

>> There remains a regression in man(7) .EX/.EE which i will report ASAP.

> If it's this one, I already pushed a fix days ago.
> 
> commit f287bb7243a7d77e8b4f3a432d00c6f0681b687d
> Author: G. Branden Robinson <g.branden.robinson@gmail.com>
> Date:   Tue Aug 23 12:56:02 2022 -0500
> 
>     [man]: Restore robustness to `EE` misuse.
[...]
>     This regressed post-1.22.4.  Thanks to Ingo Schwarze for the report and
>     a proposed patch.

The remaining problem is that you only committed half of the fix.

The .nf or .fi, respectively, needs to be done unconditionally, like
it was in my original minimal patch, even if an*is-in-example is in the
wrong state, such that even a stray .EX or .EE at least produces a break.

In git master,

  inside
  .EE
  outside

with no .EX now renders as

  inside outside

whereas traditionally, it rendered as

  inside
  outside

The traditional behaviour was better because if the author mistakenly
thinks that an .EX display is open and closes it, that's an unambiguous
signal that they do *not* want to continue output on the same output line.

Yours,
  Ingo