On Thu, Nov 23, 2023 at 11:12:45PM +0100, Alejandro Colomar wrote:
> > It looks fine, although you have to run the code in
> > "prepare_linux_man_book.pl" twice (to avoid using a temporary file).
>
> Yep. I was wondering if we could change something in the design of
> prepare_linux_man_book.pl
Hi Deri,
On Thu, Nov 23, 2023 at 06:41:14PM +, Deri wrote:
> Hi Alex,
>
> It looks fine, although you have to run the code in
> "prepare_linux_man_book.pl" twice (to avoid using a temporary file).
Yep. I was wondering if we could change something in the design of
prepare_linux_man_book.pl
On Wednesday, 22 November 2023 14:58:56 GMT Alejandro Colomar wrote:
> Hi Deri,
>
> I've optimized from 18.5 s down to 16.3 s the script, by splitting the
> pipeline with this wrapper (and slightly reducing the perl script to
> just print the pages to stdout). BTW, now it can be run from any
>
Hi Deri,
On Wed, Nov 22, 2023 at 05:33:52PM +, Deri wrote:
> Hi Alex,
>
> Is there a git address I can clone to see the changes "in the round” and give
> it a go?
Here's an unstable branch (I rebase often):
On Wednesday, 22 November 2023 14:58:56 GMT Alejandro Colomar wrote:
> Hi Deri,
>
> I've optimized from 18.5 s down to 16.3 s the script, by splitting the
> pipeline with this wrapper (and slightly reducing the perl script to
> just print the pages to stdout). BTW, now it can be run from any
>
Hi Deri,
I've optimized from 18.5 s down to 16.3 s the script, by splitting the
pipeline with this wrapper (and slightly reducing the perl script to
just print the pages to stdout). BTW, now it can be run from any
directory. And every step can be debugged by just introducing
| tee /dev/tty \
