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

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

From
Thomas Schneider <thosch97@gmail.com>
Date
Mar 25, 2015, 11:43 UTC
Message-ID
<CAJUTLVXC7b4svJ0N4sQGm3+eRpjcQ_8eSv0vSYff=K_x_7mO3A@mail.gmail.com>
In-Reply-To
<DA8ADE6265034B1186A4D63318C6EF3C@PhilipOakley>
Philip Oakley <philipoakley@iee.org> wrote:
> I'd expect 'git help --pdf git' to simply feed the path of git.pdf
> (probably in the same directory as the .html versions) to the web
> browser and let it determine the users prefered reader.

Yes, this is what I would do as well. Unfortunately I don’t really know C, so I can’t implement this. But for someone who is familiar with C, it should be easy---just call `xdg-open` (X11), `open` (OS X) or `start` (Windows) and thus the user’s preferred PDF reader, and maybe some common programs (evince, okular, …) as fallback.

Junio C Hamano <gitster@pobox.com> wrote:
> I didn't see (and I still do not quite see) why people would want to
> have separate pdf files for all the subcommands (instead of say an
> .epub or .pdf that binds all the man pages and perhaps user-manual,
> just like we do for .texi/.info).

Because it’s a good start :-) I see your point, and I agree that a combined PDF/EPUB/etc would make more sense. This should be not too difficult with the AsciiDoc-DocBook-Toolchain (or maybe even without DocBook), I just need to dig into it a bit further.

Previous: Philip OakleyNext: Junio C Hamano
Message 13 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.