João Marcos

Nice issue. > and ouch crashed. This crash was solved but I did not created a new release with it yet. Been busy since the last week. > Normally passing...

Now, focusing on your current issue, I think that we should detect this with the flag `--output`. The usage would be: ```sh ouch d hello.tar.lzma.zst --output - ouch d hello.tar.lzma.zst...

@figsoda great point, everything would need to go to `stderr`, otherwise, decompressing to `stdout` will potentially corrupt all the files, right? It's a small tradeoff.

One could argue it's annoying because `[INFO]` messages are also redirected. Maybe we could add a `-q/--quiet` flag to suppress non-error messages. I knew a tool that switched from stdout...

Yeaah, I'm not a huge fan of that switch logic, so I think this is a moderate solution, will create the issue for it.

Moving this specific part of the discussion to the dedicated issue #114.

@figsoda @SpyrosRoum do you both think that `--format` https://github.com/ouch-org/ouch/issues/110#issuecomment-946916791 should be a thing? If so, I can create it's dedicated issue. Motivations: 1. Overwrite the extensions detection, can be used...

(disclaimer: It's just a suggestion for now, no issues open). `ouch c foo bar baz result --format tar.gz` Would be equivalent to: `ouch c foo bar baz result.tar.gz && mv...

> How much increased time would be tolerable? I'm not sure, we would need to investigate it further, we might even conclude at the end that our current time is...

It's common to speed up this by using an additional buffer, here's an example from `coreutils`: https://github.com/GrayJack/coreutils/blob/dev/uniq/src/main.rs#L25-L32 This saves on OS calls to write into the `stdout` file descriptor, but...