public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: "G. Branden Robinson" <g.branden.robinson@gmail.com>
Cc: Deri James <deri@chuzzlewit.myzen.co.uk>, linux-man@vger.kernel.org
Subject: Re: Linux man-pages PDF book
Date: Sun, 14 Apr 2024 21:55:00 +0200	[thread overview]
Message-ID: <Zhw0lSlm0F2qnqMm@debian> (raw)
In-Reply-To: <Zhv9F9VuAi6qEQ2L@debian>


[-- Attachment #1.1: Type: text/plain, Size: 1622 bytes --]

Hi Branden,

On Sun, Apr 14, 2024 at 05:58:09PM +0200, Alejandro Colomar wrote:
> > > However, our an.tmac is not for appending, but for replacing man(7).
> > > :( I'd like to get rid of that an.tmac fork.  Does your message mean
> > > that if I use groff git HEAD to build our book I can just drop the
> > > fork and use man(7), and groff(1) will do the right thing?
> > 
> > I think so, and want to know if it doesn't.  Also, fair warning, Deri
> > said he observed a CRAZY bad performance regression when building the
> > Linux man-pages book with groff Git HEAD.  If you can reproduce that,
> > then I have some work to do.  Let me know.
> 
> Can't reproduce.  I've removed the an.tmac fork, and added -man to
> troff(1)'s invocation, and get the same times.

I forgot to mention that while I can't reproduce the performance
regression, I see a regression in the navigation panel.  When using
groff.git HEAD's an.tmac, the navigation panel doesn't allow collapsing
an entire chapter, while the Linux man-pages fork of it does allow.
Both PDF books are attached to this message.

> $ time make build-pdf-book 2>/dev/null
> GROPDF		.tmp/man-pages-6.7-53-g5125d867d.pdf
> 
> real	0m13.307s
> user	0m16.229s
> sys	0m0.481s
> 
> $ time make build-pdf-book 2>/dev/null
> GROPDF		.tmp/man-pages-6.7-53-g5125d867d-dirty.pdf
> 
> real	0m13.564s
> user	0m17.060s
> sys	0m0.510s
> 
> (I've built all the dependencies before hand, so that only the PDF is
>  built in these invocations.)
> (The -dirty one uses -man.)

Have a lovely night!
Alex

-- 
<https://www.alejandro-colomar.es/>

[-- Attachment #1.2: man-pages-6.7-53-g5125d867d.pdf --]
[-- Type: application/pdf, Size: 8848415 bytes --]

[-- Attachment #1.3: man-pages-6.7-53-g5125d867d-dirty.pdf --]
[-- Type: application/pdf, Size: 8886213 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2024-04-14 19:55 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-14 11:37 Linux man-pages PDF book Alejandro Colomar
2024-04-14 11:41 ` Alejandro Colomar
2024-04-14 12:01   ` G. Branden Robinson
2024-04-14 12:25     ` Alejandro Colomar
     [not found]       ` <3935722.768hzMJKAL@pip>
2024-04-16  1:02         ` Alejandro Colomar
2024-04-16  2:08           ` G. Branden Robinson
2024-04-16  2:42             ` Alejandro Colomar
     [not found]           ` <44896690.SEQk1G1hEZ@pip>
     [not found]             ` <20240416165157.ml3ntjoozh3mpyzo@illithid>
2024-04-16 20:15               ` Alejandro Colomar
2024-04-16 20:57         ` Alejandro Colomar
2024-04-16 23:17           ` Deri
2024-04-17  9:54             ` Alejandro Colomar
2024-04-17  9:56               ` Alejandro Colomar
2024-04-17 10:28                 ` Deri
2024-04-17 10:33                   ` Alejandro Colomar
2024-04-17 20:01                     ` Deri
2024-04-17 20:48                       ` Alejandro Colomar
2024-04-18  0:26                         ` Deri
2024-04-18  1:09                           ` Alejandro Colomar
2024-04-18 14:45                             ` Deri
2024-04-18  0:44         ` Alejandro Colomar
2024-04-18  1:08         ` Alejandro Colomar
2024-04-14 11:57 ` G. Branden Robinson
2024-04-14 12:32   ` Alejandro Colomar
2024-04-14 12:42     ` Alejandro Colomar
2024-04-14 13:00       ` G. Branden Robinson
2024-04-14 12:56     ` G. Branden Robinson
2024-04-14 15:58       ` Alejandro Colomar
2024-04-14 19:55         ` Alejandro Colomar [this message]
2024-04-14 20:25           ` G. Branden Robinson
2024-04-14 21:06             ` Alejandro Colomar
2024-04-14 14:50 ` 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=Zhw0lSlm0F2qnqMm@debian \
    --to=alx@kernel.org \
    --cc=deri@chuzzlewit.myzen.co.uk \
    --cc=g.branden.robinson@gmail.com \
    --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