\chapter{Coda}

\section{What I Learned About \LaTeX{} While Creating This Issue}

\subsection{\texttt{include} is Your Friend}

Last time around, I mentioned using \verb|\input{<filename>}| to keep your \LaTeX{} GUI happy. But I've also found that using \verb|\input{<filename>}| keeps \textit{me} happy. Creating this zine means I end up with a very long file (the file for issue \#5 was 1005 lines long!) making it time consuming to constanty scroll through the file to get to the last part I was editing. (It's not terrible in and of itself, but repeatedly having to do it impacts my overall efficiency.) 

For this issue, I decided to write up each chapter as a separate file, and then just \texttt{include} that file into my main document. This makes it much easier to manage, and I do feel more efficient. But because I'm using a GUI (Texmaker) I do have to remember to switch back to my main file when I compile the document. Overall, that's a trade-off I can live with. As a bonus, I can comment out chapters I am not concerned about when compiling. This saves both printer paper (since I tend to edit on paper—I'm very old-school in that way) and my adult-onset-attention-deficit-disordered brain.

\subsection{Redefining a Command} 

I switched to the Cantarell font for sans-serif fonts in this issue. The only problem is that it seemed a bit bigger than the serif font around it. So I redefined it in the preamble to make it a bit smaller: 

\begin{Verbatim}[]
\let\oldtextsf\textsf
\renewcommand{\textsf}[1]{\small\oldtextsf{#1}\normalsize}
\end{Verbatim}

The first line saves the \texttt{textsf} command under a new name (\texttt{oldtextsf}). The second line then allows me to renew the original command by using the new name as an input to the original. I added \verb|\small| in front to change the size of the sans-serif text, and added \verb|\normalsize| after it to return to the regular font size.

%\newpage % Use only to keep the afterword together if we end up with orphans
\section{Afterword}

\begin{multicols}{2}
\begin{small}
\paragraph{I cannot believe that this is where we are:}This is the sixth issue of this zine. I originally created this zine to learn \LaTeX{} and also to learn more about Linux (and get some practice with Git in the meantime). I thought I might get at most one or two issues and that would be the end of it. So when I started doing this, I pushed everything to my git repo at \kref{https://git.kjodle.net/kjodle/the-codex}{https://git.kjodle.net/kjodle/the\\-codex}. 

It looks like this is a thing now, and a single repo just won't work. I'm at well over 300 commits in that repo, which doesn't really reveal much about the state of each issue. Going forward, I've decided to make this an organization on my git repo at \kref{https://git.kjodle.net/the-codex-zine}{https://git.kjodle.net/the-codex-\\zine}. That way, each issue can have its own repository and will eventually come to a logical end, instead of being never ending. 

Believe it or not, I also have a forum for it at \kref{https://forums.kjodle.net/forumdisplay.php?fid=15}{https://forums.kjodle.net/\\forumdisplay.php?fid=15}, so if you want to join that forum and share your opinions and ideas, I encourage you to do so.

Starting with this issue, I wrote each chapter in a separate \LaTeX{} file, and then used the \texttt{input} command to include it in the main file. This made writing and editing this issue a lot easier, but I realize now that this method also makes it easier to collaborate with others on the writing of this zine. If you are interested in contributing a chapter to this zine, and are familiar with \LaTeX{} and Git, then you can just clone the repo for the current issue, make your changes, and then file a pull request. 

\label{codeberg}Because you probably don't already have an account on my personal Git server (although if you are interested, contact me and we can talk about it), I'm also pushing the entire thing to Codeberg, which you can see here: \kref{https://codeberg.org/the-codex-zine}{https://codeberg.org/the-codex-zi\\ne}. (I've included the template files that I use for each issue there, so if you want to make your own zine in \LaTeX{}, you can download those and create your own.)

To mark this change, I've made a few changes to the title page to make it a bit cleaner and more inviting, but that's the only change I plan to make. You can expect the same level of quality (both high and low) as you've always gotten.

\paragraph{A shameless bit of self-promotion:} I wanted to learn more about using Tikz in \LaTeX{} so I created a zine of funny (or at least what I found to be funny) Venn diagrams. You can see and even buy a copy on Etsy at \kref{https://wolfgangswishlist.etsy.com/listing/1884948144/funny-venn-diagrams-a-zine-and-coloring}{https://wolfgangswishlist.etsy.co\\m/listing/1884948144/funny-venn-d\\iagrams-a-zine-and-coloring}.

\paragraph{How to Support This Zine}In a lot of ways, this zine is an open source project. It's published under a Creative Commons Attribution Non-Commerical Sharalike 4.0 license (\ccbyncnd)\footnote{See \kref{https://creativecommons.org/licenses/by-nc-sa/4.0/}{https://creativecommons.org/licenses/by-nc-sa/4.0/} for more information.} so there's no reason you couldn't just take this code and do your own thing with it. The only reason somebody hasn't already is that there's just not a huge market for zines about Linux.

You're already doing the best thing you can do to support this zine: you're reading it. (I'm grateful that you are and I hope you're enjoying it.)

But everything that I wrote in section \ref{support} also applies here: Please talk about this zine on whatever social media platforms you participate on and share the Etsy link. And yep, please remember to talk about \textit{why} you like this zine. (Also tell me what you'd like to see more of. Like a lot of creative people, I vacillate between having too many things to talk about and not having enough things to talk about.) If you have friends you think would like this zine, please send them over to take a look, or buy them a copy. If you want to buy some copies in bulk to give away, please contact me so we can work out a pretty hefty bulk discount.

If you want to donate just to keep this thing going, you can always do so via PayPal at

\kref{https://paypal.me/kjodle}{https://paypal.me/kjodle}.

\noindent{}But really, please just read and enjoy this zine. And remember to tell your friends. Thanks!


\paragraph{Me, on social media:} I used to love Twitter, and was disappointed (to say the least) to see what it's devolved into. I am on both Mastodon (\texttt{@kjodle}) and Bluesky (\texttt{@iswpw.bsky.social}). Please feel free to reach out to me there, although I am not nearly as active on either of those platforms as I used to be on Twitter. Maybe someday, again, although I doubt it. Sometimes that which is lost will never be found again.

\paragraph{Zine site:} I make other zines besides this one, which you can read about at \kref{https://just13.click/}{https://just13.click/}. I also have a mailing list there, and I encourage you to sign up for it.  I have to pay if I send out more than one email per month anyway, so I definitely won't be clogging up your inbox.

\paragraph{Dedication:} This issue is dedicated to my mother Carmen Moreno-Parsons (3 September 1950 — 13 February 2026) who never understood my fascination with computers, but did what she could to encourage it.

\medskip
\begin{flushright}
Until next time,\\
thanks for being here,\\—Ken
\end{flushright}

\end{small}
\end{multicols}