it is tempting to throw in all the commands from my latex template to use in markdown but I want to stay complient (?) with gitlab markdown so that the files are properly displayed on the gitlab

Qs sind nicht null

etwas demotivierend, wenn selbst der Plan schon langsam ist

necessary if you want to convert markdown written for gitlab to pdf with pandoc
pandoc is the only way I know that works programmatically and locally to convert markdown to pdf and some people might want to get pdfs instead of markdown files, especially those with a lot of math
The math with $`...`$ is the problem. gitlab needs it and LaTeX chokes on the
`

will only change things in non-staging files. So at least if everything was added beforehand, changes of script can be reversed

but the script seems quite reliable now

a pre-commit hook that checks if $ $ without ` exists and a script that introduces the ` where necessary

gitlab has this weird syntax $`ℝ^n`$ to mark math

ein paar Details und Definitionen aufgeschrieben. Viele Sätze nur überflogen. Mal schauen, ob ich sie mir nochmal genauer anschauen muss

They seemed reasonable to take from this document to the template (and
back).