Afaict that's an issue with your operating system, not with tangled's git implementation. You're trying to check out a file with a colon in its name, and Windows can't handle that because of DOS baggage. If you mirrored that to GitHub or wherever and then tried to clone, you'd probably get the same error again.

Try cloning on WSL, in the VM's filesystem, and let us all know how that goes.

▲

eterm 2 hours ago | parent [-]

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.

	▲	ethin 2 hours ago \| parent [-]
		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.