Philip Oakley philipoak...@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
From: Michael J Gruber g...@drmicha.warpmail.net
Junio C Hamano venit, vidit, dixit 20.03.2015 23:38:
Stefan Beller sbel...@google.com writes:
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.
Junio C Hamano venit, vidit, dixit 20.03.2015 23:38:
Stefan Beller sbel...@google.com writes:
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
Signed-off-by: Thomas Schneider thosc...@gmail.com
---
dblatex does print some warnings, but they seem to be irrelevant.
Besides, first patch I submit to git or even to any project using a
mailing list … let’s hope I did everything right :)
Documentation/Makefile | 9 -
1 file changed, 8
On Fri, Mar 20, 2015 at 4:23 AM, Thomas Schneider thosc...@gmail.com wrote:
Signed-off-by: Thomas Schneider thosc...@gmail.com
---
dblatex does print some warnings, but they seem to be irrelevant.
Besides, first patch I submit to git or even to any project using a
mailing list … let’s hope I
From: Stefan Beller sbel...@google.com
On Fri, Mar 20, 2015 at 4:23 AM, Thomas Schneider thosc...@gmail.com
wrote:
Signed-off-by: Thomas Schneider thosc...@gmail.com
---
dblatex does print some warnings, but they seem to be irrelevant.
Besides, first patch I submit to git or even to any project
Stefan Beller sbel...@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
Thomas Schneider thosc...@gmail.com writes:
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
2015-03-20 22:28 GMT+01:00 Junio C Hamano gits...@pobox.com:
I think you misunderstood me. I am not dismissing the need for PDF;
I am just saying that there is no need to directly generate them
from asciidoc sources, especially when there are already manpages
and html pages available as
2015-03-20 21:21 GMT+01:00 Junio C Hamano gits...@pobox.com:
Stefan Beller sbel...@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
From: Junio C Hamano gits...@pobox.com
Stefan Beller sbel...@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
On Fri, Mar 20, 2015 at 1:21 PM, Junio C Hamano gits...@pobox.com wrote:
Stefan Beller sbel...@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
Stefan Beller sbel...@google.com writes:
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
Stefan Beller sbel...@google.com writes:
... 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.
The help framework can choose the backend and the format and it
wouldn't be too outlandish to do git help --pdf add as
14 matches
Mail list logo
