public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Deri <deri@chuzzlewit.myzen.co.uk>
To: linux-man@vger.kernel.org, Alejandro Colomar <alx@kernel.org>,
	linux-kernel@vger.kernel.org
Subject: Re: man-pages-6.10 released
Date: Thu, 23 Jan 2025 22:53:04 +0000	[thread overview]
Message-ID: <5879567.Si16P0KhqQ@pip> (raw)
In-Reply-To: <glkd5bliwzofuoevcr5uqxkkebrwnwfqxiea4dblnjjj24sl72@22f5lir52umy>

On Wednesday, 22 January 2025 22:26:48 GMT Alejandro Colomar wrote:
> Gidday!
> 
> I'm proud to announce:
> 
>         man-pages-6.10 - manual pages for GNU/Linux

Hi Alex,

I have noticed in recent releases using a newer version of groff, the overview 
panel was getting double entries. Here's a patch to fix it. 

================================================================================

diff --git a/share/mk/build/pdf/book/prepare.pl b/share/mk/build/pdf/book/
prepare.pl
index ef8c17b18..4620072ca 100755
--- a/share/mk/build/pdf/book/prepare.pl
+++ b/share/mk/build/pdf/book/prepare.pl
@@ -184,7 +184,7 @@ sub BuildPage
                                # Add a level two bookmark. We don't set it in 
the TH macro since the name passed
                                # may be different from the filename, i.e. 
file = unimplemented.2, TH = UNIMPLEMENTED 2
 
-                               print ".pdfbookmark -T $bkmark 2 $nm($sec)\n";
+                               print ".pdfhref M -N $bkmark\n";
 
                                next;
                        }

================================================================================

Cheers

Deri



  reply	other threads:[~2025-01-23 23:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-22 22:26 man-pages-6.10 released Alejandro Colomar
2025-01-23 22:53 ` Deri [this message]
2025-01-24  0:00   ` Alejandro Colomar
     [not found] ` <34ff2ea5-cf9f-4401-8fd9-7292a4b4b4d1@SystematicSW.ab.ca>
2025-01-26 20:34   ` 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=5879567.Si16P0KhqQ@pip \
    --to=deri@chuzzlewit.myzen.co.uk \
    --cc=alx@kernel.org \
    --cc=linux-kernel@vger.kernel.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