João Marcos

I believe I'd also like to see `.gitignore` and `.gitconfig` be ignored by default.

> > .gitconfig > > Not sure if that's a special path? Isn't this file supposed to be in $HOME? Ah, true, this one isn't searched while traversing parent dirs...

> I don't agree with this, I would consider them part of the repository. I think a good comparison is github's archived tarballs. Yes, makes sense, my suggestion was bonkers.

This can be a bit confusing, here's how `-g/--gitignore` works: When recursing through directory entries, do not include the ones in `.gitignore`. (This can be useful if you want to...

> The output of "**ouch --help**" gives "**Usage: ouch [OPTIONS] **" the options before the command. Is it necessary to respect the order? No, `--gitignore` is currently a global flag...

Previous behavior: we always decompress all formats in the chain for all supported files. This PR breaks this, I'm clueless what are the implications of this. We could suggest `ouch...

Thanks for the issue, glad to see you like Ouch :) I can't think of any problems with supporting `.deb`. Yeah it would be the first of the kind (binary...

Makes sense! I never had to compress a `.deb` archive, but countless times I had to decompress it. It's certainly the most common use-case. This would be the first format...

> I think we can support compression with a (arbitrary?) compression method We can choose a default compression method, the problem is providing more required fields that can't have a...

Did you run `cargo install ouch` recently? Can you confirm that was version `0.4.1`? I double-checked and the `0.4.1` code in crates.io is the same as `0.4.1` in our GitHub...