c0per

I kind of get it. So `SystemFontSearcher` and `BrowserFontSearcher` are builder types for a `FontResolver`. If we want to add or edit fonts in a resolver, we should `FontSearcher::reuse()` it...

Checkout [dd347a9](https://github.com/Myriad-Dreamin/tinymist/pull/1636/commits/dd347a9227c964489fa8b4025fac8cd0fa302327). Since `typst::FontBook` doesn't provide any method to edit its content, we only can push more fonts into it, there's no need to maintain a FontBook in searcher. FontBook...

if I understand it correctly, currently there's no way to add `systemd.unified_cgroup_hierarchy=0` somewhere to enable cgroup v1 in orbstack vms right?