jaskij

@IniterWorker you credit me needlessly, I just incorporated this change into my version because I needed both.

I have been meaning to do a ground-up rewrite of the project, since it has other issues and it shouldn't be hard, but I'm not currently working with anything Yocto,...

> Yah, that's what I've been doing, but it seems kinda hacky for production use Those are still files where you manually run the generator and add the output to...

Having looked a little further, this behavior is also wrong according to the current (4.5.32) documentation for `conflicts_with()`.

I see, and understand. In this case, having any non-`Option` required argument when `exclusive()` is used elsewhere is clearly a bug in user code, and the current output is, to...

TLDR: my experience so far with clap has been panics on programmer errors, and the current behavior breaks the pattern, and hence the principle of least surprise. Instead of a...

Oh, absolutely, and the file was fixed. Just wanted to draw your attention to this, in case it was a bug in resvg.

If I'm reading it right, the backend is using a [Go reimplementation](https://github.com/xiatechs/jsonata-go) of JSONata, which has an issue for the percent operator not working: https://github.com/xiatechs/jsonata-go/issues/41

FWIW, as someone actually working with embedded Linux, ARMv7 is a (slowly) dying breed. Sure, it's used, but less and less. A greenfield project will most likely bo on AArch64.

The expectation here is primarily about the state of my terminal when calling `pytest` not influencing the tests, less so about which value is chosen as the default.