João Marcos

Thanks for the info, we don't have extra logs, and we can't reproduce it, I don't even know where to start debugging. This may be a long journey but if...

I think it does get statically linked automatically when compiling with musl in Ubuntu (that's [what our CI does](https://github.com/ouch-org/ouch/blob/557f42af926c8f357874871d91fad59073e3e0e8/.github/workflows/build-and-test.yml#L88-L99)).

``` ... "first archive"> a/b/file1 ... "second archive"> a/b/file2 ``` Those are different files, was this on purpose? If so, I don't understand why the `cat` is there.

> Sourcing the completion script and then running test will not suggest bar and test bar will not suggest --my-flag. The first bug was solved, but the second still exists....

I think those were our previous integration tests, I asked @vrmiguel to add the Python script back in this comment https://github.com/ouch-org/ouch/pull/337#issuecomment-1373050212 Maybe this is redundant but we can change it...

The ecosystem's solution doesn't seem reliable, from the [zip crate (0.6.3) documentation](https://docs.rs/zip/0.6.3/zip/read/struct.ZipArchive.html#warning): ``` [Warning] The implementation of the cryptographic algorithms has not gone through a correctness review, and you should...

This is a follow-up to https://github.com/ouch-org/ouch/pull/321 (kinda), having this kind of specific and unpredictable behavior for smart unpack makes me question if we have a better solution for this, and...

@figsoda > `--dir` should just work as if we `cd`ed before unpacking, which I'm not sure is the behavior right now Yeah that's the current behavior I was complaining about....

> This explanation ignores the implementation details because those can change at any time. Currently, `Smart Unpack` creates a temporary directory, decompresses inside, and moves stuff to the correct location....

Thanks for the input. About `doggo_0.5`, yeah can you please create a new issue for that? That naming is unreasonable :smile:.