Merge branch 'nd/wildmatch-double-asterisk'
A pattern with '**' that does not have a slash on either side used to be an invalid one, but the code now treats such double-asterisks the same way as two normal asterisks that happen to be adjacent to each other. * nd/wildmatch-double-asterisk: wildmatch: change behavior of "foo**bar" in WM_PATHNAME mode
This commit is contained in:
@ -237,7 +237,7 @@ match 0 0 0 0 foobar 'foo\*bar'
|
||||
match 1 1 1 1 'f\oo' 'f\\oo'
|
||||
match 1 1 1 1 ball '*[al]?'
|
||||
match 0 0 0 0 ten '[ten]'
|
||||
match 0 0 1 1 ten '**[!te]'
|
||||
match 1 1 1 1 ten '**[!te]'
|
||||
match 0 0 0 0 ten '**[!ten]'
|
||||
match 1 1 1 1 ten 't[a-g]n'
|
||||
match 0 0 0 0 ten 't[!a-g]n'
|
||||
@ -253,7 +253,7 @@ match 1 1 1 1 ']' ']'
|
||||
# Extended slash-matching features
|
||||
match 0 0 1 1 'foo/baz/bar' 'foo*bar'
|
||||
match 0 0 1 1 'foo/baz/bar' 'foo**bar'
|
||||
match 0 0 1 1 'foobazbar' 'foo**bar'
|
||||
match 1 1 1 1 'foobazbar' 'foo**bar'
|
||||
match 1 1 1 1 'foo/baz/bar' 'foo/**/bar'
|
||||
match 1 1 0 0 'foo/baz/bar' 'foo/**/**/bar'
|
||||
match 1 1 1 1 'foo/b/a/z/bar' 'foo/**/bar'
|
||||
|
Reference in New Issue
Block a user