Leah Amelia Chen

Also the old PR title is just way too long haha, caught my attention immediately

> All of the dictionaries have build scripts, e.g. [mozcdic-ut-place-name](https://github.com/utuhiro78/mozcdic-ut-place-names/blob/main/src/make.sh?rgh-link-date=2024-05-24T15%3A00%3A08Z) (except for [mozcdic-ut-personal-names](https://github.com/utuhiro78/mozcdic-ut-personal-names)). Is there any merit in packaging the dictionaries "from source" rather than relying on the manually updated...

Also problematic in restricted build environments (like [Nix](https://github.com/NixOS/nixpkgs)) that don't expose `/sys/devices/system/cpu/{possible,present}` to prevent packages from relying on the specific hardware configuration of the build system.

Yeah, what I mean is that we should ideally have one *other* person to serve as a co-translator or a proofreader to ensure the quality of translations.

Any updates? It's really quite annoying to have CI complain about trailing whitespace and having to manually fix it line-by-line

BTW there isn't actually a `new_split:top` — Ghostty currently only does right and down splits due to how the split tree is internally structured. I'll see what I can do...

No longer specific to macOS following #7167

We'd want one unified issue in this case since there's some design work that needs to be done here, such as how it should be shown to the user, how...

This smells like something that never should have worked in the first place. Relying on `.zig-cache` is never a good idea since it by design is a cache folder that...

Why would you want to have it as `never`... 🤦‍♀️ Though I guess it's not that hard to implement