You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To reduce the footprint, I command zstd --long --rm -r C:\Logs
then big .txt are replaced with small .txt.zst, so far so good.
But tomorrow the tree will obviously look like this
And here lies the crux as the aforementioned command will compress existing.txt.zstagain.
Current workaround is find -type f -not -iname *.zst -exec zstd --long --rm {} +
or by means of fd by @sharkdp as follows fd -t f --exclude *.zst -x zstd --long --rm
However, some native exclude switch would be appropriate and appreciated,
e.g. zstd --exclude *.zst --long --rm -r C:\Logs
Do you agree?
The text was updated successfully, but these errors were encountered:
I don't want to add glob match finding support to zstd. However a --exclude-suffix .zst or maybe --exclude-compressed which would ignore (.zst|.gz|.xz|.lz4|...) would be a useful feature.
Dear @facebook,
Imagine there is the following files tree, which is growing day by day.
To reduce the footprint, I command
zstd --long --rm -r C:\Logs
then big
.txt
are replaced with small.txt.zst
, so far so good.But tomorrow the tree will obviously look like this
And here lies the crux as the aforementioned command will compress existing
.txt.zst
again.Current workaround is
find -type f -not -iname *.zst -exec zstd --long --rm {} +
or by means of fd by @sharkdp as follows
fd -t f --exclude *.zst -x zstd --long --rm
However, some native exclude switch would be appropriate and appreciated,
e.g.
zstd --exclude *.zst --long --rm -r C:\Logs
Do you agree?
The text was updated successfully, but these errors were encountered: