https://github.com/tadfisher/pass-otp

The pass android app is really nice too

https://play.google.com/store/apps/details?id=dev.msfjarvis....

It also works in termux

Yes, but each included file (like education.typ, publications.typ, etc) should also get these settings propagated from top - which typst doesn't allow - the appropriate settings need to be included in each of these files.

> you can pass global settings at build time with `typst c --input name=value`

This is something I did not know - will check.

Let's say I have 3 flavors of settings and 10 different typ files - normally I'd just have 3 flavors of top.typ (top1.typ, top2.typ, top3.typ) with the correct settings for each flavor with settings proagated to all 10 files. Compiling top1/top2/top3 would then create flavor1.pdf, flavor2.pdf, and flavor3.pdf

Now how do I do it with settings1.typ, settings2.typ and settings3.typ? I have to go into the 10 different files and include the appropriate settings file! Or employ hacks like creating a common settings.typ using bash in the Makefile and including the common settings.typ in the 10 different files.

Edit: This is an actual use case - I'm helping with a resume, and have 3 different resume styles - a resume, a cv, and a timeline - and different files like education, work experience, honors, awards, publications, projects, etc and the level of detail, style, and what is included or not in each is controlled by which resume style is active. In latex I did this using \newcommand and the ifthenelse package.

In typst, I have had to resort to passing these global settings as arguments to functions spread across these different files, so each resume item (function) instantiated from the top file has a bunch of parameters like detail_level = 1, audited_courses = true, prefix_year = false, event_byline = true, include_url = true, etc., which make the functions unweildy.

1. They should have carried forward the latex standard as-is for math, instead of getting rid of the backslash escape sequence, etc.

2. There is no way to share a variable across a file's scope - so can't have a setting that is shared across files - not even with state variables.

Other than this, typst is solid, and with the neovim editor and tinymist lsp, is great to write with.

https://x.com/sidhant/status/1933160167816007842

Also how do you implement things like different page numbering for front matter content and the main content? In general, the "simplicity" of markdown seems to be taking away a lot of granular control that people use LaTeX and Typst for.

Or neovim with FzfLua (on laptop)

> but it had been some time ago, and they never worked on any of the features

It appears that the candidate might have actually worked on the daycare app, but not on what they said they worked - i.e., the ratelimiting and pagination. It appears that they might have been working on the frontend, and took the liberty of "expanding" their role - this used to be extremely common in a big sample of the resumes, and I'm guessing it still is. They might have used AI to prep - they used to use google earlier, but the prep was (and is) still inadequate if you've not actually worked on and implemented it. I don't think it was an entirely LLM created project...