New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Spaces in -fs_userpath are not allowed #122
Comments
It's actually possible to do this already, quoted strings are supported out of the box by ./opensoldatserver -fs_userpath "\"~/temp/soldat with space\"" -log_level 1 But of course this is a pretty bad documentation problem, which should be solved ASAP. Anyone is welcome to take a stab at adding a few pages to the wiki, and I'll try to get around to adding some documentation myself soon. |
Oh, I see. I didn't think of trying that! It's not exactly pretty though. That gave me an idea. The same could be achieved by changing shared/Command.pas:491 from this:
to this:
I just tried that out and it this allows me tu run as:
Now escaped spaces work as expected and all the other command-line arguments remain functional as well. What do you think of doing it like that? You wouldn't have to rely on people reading documentation. |
Wayyy better thanks. |
When trying to set
-fs_userpath
to a path with spaces, only the part before the space is being considered. For example, when running opensoldat like this:The reason is that at some point in shared/Command.pas there is code like this;
So even though the argument is correctly supplied on the command line, the above code will just split it out anyway.
I'll open a PR for this one. I was able to solve this one locally (although it's affected by issue #121).
The text was updated successfully, but these errors were encountered: