git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Documentation: Add target to build PDF manpages

From
Stefan Beller <sbeller@google.com>
Date
Mar 20, 2015, 22:19 UTC
Message-ID
<CAGZ79kaDnRiUQ6=3gVvsPrkSzkNbACRvgQBSo8gmpRZ8bka84g@mail.gmail.com>
In-Reply-To
<xmqq4mpfe7xm.fsf@gitster.dls.corp.google.com>
On Fri, Mar 20, 2015 at 1:21 PM, Junio C Hamano <gitster@pobox.com> wrote:
Show 9 quoted lines
> Stefan Beller <sbeller@google.com> writes:
>
>> ... though how would I read man pages in pdf
>> format? I tried searching the web and all I can find is how
>> to convert the a man page to pdf. So is there a conveniant
>> way to tell `man` to prefer opening pdfs when available?
>
> I presume that "man -Tpdf git.1" is not what you are looking for, as
> that would literally be how you get the manpages in PDF format?
Not quite as that is producing a pdf. So I could do
    man -Tpdf git add >tmpfile && evince tmpfile && rm tmpfile
but that is inconvenient to type, so I'd rather be looking for
   man_or_pdf_when_possible git add
and I could alias man_or_pdf_when_possible to a short name.
Show 6 quoted lines
>
> Personally, I honestly am not quite sure why anybody wants to
> generate manpages in the PDF format like this patch does, unless
> they are planning to print them on paper, in which case the existing
> manpages (git.1 and friends) or html pages (git.html and friends)
> should be an already available source format.

This is what I was wondering about as well and my conclusion was it is nicer than the output of man itself to look at, so there must be an obvious command to read pdf instead of man.

Thomas referencing reading the man page offline, made me wonder why you wouldn't read the man pages itself as they can also be carried around offline. But the striking point is "on an iPad", which doesn't offer you the convenience of a shell etc, but pdf is fine to read there. Also you can add comments to pdfs more easily that html pages I'd guess.

So the patch makes sense to me now. It's just a use case I'm personally not interested in for now, but I don't oppose it as is.

Previous: Philip OakleyNext: Junio C Hamano
Message 9 of 14 in “Documentation: Add target to build PDF manpages”
  1. Documentation: Add target to build PDF manpagesThomas Schneider, Mar 20, 2015
  2. Stefan BellerMar 20, 2015
  3. Philip OakleyMar 20, 2015
  4. Junio C HamanoMar 20, 2015
  5. Thomas SchneiderMar 20, 2015
  6. Junio C HamanoMar 20, 2015
  7. Thomas SchneiderMar 20, 2015
  8. Philip OakleyMar 20, 2015
  9. Stefan BellerMar 20, 2015
  10. Junio C HamanoMar 20, 2015
  11. Michael J GruberMar 23, 2015
  12. Philip OakleyMar 24, 2015
  13. Thomas SchneiderMar 25, 2015
  14. Junio C HamanoMar 20, 2015

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.