Thanks, you've correctly identified the issue, although I wouldn't call it a problem with "my" OS unless it's my configuration.
I just wanted to read the source locally. I know things are getting worse by the month for developers on Windows because other developers are increasingly not giving a shit to support it, but it's odd to have a repo that doesn't even clone on windows.
Not building is common, not passing tests even if it builds is extremely common, but not even cloning is a new one.
I guess eventually I'll give up and switch to linux, but I'm still paid to work on Windows. I guess maybe it's finally time to look into a real dev-container setup for this kind of thing and I can do this all a bit more securely too.
I feel that people still need to support Windows for a while. I for example am stuck on Windows because it (still) has the best accessibility out of all of the operating systems (and Wine is not a replacement for that). It's unfortunate, and I'm hoping it will change in the future.
I’m surprised to hear that, I don’t often use accessibility options on Mac but i use some on iOS so I always assumed Apple had the best a11y since there are so many options on iOS. Like almost too many, though I get that’s kind of the point.
The classic two FS errors I’ve seen are MacOS case insensitivity fusing two separate files and Windows reserved chars. Most people build and deploy to Linux so repos are usually sane to that OS. It’s just life though it’s funny to see the shoe on the other foot.
If it's your configuration, it's not a problem with your OS, it's a problem with your configuration. Your problem is specifically that your OS has chosen not to support certain characters in filenames, and you want to write files containing those characters.
That's not a configuration. There is no way to configure Windows to accept files with colons in them. As well say it's a configuration issue if the software hardcodes the assumption of filesystem case-insensitivity.