For example, if Run on Save is called on a file located at /home/user/Project Files/file.txt and "command" is set to normalize ${file} Run on Save executes:
$ normalize /home/user/Project Files/file.txt
Which is two parameters, rather than one.
The correct behavior would be quote and escape substituted variables, so Run on Save would correctly execute:
$ normalize "/home/user/Project Files/file.txt"
With this command normalize would be provided a single correct path rather than two incorrect paths.
It is currently possible to workaround this bug somewhat by setting the command to normalize "${file}", but this will not work reliably on Unix platforms (and WSL) where filenames may contain quotes.
For example, if Run on Save is called on a file located at
/home/user/Project Files/file.txt
and "command" is set tonormalize ${file}
Run on Save executes:Which is two parameters, rather than one.
The correct behavior would be quote and escape substituted variables, so Run on Save would correctly execute:
With this command
normalize
would be provided a single correct path rather than two incorrect paths.It is currently possible to workaround this bug somewhat by setting the command to
normalize "${file}"
, but this will not work reliably on Unix platforms (and WSL) where filenames may contain quotes.