lyceum:0.1.0

[cnaak]

I am submitting

• a new package
• an update for a package

Description: Lyceum is a simple academic book template that is in it's infancy. It may contain bugs and lack features.

I have read and followed the submission guidelines and, in particular, I

• selected a name that isn't the most obvious or canonical name for what the package does
• added a typst.toml file with all required keys
• added a README.md with documentation for my package
• have chosen a license and added a LICENSE file or linked one in my README.md
• tested my package locally on my system and it worked
• excluded PDFs or README images, if any, but not the LICENSE

• ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

[cnaak]

[no-stop] One of the tests is running for about 3 hours now. It is neither failing nor completing... unsure of what to do.

[elegaanz]

Just a suggestion about fonts, but if you prefer to keep Linux Libertine, it can be merged as is.

[elegaanz]

Linux Libertine is no longer the default font in Typst because the Libertinus Serif fork is better maintained, maybe you want to change that here too?

Suggested change

	text-font: ("EB Garamond", "Linux Libertine"),
	text-font: ("EB Garamond", "Libertinus Serif"),

[cnaak]

Surely I'll change there too. Sorry to miss that one instance / Thanks for the diagnostic and suggestion, which I accept.

I've never had this sort of (pull-request's commit amidst comments) before... not sure how's the best way to proceed to accept it, but since I want such a commit on my side (as to tag it properly), I'll proceed by re-committing from my side, which has been automatically updating the PR. This time, it looks like it will go through without errors/warnings.

[elegaanz]

Thank you for making the changes.
If my "suggested change" solved the whole problem, you could just have clicked "commit suggestion" and both of us would have been credited for it. In that case, because there were more occurrences of it to fix, doing it manually was the correct way to do it.

[cnaak]

Thank you, @elegaanz !