From: Alejandro Colomar <alx@kernel.org>
To: mtk.manpages@gmail.com
Cc: linux-man@vger.kernel.org, branden@debian.org
Subject: Re: pdfman
Date: Sun, 3 Nov 2024 06:31:32 +0100 [thread overview]
Message-ID: <ZycKuuxXSbZI2-Wo@devuan> (raw)
In-Reply-To: <6d09983e-7c7e-c04d-dc02-33d3828594a7@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
[CC += Branden]
Hi Michael,
[Speleology session below]
<https://lore.kernel.org/linux-man/ae31daa2-a44b-2e79-1a70-a95428b7e231@gmail.com/>
On 2021-01-06, Michael wrote:
> Hi Alex,
>
> On 1/5/21 3:05 PM, Alejandro Colomar (man-pages) wrote:
> > Hey Michael,
> >
> > On 1/5/21 1:00 PM, Michael Kerrisk (man-pages) wrote:
> >> function pdfman {
> >> man -Tps -l $1 > /tmp/$(basename $1).$$.ps
> >> ps2pdf /tmp/$(basename $1).$$.ps $1.pdf
> >> evince $1.pdf
> >> }
I was wondering why -Tps and then ps2pdf(1) instead of directly -Tpdf.
Do you remember a reason? We still have the function around (with my
rewrite, but we kept that ps thing), and was wondering if I could
simplify.
Cheers,
Alex
> >
> > Would you mind adding that to a script in scripts/?
>
> I'm not convinced it really belongs in there.
>
> Thanks,
>
> Michael
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
prev parent reply other threads:[~2024-11-03 5:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-04 22:45 [PATCH] circleq.3, list.3, slist.3, stailq.3, tailq.3: Improve readability, especially in SYNOPSIS Alejandro Colomar
2021-01-04 23:05 ` Alejandro Colomar (man-pages)
2021-01-05 13:25 ` Michael Kerrisk (man-pages)
2021-01-05 22:39 ` [PATCH v2] " Alejandro Colomar
2021-01-05 22:53 ` Alejandro Colomar (man-pages)
2021-01-06 12:54 ` Michael Kerrisk (man-pages)
2021-01-06 11:12 ` Michael Kerrisk (man-pages)
2021-01-05 12:00 ` [PATCH] " Michael Kerrisk (man-pages)
2021-01-05 14:05 ` pdfman Alejandro Colomar (man-pages)
2021-01-06 11:09 ` pdfman Michael Kerrisk (man-pages)
2024-11-03 5:31 ` Alejandro Colomar [this message]
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=ZycKuuxXSbZI2-Wo@devuan \
--to=alx@kernel.org \
--cc=branden@debian.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/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