Shish

Actually there are even more layers in this rabbit hole -- looks like the `env` supplied to this function is _supposed_ to contain the complete parent environment (If I'm reading...

Looking into "reasons why the zed CLI might report an empty environment", I believe my case is a related-but-separate bug (`cargo run` in the root results in `env` being set...

Thank you for the explanation, that has connected some dots :) With that deeper understanding, and my misleading part-of-a-comment removed, I think this is good to go (the only way...

@josser are you launching zed by clicking the `.app`? My understanding is that when you do that, zed gets launched with no locale environment variables at all, and "hard-code en_US...

I like the look of this, but unit tests are failing so can't merge :eyes:

FWIW I ended up building my own package for Debian Testing. I wouldn't recommend using my repo (it is very much built to scratch my own itch), but the Dockerfile...

Update: it seems that python 3.12 was recently removed from Debian Testing, so the Dockerfile that I wrote for self-contained package-building no longer works (it was only working when I...

My gut says to go with the tiniest blurhash (the 5-byte CSS ones) embedded in tracks.json, plus decent-quality separate files for full-size thumbs -- but that is based on a...

I've added a `date` tag like `date:1985-04-24` (YYYY-MM-DD) to a bunch of tracks (not a lot, but enough for testing) pm3 pulls out the first part and generates a `year`...

1 - Multiple encoders per output filetype is already a feature, eg we have both `VideoToAV1()` and `ImageToAV1()` and PM3 chooses which encoder to use based on which input files...