All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx@kernel.org>
To: Deri <deri@chuzzlewit.myzen.co.uk>
Cc: linux-man@vger.kernel.org
Subject: Re: Optimize script for generating LinuxManBook.pdf
Date: Fri, 1 Dec 2023 01:14:58 +0100	[thread overview]
Message-ID: <ZWklguznkCz6pdr8@debian> (raw)
In-Reply-To: <ZWkO4qPC4BxkwBNm@debian>

[-- Attachment #1: Type: text/plain, Size: 849 bytes --]

Hi Deri,

On Thu, Nov 30, 2023 at 11:38:18PM +0100, Alejandro Colomar wrote:
> > It replaces the complete LinuxManBook directory and the executable is now 
> > called BuildLinuxMan2.pl.
> 
> I'd prefer if the huge groff code would go in a separate file.  Would
> that make sense?

I've applied a few tweaks to the script you sent before committing it.
The performance is similar, and it's less of a change to the current
code.

<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=0e64299d4dd0df90ea52b3fe6777e5ebfb2484da>

I think we should be able to cut half a second or so if we add a
BuildSec() function so that we don't block the first page until the
entire sort is done.  And it would be also more readable.  Please check.

Cheers,
Alex

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

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

  reply	other threads:[~2023-12-01  0:15 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
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 [this message]
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=ZWklguznkCz6pdr8@debian \
    --to=alx@kernel.org \
    --cc=deri@chuzzlewit.myzen.co.uk \
    --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.