On 5/10/23, Dave Kemper wrote:
> Nonintuitively, .ss's units aren't in fractions of standard
> typographical measurements, but 1/12 of the current font's ordinary
> space.
And I just learned (or maybe relearned) this is a deviation from AT&T
troff's .ss units, which are a fixed 1/36 em.
This dif
On 5/10/23, G. Branden Robinson wrote:
> But it was interesting
> to me to observe the performance of GNU troff and grotty with literally
> billions of lines of input.
I agree, though it wasn't a completely realistic test, with each line
having only one word on it: no filling, no adjusting (thoug
Hi Alex,
I endorse Dave's critique of your measurement. But it was interesting
to me to observe the performance of GNU troff and grotty with literally
billions of lines of input.
At 2023-05-09T15:37:16-0500, Dave Kemper wrote:
> (I can already hear the questions. "Why is the terminal basic unit
On 5/8/23, Alejandro Colomar wrote:
> I couldn't notice the non-infiniteness. See the following session.
I'm not sure what you thought that test was measuring, but I'm pretty
sure it's not what it was actually measuring.
First, the man macros don't set their page length to INT_MAX. This
was a
Hi Branden,
I pushed this.
Cheers,
Alex
*.mk: Use -wbreak in TROFFFLAGS, and -ww in NROFFFLAGS
We don't need to see all warnings everywhere we call troff(1). Instead,
put all warnings in nroff mode, which we only run for the warnings, and
then only ask for warnings that de
Hi Branden,
On 5/8/23 02:29, G. Branden Robinson wrote:
> Hi Alex,
>
> At 2023-05-07T22:42:05+0200, Alejandro Colomar wrote:
>> $ make build-pre-tbl >/dev/null
>> $ grep 'table wider' .tmp/man/man4/console_codes.4.eqn
>> . tm1 " table wider than line length minus indentation
>> . tm1 " table wi
Hi Alex,
At 2023-05-07T22:42:05+0200, Alejandro Colomar wrote:
> $ make build-pre-tbl >/dev/null
> $ grep 'table wider' .tmp/man/man4/console_codes.4.eqn
> . tm1 " table wider than line length minus indentation
> . tm1 " table wider than line length minus indentation
> . tm1 " table wider than
On 5/7/23 03:59, G. Branden Robinson wrote:
> 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
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
Hi Branden,
On 5/2/23 17:10, G. Branden Robinson wrote:
[...]
> Where you're headed with this already sounds tricky, since GNU troff
> (like AT&T device-independent troff) reads information about the device
> for which it is preparing output at the time it starts. In fact, you
> _cannot_ launch
Hi Alex,
At 2023-04-28T15:56:13+0200, Alejandro Colomar wrote:
> Considering a build system that builds man pages into several formats,
> including utf8, PostScript, HTML, and PDF, it is interesting to be
> able to see all available warnings, and see them only once.
Where you're headed with this
11 matches
Mail list logo
