The workarounds are ingenious, and yes, you could write a script wrapper to rename the save file after running, but really, the second thing you tried, with the quotation marks, is the right solution and ought to have worked. (Double-quotes would perhaps be more natural, but either single or double should work).
I didn't see a mention in the other thread or here of what "oolite-trunk" is. I suspect it is a script wrapper around the actual oolite binary, and the way it is passing the command-line on to the application is causing problems with the spaces. If so, it should be fixed. If it has something like
That needs to be changed to
That is the correct way to pass on the arguments without having this problem. The $* thing works fine as long as no arguments have spaces in them.
Failing that, there is probably some number of backslashes you could put before the space which would fix it. My first guess would be three:
Code: Select all
oolite-trunk -load /home/robert/oolite-saves/RB\\\ Lock.oolite-save
But it depends on exactly what is going on between your command line and the process that's actually looking at ARGV