ayberkt / chalmers-msc-thesis-template Goto Github PK

I removed the parskip package because it's mostly not needed: we do not want paragraph to be separated with empty lines. It was also tampering with other stuff like mathematical environments.

It seems that the only function of parskip was to get the formatting of the front matter correct. Hence some lines in the front pages are now incorrectly formatted but this should be easy to fix (by using \noindent for instance)

As this template seems to be coming together, I think we can let Birgit Grohe know so that she can add a link in the Canvas page.

The acknowledgements page is not included in the TOC. Should it be?

As laid out in #17 it is tricky to manage the Tectonic cache in the following setup as GitHub's docker actions binds their home environment from outside of Docker, rendering any Docker-prepared cache useless.

Since I don't want to modify the testing script with ugly hacks to fix this issue (my plan is that the testing script should be usable locally as well as in the CI), my plan forward is to define the CI workflow by using whatever the alternative to Docker is called.
A benefit of this is that we actually could cache quite much of the setup in that case, for instance the Tectonic binary and deps AND the TeX cache.

I think we should activate branch protection for the master branch. I noticed that I've accidentally pushed two commits (1ed43c8, f384287, feel free to rebase the history and remove, or revert) to master, believing that I pushed them to my own fork..

The branch protection should disable push access to master and force us to use PR's for adding commits to the master branch. This might seem a bit too strict for a project such as this, but keep in mind that you can always merge a PR even if no-one has approved it.

See the documentation for more information and how-to's.

What do you think (and sorry for force-pushing to your repo!)?

I came across a small Docker image for building with tectonic: rekka/tectonic.

We might speed up the CI tests if we use this.

It might be nice to provide, right in the template, some theorem environments using the amsmath package to ensure consistency in style. I think we should include at least the following:

1. Theorem,
2. Lemma, and
3. Definition.

It seems that Chalmers has updated their title page design somewhat recently. At least according to this example it seems quite different to the title page we use.

Should we update the template to make it look like this? I am thinking mainly on the header and footer..

@Jassob I created a Docker image equipped with the minimum requirements for compiling this template (including the fonts): https://hub.docker.com/r/ayberkt/latex.

Can you use it to set up CI testing using GitHub actions? I have no idea how to use it since I use GitLab for this purpose.

Now that we have conditional typesetting for both subtitles and divisions, it would be rather simple to use the same mechanism to support cover image.

For some reason, I can't get \keywords command to work correctly..

With this example, I expect the keywords in the abstract to be "Some, random, words" but instead some strange default value ("keywords") pop ups instead.

\input{template/template}

\title{The Thesis Title}
\author{John Doe}

\keywords{Some, random, words}

\begin{document}

\begin{abstract}
  \lipsum[1-3]
\end{abstract}

\end{document}

Note that this is with the following patch applied, as the keywords otherwise are hard-coded to "foo, bar"

diff --git a/settings.tex b/settings.tex
index 31f438f..0b355e7 100644
--- a/settings.tex
+++ b/settings.tex
@@ -62,7 +62,7 @@
   }
   {% KEYWORDS (MAXIMUM 10 WORDS)
    \vfill
-   Keywords: foo, bar
+   Keywords: \@keywords

    \newpage	% Create empty back of side
    \thispagestyle{empty}

The result is available here.