5 ms·
Thanks! I don't have much experience with Windows, and the backend is quite closely tied to the OS. Is this on plain Windows, or on WSL?
by pmeunier 5y ago
Thanks! I don't have much experience with Windows, and the backend is quite closely tied to the OS.
Is this on plain Windows, or on WSL?
- maccard 5y agoNo 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)
- aidenn0 5y agoFWIW, 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)
- pmeunier 5y agoThanks, 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.
- aidenn0 5y agoRight, but the original comment in this thread was with wildcards not expanding on windows.
- maccard 5y agogit still expands wildcards even if you dont run it under msys. git add \*.cpp works just fine in powershell and cmd.exe
- aidenn0 5y agoThat would confuse the heck out of me; what if I wanted to add a file named "*.cpp"?
- maccard 5y agoI 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.