FWIW, git on windows ships with a (originally msys based) posix environment so that it can have only a single frontend as well (unlike unix shells, the windows command shell does not do wildcard expansion)

Thanks, but our problem is different, the datastructure on which all of this is based is memory-mapped, and does need some filesystem and OS cooperation to work well.

I haven't tested Pijul on Windows much, and I know that at least at some point it didn't work on WSL.

Right, but the original comment in this thread was with wildcards not expanding on windows.

git still expands wildcards even if you dont run it under msys.

    git add \*.cpp  

works just fine in powershell and cmd.exe

That would confuse the heck out of me; what if I wanted to add a file named "*.cpp"?

I think you're going to open a world of hurt by doing that. The windows command tools don't really like .cpp, or a.cpp for files. If you _do_ have a file called .cpp and another called a.cpp in the same directory, explorer will display the asterisk as a missing character. calling `del .cpp` will delete both files too.

No problem. This is on plain windows, not on wsl. I have a Mac that I can try it on again later (although it will have to be a much smaller repository heh)