ing, failing an
> assertion, or going computationally asymptotic as it struggles with
> interiority like a character from a Bergman film.
>
> If someone would test GNU troff's boundaries so that I can document what
> those boundaries are, I'd appreciate it.
>
> Same if you can disabuse
> How does the formatter know which parts to fill?
In the case of groff (I can't say anything about the original
troff), I don't think the formatter actually knows or cares,
but simply passes the path on to the device postprocessor,
which just incorporates it into the device-dependent output,
to
I was reading groff_diff(7)'s short and simple description of the GNU
troff drawing command extension, `\D'P'`.
\D'P h1 v1 ... hn vn'
As \D'p', but the polygon is filled.
Instantly (or not, given that I must have read this sentence dozens of
times before without finding it
