Hi again, Sorry for not answering your question in my previous post... I'm a bit sleepy (it's about 1am my time).
Try double quotes. Just tested with no errors: > fossil add "new file.txt" ADDED new file.txt > fossil chan ADDED new file.txt > fossil commit -m "new file added..." New_Version: 4023b409f054b270412af3302e79ad20a67de5c0 However, I think you usually don't need to specify file names by hand. It's enough to issue 'fossil add *' or 'fossil add a_dir' or 'fossil add "a_dir\b dir"' and fossil will do the job you. Jacek 2012/6/11 Mike Meyer <[email protected]>: > 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? > > 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 _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
