Lots of bugs

Summary (I did not check on Linux, but hopefully, matching there is case-sensitive):

• IsPathSeparator(...) is correct for Windows, but wrong for Linux, as back-slashes are not considered separators. There is even a possibility that the forward-slash is escaped (preceded with the odd number of back-slashes: 1, 3, 5…), hence not considered as a separator
• Current directory and relative paths are not considered
• Path separator assumed to be outside any kind of brackets
• Braces not implemented (this is significant)

Details (YES = all good):

Current Directory: C:\Users\AlexIurovetski\Projects\Dabble\Dabble\bin\Debug\net6.0

Glob:  c:\a\b\..\b\*.cs
Path:  c:\a\b\c.cs
Match: -- NO --

Glob:  **/*.cs
Path:  c:\a\b\c.cs
Match: YES

Glob:  **\*.cs
Path:  c:\a\b\c.cs
Match: YES

Glob:  **.cs
Path:  c:\a\b\c.cs
Match: -- NO --

Glob:  \**\*.cs
Path:  c:\a\b\c.cs
Match: -- NO --

Glob:  *.{cs,txt}
Path:  c:\a\b\c.cs
Match: -- NO --

Glob:  **/{*.md,src/*.cs}
Path:  c:\a\b\c.cs
Match: -- NO --

Glob:  **[/\]*.cs
Path:  c:\a\b\c.cs
Match: -- NO --

[dazinator]

Thanks it’s definitely value feedback. I will consider things I can do to enable this scenario better in future. I’ll open a more targeted issue for now about the Linux filename slash issue.

[aiurovet]

Mainly, I wanted to draw attention to the issues which arise when using glob patterns for filtering files. This is primary use case. Something like a command-line application which expects files to process: customapp ..\otherdir\*.txt or ./customapp "/rootdir/lib*/**.{a,obj}" and so on. You can close the ticket.