Ingvar Stepanyan

> I'm more than happy to collaborate. Hm I don't represent rawler, so you probably should reach out to each other for that somehow. I was rather thinking that you...

A bit off-topic but meanwhile also found libopenraw, which seems to be actively developed and also has CR3 & metadata support, but it appears to be in much earlier stages...

Realised that for now I can just add ```toml rawler = { git = "https://github.com/dnglab/dnglab" } ``` and Cargo actually finds crates in subdirectories too, so that's probably a bit...

> All these tools should be LGPL2 as they all tend to come from the same original base code. That's a good point. I also just noticed that it seems...

> set a better foundation for porting common cli applications > * Providing a `tcgetattr`, `tcsetattr`, and `cfmakeraw` callback to WASM code should handle terminal aware applications For those coming...

> May I ask how you are going to solve the signals issue? Emscripten already had basic intra-process signal emulation support except for default signal handlers, which I added too....

> Still thats only working for actions the code asked for in the first place like reading from a blocking source. No, not quite - it will work _whenever_ code...

We also need this for gphoto2-rs where libgphoto2 invokes provided callback with logging scope, level and message and we want to translate those to `tracing` events.

Yeah that's what we're going to go with for now, but 1) proper solution would be still nice and 2) that doesn't solve dynamic target case, only dynamic level. That...

Will using `log` work correctly with `[tracing::instrument]` and manual spans? If so, yeah that's an option too and probably easier one. But now I'm curious, in that case how does...