On Sat Feb 22, 2025 at 2:06 AM CET, G. Branden Robinson wrote:
> At 2025-02-22T01:31:28+0100, onf wrote:
> > On Sat Feb 22, 2025 at 12:12 AM CET, G. Branden Robinson wrote:
> > > At 2025-02-21T15:22:02+0100, onf wrote:
> > > [...]
> > > > Ideally, `so` would behave like `tm` except it would trim sp
On Sat Feb 22, 2025 at 12:12 AM CET, G. Branden Robinson wrote:
> At 2025-02-21T15:22:02+0100, onf wrote:
> [...]
> > Ideally, `so` would behave like `tm` except it would trim spaces
> > at the end, but I understand that this would be adding yet another
> > special case.
>
> Alternatively, we could
At 2025-02-22T01:31:28+0100, onf wrote:
> On Sat Feb 22, 2025 at 12:12 AM CET, G. Branden Robinson wrote:
> > At 2025-02-21T15:22:02+0100, onf wrote:
> > [...]
> > > Ideally, `so` would behave like `tm` except it would trim spaces
> > > at the end, but I understand that this would be adding yet ano
On Sat Feb 22, 2025 at 12:21 AM CET, G. Branden Robinson wrote:
> At 2025-02-22T00:11:13+0100, onf wrote:
> > By the way, Heirloom troff has floating point registers.
>
> Just converting the type backing groff's registers from `int` to `long`
> is a significant refactor, because it implicates other
On Fri Feb 21, 2025 at 3:22 PM CET, onf wrote:
> Ideally, `so` would behave like `tm` except it would trim spaces
> at the end, but I understand that this would be adding yet another
> special case.
>
> Honestly, I never liked the fact `ds` doesn't trim trailing spaces.
> I never understood why the
At 2025-02-22T00:11:13+0100, onf wrote:
> By the way, Heirloom troff has floating point registers.
Just converting the type backing groff's registers from `int` to `long`
is a significant refactor, because it implicates other things like the
formatting of diagnostic messages. I found this out whe
At 2025-02-21T15:22:02+0100, onf wrote:
> On Fri Feb 21, 2025 at 3:14 PM CET, onf wrote:
> > Well, I have thought about it a bit since yesterday and I think
> > making `so` similar to `tm` would be a better idea:
> > $ 9 nroff << EOF
> > .tm Lorem ipsum dolor \" print to stderr
> > EOF
> >
On Fri Feb 21, 2025 at 11:41 PM CET, G. Branden Robinson wrote:
> I further observe that a loss of precision threatens.
>
> $ cat EXPERIMENTS/unit-conversion.groff
> .nf
> .nr basic-units-per-cm 1c
> There are \n[basic-units-per-cm] basic units per centimeter.
> The line length is \n[.l] basic unit
Hi Francesco,
At 2025-02-21T16:19:25+0100, Francesco Ariis wrote:
> can I format/scale numbers when interpolating them?
Not without arithmetic, as far as I know.
> Long explanation follows.
>
> While writing a minimal reproducible example for this list,
> I found myself typing:
>
> Lin
Hi Ingo,
as part of documenting the roff escape sequence \!, I want to define
a tag named '!'. Unfortunately, this doesn't seem possible with mandoc.
None of the following work:
.It Ic \e!
.Tg !
.Tg \e!
.Tg \&!
The last two trigger the following errors:
ERROR: skipping tag containing wh
Hello groff users,
can I format/scale numbers when interpolating them?
Long explanation follows.
While writing a minimal reproducible example for this list,
I found myself typing:
Line length is set to:
.nr calc \n[.l]/1c
\n[calc]
Notice how, to interpolate line length in centim
On Fri Feb 21, 2025 at 3:14 PM CET, onf wrote:
> Well, I have thought about it a bit since yesterday and I think making
> `so` similar to `tm` would be a better idea:
> $ 9 nroff << EOF
> .tm Lorem ipsum dolor \" print to stderr
> EOF
> Lorem ipsum dolor
Scrap that, I forgot to verify it's
On Fri Feb 21, 2025 at 4:39 AM CET, G. Branden Robinson wrote:
> At 2025-02-21T04:30:57+0100, onf wrote:
> [...]
> > Is my understanding correct that this change affects compatibility
> > mode too,
>
> Yes.
>
> > thus lessening compatibility with DWB troff?
>
> ...non sequitur. What is it that we'
13 matches
Mail list logo
