arya dradjica

> If the encoding is in a separate crate then I thjnk they should already share a a lot of code and then then the multicall might not be necessary....

Alright, then I'll focus on the streaming interface for now. Hopefully better argument parsing systems can bring the per-binary overhead down.

Status update: I've got basic implementations of all the formats together in my crate [`glassy`](https://git.sr.ht/~bal-e/glassy) ([documentation](https://docs.rs/glassy)). I've got a pretty thorough automated testing setup, but I need to test some...

@sylvestre There are a few reasons why I think this should be a separate dependency: 1. The code being developed forms a good utility library for any Rust project that...

At the moment, even the relatively simple (but complete) implementations of the formats needed by `basenc` add up to two thousand lines of code (three thousand with documentation), and this...

I understand that moving `glassy` under the uutils organization will make it easier for you to maintain it in the future. But I would appreciate it if you could use...

While I love the XDG directory specification, I've seen it cause a lot of trouble in other open-source projects due to backward compatibility issues. I expect that anybody who sets...

> If they set XDG_MUSIC_DIR to something other than $HOME/Music then under the preference order I recommended, it would not matter as XDG_MUSIC_DIR would be used and $HOME/Music would never...

I haven't been able to find any utility to parse `user-dirs.dirs(5)`, so I'll probably write a small utility module to parse it into a `dict[str, pathlib.Path]`. The only other change...

I think this broke the changelog check. For example, from a fresh PR (#5303): : > Invalid workflow file: .github/workflows/changelog_reminder.yaml#L19 > You have an error in your yaml syntax on...