From: Alejandro Colomar <alx.manpages@gmail.com>
To: Bernd Petrovitsch <bernd@petrovitsch.priv.at>
Cc: g.branden.robinson@gmail.com, groff@gnu.org,
linux-man@vger.kernel.org, Ingo Schwarze <schwarze@usta.de>
Subject: Re: .so colophon.man
Date: Tue, 2 Aug 2022 12:29:47 +0200 [thread overview]
Message-ID: <5d401f91-3c12-d97f-8934-2f72e73a0470@gmail.com> (raw)
In-Reply-To: <98debad8-80ed-b6e9-b926-44c07b09325e@petrovitsch.priv.at>
[-- Attachment #1.1: Type: text/plain, Size: 1289 bytes --]
Hi Bernd,
On 8/2/22 12:24, Bernd Petrovitsch wrote:
> Hi all!
>
> On 31/07/2022 14:38, Alejandro Colomar (man-pages) wrote:
> [...]
>> I think I'll remove the COLOPHON. One less problem.
>
> Or add another preprocessing step which resolves another type
> of include for such cases.
>
> Idk if resolving the /^\.so / with a simple perl/whatever script
> seems useful sensible or kills some other feature.
>
> Kind regards,
> Bernd
Actually, I'm appending the COLOPHON right now in a very simple way (no
need for perl(1) if sh(1) can do it):
find man?/ -not -type d \
|xargs sed -i "\$a \\
.SH COLOPHON\\
This page is part of release\\
$(git describe | sed 's/^man-pages-//')\\
of the Linux\\
.I man-pages\\
project.\\
A description of the project,\\
information about reporting bugs,\\
and the latest version of this page,\\
can be found at\\
.UR https://www.kernel.org/doc/man-pages/\\
.UE .
"
Oh, and I just realized that I'm also appending it to link pages. I
should fix that!
I'm still not convinced about what to do with the COLOPHON, so I'll
leave the script around for now. But it may happen that I simply drop
it in the future.
Cheers,
Alex
--
Alejandro Colomar
<http://www.alejandro-colomar.es/>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2022-08-02 10:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-30 20:45 .so colophon.man Alejandro Colomar (man-pages)
2022-07-31 12:20 ` Ingo Schwarze
2022-07-31 12:38 ` Alejandro Colomar (man-pages)
2022-08-02 10:24 ` Bernd Petrovitsch
2022-08-02 10:29 ` Alejandro Colomar [this message]
2022-08-06 12:00 ` Bernd Petrovitsch
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=5d401f91-3c12-d97f-8934-2f72e73a0470@gmail.com \
--to=alx.manpages@gmail.com \
--cc=bernd@petrovitsch.priv.at \
--cc=g.branden.robinson@gmail.com \
--cc=groff@gnu.org \
--cc=linux-man@vger.kernel.org \
--cc=schwarze@usta.de \
/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