From: Deri <deri@chuzzlewit.myzen.co.uk>
To: linux-man@vger.kernel.org, Alejandro Colomar <alx@kernel.org>
Cc: groff@gnu.org
Subject: Re: Optimize script for generating LinuxManBook.pdf
Date: Thu, 23 Nov 2023 18:41:14 +0000 [thread overview]
Message-ID: <2818350.Jt13fLt2Sg@pip> (raw)
In-Reply-To: <ZV4XNnNlv8OK1B1m@debian>
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
> directory. And every step can be debugged by just introducing
>
> | tee /dev/tty \
>
> wherever you want to debug. It's all pushed to master.
>
> The PDF is now printed to stdout, to avoid hard-coding file names.
>
> I still need to split a bit more and reduce the longest lines. How does
> this script look to you?
>
> Cheers,
> Alex :-)
>
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). If you
are going to run preconv it is best to run it first - stops pic spitting out
loads of warnings. You also dropped one stage in second pass, no pic in the
pipeline. This may explain part of the speedup you observed. I don't know if
any of your man pages require pic but they could in the future. The changes I
would advise are:-
--- a/scripts/LinuxManBook/build_linux_man_book.sh
+++ b/scripts/LinuxManBook/build_linux_man_book.sh
@@ -4,8 +4,8 @@
(
"$(dirname "$0")"/prepare_linux_man_book.pl "$1" \
- | pic \
| preconv \
+ | pic \
| tbl \
| eqn -Tpdf \
| troff -Tpdf -dPDF.EXPORT=1 -dLABEL.REFS=1 -dpaper=a4 \
@@ -16,6 +16,7 @@
"$(dirname "$0")"/prepare_linux_man_book.pl "$1";
) \
| preconv \
+| pic \
| tbl \
| eqn -Tpdf \
| (
Cheers
Deri
next prev parent reply other threads:[~2023-11-23 18:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 14:58 Optimize script for generating LinuxManBook.pdf Alejandro Colomar
2023-11-22 17:33 ` Deri
2023-11-22 17:39 ` Alejandro Colomar
2023-11-23 18:41 ` Deri [this message]
2023-11-23 22:12 ` Alejandro Colomar
2023-11-24 11:46 ` Alejandro Colomar
2023-11-30 16:56 ` Deri
2023-11-30 22:38 ` Alejandro Colomar
2023-12-01 0:14 ` Alejandro Colomar
2023-12-01 0:37 ` Alejandro Colomar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=2818350.Jt13fLt2Sg@pip \
--to=deri@chuzzlewit.myzen.co.uk \
--cc=alx@kernel.org \
--cc=groff@gnu.org \
--cc=linux-man@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.