Custom configuration file path can't contain spaces.

[ncklboy]

When setting up a custom configuration for either an unsupported application or file, if there are any spaces in the file name the file fails to be synced. I have verified that there is no current workaround for this by both escaping and quoting the file path. Input parsing does not seem to expect or except the existence of spaces.