On Mon, Jun 11, 2012 at 6:36 PM, Mike Meyer <[email protected]> wrote: > My boss just sent me mail that said, and I quote: > > Fossil sucks and is actually not compatible with Windows > > I'm pretty sure I've seen people here who use it no Windows, and > there's a Windows distribution, which makes me think he's wrong. > > His problem is that he has lots of spaces in his directory and file > names, and we (Windows is a third-line gaming platform for me, but I > try...) couldn't figure out how to get such passed to fossil as file > names, instead of broken up by command.com or whatever does that job > these days. Quoting again: > > If I try adding parentheses or quotes then the ignorant > application bombs out. > > So, anyone got advice on this? Maybe a GUI that works with the fossil > Windows binary from fossil.org? >
I think the windows command-line shell insists on double-quotes around arguments that contain spaces. Unix will accept single-quotes and escaped spaces, but windows wants double-quotes. At least that has been my experience. On the other hand, there might be bugs in Fossil related to spaces in file and directory names. I never allow spaces in directory and filenames myself, so the ability to handle spaces in names is not something that gets heavily exercised. > > Thanks, > <mike > -- > Mike Meyer <[email protected]> http://www.mired.org/ > Independent Software developer/SCM consultant, email for more information. > > O< ascii ribbon campaign - stop html mail - www.asciiribbon.org > _______________________________________________ > fossil-users mailing list > [email protected] > http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users > -- D. Richard Hipp [email protected]
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
