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

Brace expansion possible edge case fix #1061

Closed
wants to merge 1 commit into from
Closed

Conversation

guilherme
Copy link

When there are closing braces '}' before a open brace '{' it must be ignored and considered as literal otherwise the brace expansion won't work properly.
This make the brace expansion more robust since it make the brace expansion work with files that starts with closing braces.

I hope to cover all the cases. I'm not sure if i should put a test case for the File.fnmatch with the File::FNM_EXTGLOB option and if there are more side effects than File.fnmatch.

When there are  closing braces '}' before a open brace '{' it must be
ignored and considered as literal.
@guilherme guilherme changed the title Glob brace expansion edge case fix Glob brace expansion possible edge case fix Oct 22, 2015
@guilherme guilherme changed the title Glob brace expansion possible edge case fix Brace expansion possible edge case fix Oct 22, 2015
@nobu nobu closed this in ff3288f Oct 22, 2015
sonots pushed a commit to sonots/ruby that referenced this pull request Nov 17, 2015
* dir.c (ruby_brace_expand): glob brace expansion edge case fix.
  When there are closing braces '}' before a open brace '{' it
  must be ignored and considered as literal.
  [ruby-core:71138] [Bug ruby#11609]

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@52212 b2dd03c8-39d4-4d8f-98ff-823fe69b080e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

1 participant