On Fri, 02 Nov 2007 13:57:59 +0100, Tim Tassonis timtas@cubic.ch wrote:
Hi Nick, Enrico
At the moment the command line is just split up on every space, so filenames with spaces won't work (although paths will). The quotes become part of the filename. A workaround is to remove the quotes from the compile & build commands for the filetype you want to use. But of course the code could/should be improved to support quotes.
Well, I can well live with that restriction. I won't repeat on this list how I call people putting blanks in source file names...
I do ;-), spaces in filenames(as well as other non-Ascii characters) are one of the worst improvements ever.
Btw, if you are testing the code, I just committed some exit code detection for Windows. I have no idea whether it works reliable but a few tests seemed to be good.
Regards, Enrico