On 17 Nov 2018, Adam Borowski wrote: >On Sat, Nov 17, 2018 at 12:02:38PM -0200, Gabriel F. T. Gomes wrote: >> >> and even for `.tar.zstd', `.gem.zstd', `.spkg.zstd', as people are >> probably going to create archives with such extensions. > >Bad idea -- tar doesn't consider .zst_d_ as a valid extension, and >produces an uncompressed tarball (like it does with any unknown >extension). Thus, bash-completion definitely shouldn't show them up.
OK. Thanks for the explanation. >Yeah, it's confusing to have .zst for a compressor named "zstd" -- but >then, there's .gz for gzip, and .lzo for lzop. And this extension has >been reportedly used by zstd's upstream for years, thus it's too late >to change -- too many programs already accepted patches without the d. Likewise. >On the other hand, there's also .tzst (shorthand for .tar.zst) which >only some tools recognize; it might be good to allow it. OK, I'll come up with something. Cheers
