Jonathan Hodgson
55537e9488
|
5 years ago | |
---|---|---|
bin | 5 years ago | |
code-examples | 5 years ago | |
shell | 5 years ago | |
.gitignore | 5 years ago | |
Makefile | 5 years ago | |
README.md | 5 years ago | |
greeting.py | 5 years ago | |
main.latex | 5 years ago |
README.md
Git Presentation
This is a presentation about Git.
Build
To build it, you will need make, pdflatex and ansi-to-svg and inkscape.
To build the main pd, run:
make main.pdf
To build with speaker notes:
make with-notes.pdf
To only build the speaker notes:
make only-notes.pdf
Auto Images
The build system will generate certain types of graphics for the presentation as part of the build system. The resultant files will always go in the auto-images
folder. As a result, this folder is not under version control.
In latex, all you need to do is
\includegraphics[<options>]{auto-<type>-<file>}
The types are documented below:
XKCD
What is a presentation without an xkcd comic?
\includegraphics[<options>]{auto-xkcd-<id>.png}
If the above is included in the latex document, the XKCD comic with the specified ID will be downloaded and embedded in the pdf.
Shell Output
I am still not aware of aware of a reliable way to include ansi coloured shell output into a latex document. I also don't want to include loads of high-res screenshots in my Git repo.
The work around I have come up with is to save the raw ansi output to a wile in shell-output
. This normally involves forcing an application to output in colour:
git -c color.status=always status > shell-output/git-status.out
\includegraphics[<options>]{auto-shell-<filename>.pdf}
%E.g.
\includegraphics[<options>]{auto-shell-git-status.pdf}
The build system will convert the ansi output into an embeddable PDF that LaTeX will embed.