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
The specification does not mention, that the slash character has to be escaped inside brackets to be treated as a single character.
There is special code in the reference implementation, for example editorconfig-core-c, that handles this case, so I do not believe that it's a bug in the implementation. The entire code looks 100% intentional.
The following example illustrates the issue:
pattern: "ab[e/]cd.i"
// matches only
"ab[e/]cd.i"
// does not match
"abecd.i"
"ab/cd.i"
On the other hand:
pattern: "ab[e\\/]cd.i"
// matches
"abecd.i"
"ab/cd.i"
// does not match
"ab\\cd.i"
Since the bracket-syntax is borrowed from regular expressions and the specification just says "every single character in seq", this looks totally wrong. But again, since the reference implementation looks very intentional, I think it's an oversight in the spec to clarify that path separators always have highest precedence and every other syntax is only to be applied to the individual parts of the path.
The text was updated successfully, but these errors were encountered:
The specification does not mention, that the slash character has to be escaped inside brackets to be treated as a single character.
There is special code in the reference implementation, for example editorconfig-core-c, that handles this case, so I do not believe that it's a bug in the implementation. The entire code looks 100% intentional.
The following example illustrates the issue:
On the other hand:
Since the bracket-syntax is borrowed from regular expressions and the specification just says "every single character in seq", this looks totally wrong. But again, since the reference implementation looks very intentional, I think it's an oversight in the spec to clarify that path separators always have highest precedence and every other syntax is only to be applied to the individual parts of the path.
The text was updated successfully, but these errors were encountered: