From: Alejandro Colomar <alx@kernel.org>
To: Deri James <deri@chuzzlewit.myzen.co.uk>, linux-man@vger.kernel.org
Cc: groff@gnu.org
Subject: Optimize script for generating LinuxManBook.pdf
Date: Wed, 22 Nov 2023 15:58:56 +0100 [thread overview]
Message-ID: <ZV4XNnNlv8OK1B1m@debian> (raw)
[-- Attachment #1: Type: text/plain, Size: 1304 bytes --]
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 :-)
$ cat scripts/LinuxManBook/build_linux_man_book.sh
#!/bin/sh
# Copyright 2023, Alejandro Colomar <alx@kernel.org>
# SPDX-License-Identifier: GPL-3.0-or-later
(
"$(dirname "$0")"/prepare_linux_man_book.pl "$1" \
| groff -z -dPDF.EXPORT=1 -dLABEL.REFS=1 -dpaper=a4 -Tpdf -k -pet \
-M"$(dirname "$0")" -mandoc -manmark \
-F"$(dirname "$0")" -P-pa4 \-rC1 -rCHECKSTYLE=3 2>&1 \
| LC_ALL=C grep '^\. *ds ';
"$(dirname "$0")"/prepare_linux_man_book.pl "$1";
) \
| preconv \
| tbl \
| eqn -Tpdf \
| (
troff -Tpdf -ms <"$(dirname "$0")"/LMBfront.ms;
troff -Tpdf -M"$(dirname "$0")" -mandoc -manmark \
-F"$(dirname "$0")" -dpaper=a4;
) \
| gropdf -F"$(dirname "$0")" -pa4;
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2023-11-22 14:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-22 14:58 Alejandro Colomar [this message]
2023-11-22 17:33 ` Optimize script for generating LinuxManBook.pdf Deri
2023-11-22 17:39 ` Alejandro Colomar
2023-11-23 18:41 ` Deri
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=ZV4XNnNlv8OK1B1m@debian \
--to=alx@kernel.org \
--cc=deri@chuzzlewit.myzen.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox