Skip to content
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

Replace glob expansion setting with warning #191

Open
gisostallenberg opened this issue Jun 24, 2016 · 1 comment
Open

Replace glob expansion setting with warning #191

gisostallenberg opened this issue Jun 24, 2016 · 1 comment

Comments

@gisostallenberg
Copy link

A glob expansion does not happen when arguments are properly quoted, as can be seen in this example:

$ touch file1.ext file2.ext 
$ ls 'file*.ext'
ls: cannot access file*.ext: No such file or directory
$ ls file*.ext
file1.ext  file2.ext

I think having this properly configured on multiple environments/machines is harder than properly quote the arguments as is done with the ProcessBuilder for example.

I suggest replacing the documentation with a warning and add this warning at several relevant points in the documentation.
Would you like me to look into this and prepare a PR?

@webmozart
Copy link
Member

@gisostallenberg Yes, I'd appreciate that PR very much!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants