New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Path globbing syntax is not documented #705
Comments
Even a single star matches any folder depth. The asterisk is not bound by path separators: $ s5cmd ls "s3://foo/*.txt"
2024/04/13 09:38:00 3 bar/baz.txt The reason why Lines 63 to 68 in c1c7ee3
And s5cmd gives the S3 API an empty delimiter, instead of Lines 264 to 270 in c1c7ee3
This could be enhanced so that |
Thanks for looking at this. I think the thing I did not see in the documentation was something that explicitly and clearly says "Even a single star matches any folder depth". Perhaps this is what Usage means by "s5cmd supports multiple-level wildcards for all S3 operations" but it is not clear. Personally I prefer clear specification-style descriptions in --help and README.md before showing the examples, rather than just relying on the user to guess meaning from examples, but I am sure not everyone would agree. |
Looking at
README.md
ands5cmd --help
, I see no details about the glob syntax.In particular, it seems
s5cmd
understands the "double star"**
syntax for matching any folder depth, but this is not mentioned in theREADME.md
examples.The text was updated successfully, but these errors were encountered: