On 5/6/23, G. Branden Robinson wrote:
> Fortunately it's not so bad. "Most recent" was meant to refer to the
> extra-post vertical line space _applied to the output line_, not
> encountered in an escape sequence.
I considered testing this before posting to avoid potentially putting
my foot in my
On 5/6/23, G. Branden Robinson wrote:
> I disagree with this too. Part of the value of encapsulation of the
> fundamental character type inside a formatter-specific type is that we
> can change our minds _again_ if circumstances warrant.
Good point, and that moots all my points in this email. N
At 2023-05-06T22:32:37-0500, Dave Kemper wrote:
> On 5/5/23, G. Branden Robinson wrote:
> > We seem to have an ugly bit of non-orthogonality in this area.
> >
> > quantityregister access
> >
> > extra pre-vertical line spacing n/a
> > vertical (line) spacing
On 5/5/23, G. Branden Robinson wrote:
> We seem to have an ugly bit of non-orthogonality in this area.
>
> quantity register access
>
> extra pre-vertical line spacing n/a
> vertical (line) spacing .v
> extra post-vertical line spaci
At 2023-04-29T22:33:52-0500, Dave Kemper wrote:
> On 4/26/23, G. Branden Robinson wrote:
> > It would probably be a good idea to represent Unicode strings
> > internally using char32_t as a base type anyway, but groff's design
> > under the Unix filter model described above makes the choice less
>
At 2023-04-30T02:42:33-0500, Dave Kemper wrote:
> On 4/27/23, Douglas McIlroy wrote:
> > "Semantic newline" warnings are relatively innocuous. The occasional
> > pitch on this mailing list for paragraph awareness is far less so.
>
> If you're referring here to changing groff's line-by-line proces
Hi Alex,
At 2023-05-03T01:26:55+0200, Alejandro Colomar wrote:
> > troff:man3/unlocked_stdio.3:123: warning [p 2, 1.8i, div '3tbd1,0', 0.3i]:
> > cannot break line
> >
> > an.tmac:man4/cciss.4:164: style: blank line in input
> >
> > man4/console_codes.4:324: warning: table wider than line lengt
Hi Alex,
At 2023-05-03T00:21:33+0200, Alejandro Colomar wrote:
> On 5/2/23 17:10, G. Branden Robinson wrote:
> > There isn't really any such thing as a device-dependent warning,
> > unless you count those thrown by the output driver itself, like
> > grops(1) or grotty(1).
>
> No, I run the output
