Added index
This commit is contained in:
parent
b8fcf962d3
commit
354ae98ca8
@ -35,6 +35,12 @@
|
|||||||
%\renewcommand*\ShowFrameColor{\color{red}}
|
%\renewcommand*\ShowFrameColor{\color{red}}
|
||||||
|
|
||||||
|
|
||||||
|
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||||
|
%% Indices %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||||
|
\usepackage{imakeidx}
|
||||||
|
\makeindex[intoc]
|
||||||
|
|
||||||
|
|
||||||
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||||
%% Commands %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
%% Commands %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
|
||||||
\graphicspath{{images/}} % Where are our images?
|
\graphicspath{{images/}} % Where are our images?
|
||||||
@ -156,7 +162,7 @@ What I'm going to do here is describe how I understand Git. I am far from a powe
|
|||||||
|
|
||||||
Git is great if you are a software developer, because as you work you make a \textit{lot} of changes to your code. It's also great if you are a writer, because you can experiment as much as you want and not have to worry about losing or overwriting something. You can just revert to an earlier version, or \textit{branch} in order to experiment. But more about that later.
|
Git is great if you are a software developer, because as you work you make a \textit{lot} of changes to your code. It's also great if you are a writer, because you can experiment as much as you want and not have to worry about losing or overwriting something. You can just revert to an earlier version, or \textit{branch} in order to experiment. But more about that later.
|
||||||
|
|
||||||
Git works best with text-based files—basically, anything that has a \texttt{.txt}, \texttt{.html}, \texttt{.css}, \texttt{.php}, etc. extension will work. There's no reason that you can't add binaries, such as images, pdfs, Microsoft Word files, or LibreOffice files. (I'm writing this zine in \LaTeX{}, and do include a few images in most issues, for example.) The issue is that because they are binaries, Git won't be able to tell you the difference between versions. (I would add, though, that if you are writing, you really should separate out the content and the styling from the beginning, so that you can focus on the story you want to tell. Plain text files are your friends.)
|
Git works best with text-based files\index{files, text-based}—basically, anything that has a \texttt{.txt}, \texttt{.html}, \texttt{.css}, \texttt{.php}, etc. extension will work. There's no reason that you can't add binaries, such as images, pdfs, Microsoft Word files, or LibreOffice files. (I'm writing this zine in \LaTeX{}, and do include a few images in most issues, for example.) The issue is that because they are binaries, Git won't be able to tell you the difference between versions. (I would add, though, that if you are writing, you really should separate out the content and the styling from the beginning, so that you can focus on the story you want to tell. Plain text files are your friends.)
|
||||||
|
|
||||||
\section{Git Concepts}
|
\section{Git Concepts}
|
||||||
|
|
||||||
@ -379,7 +385,7 @@ Command & Purpose {\& Example, if applicable} \\
|
|||||||
\end{longtblr}
|
\end{longtblr}
|
||||||
|
|
||||||
|
|
||||||
|
\printindex
|
||||||
|
|
||||||
|
|
||||||
\end{document}
|
\end{document}
|
||||||
|
Loading…
Reference in New Issue
Block a user