Following change fixes it for met with MinGW 32 bit on windows 7. $ fossil diff src/main.c argc in wmain 3 --- src/main.c +++ src/main.c @@ -522,11 +522,13 @@ */ #if defined(_WIN32) && !defined(BROKEN_MINGW_CMDLINE) int _dowildcard = -1; /* This turns on command-line globbing in MinGW-w64 */ int wmain(int argc, wchar_t **argv) #else +int _CRT_glob = 0; int main(int argc, char **argv) + #endif { const char *zCmdName = "unknown"; int idx; int rc;
I did not test this with the 64bit version of MinGW. Using an unquoted * in this case still works as expected. Mark On Wed, Aug 21, 2013 at 2:42 PM, Mark Janssen <mpc.jans...@gmail.com> wrote: > It's a problem with the way MinGW parses and passes the command line. When > main is called in fossil, the arguments are already expanded. As for the > fix, I am not sure yet. > > > > On Wed, Aug 21, 2013 at 2:36 PM, Stephan Beal <sgb...@googlemail.com>wrote: > >> >> On Wed, Aug 21, 2013 at 2:31 PM, <fossilscm....@xoxy.net> wrote: >> >>> @ >>> Stephan Beal: So fossil is refusing to eat it's own "dog food" - or >>> rather one of its more unique assets: The integrated wiki and ticket >>> system? :-) >>> >> >> >> This problem is Windows-specific. In every Unix shell "*.css", '*.css" >> will be equivalent (they arrive in the app _without_ the quotes). Using >> *.css MIGHT be equivalent: most shells will not expand the wildcard unless >> there is a match, and if there is no match then they leave it intact (bash >> has a configuration option to change this and replace a non-matching >> wildcard with an empty string). >> >> The main difference is that in Unix the shell does a surprising amount of >> pre-processing of the CLI args before passing them on the app, meaning that >> all apps get a consistent view of CLI args. Windows, OTOH leaves the >> developer to do it all himself. >> >> The dogfood here is without a doubt the Windows "shell". >> >> >>> But since I must accept the culture of the place I'm visiting, perhaps >>> you can help out a novice mailman list fellow: Is there any way to only >>> receive emails from threads I am participating in? >>> >> >> i haven't used Windows (outside of customer sites and an occasional game >> of Empire at War) since last millennium - i can't suggest much of anything >> in that regard except maybe to find something more... well, "more." >> >> :) >> >> >> -- >> ----- stephan beal >> http://wanderinghorse.net/home/stephan/ >> http://gplus.to/sgbeal >> >> _______________________________________________ >> fossil-users mailing list >> fossil-users@lists.fossil-scm.org >> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users >> >> >
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users