Closed mr-pennyworth closed 3 years ago
Thank you! This was an unexpected bug, as I always care to test for spaces and weird characters, though them being in the path of the Workflow explains the miss.
However, I prefer a shorter fix which doesn’t require shellwords
. The crux of the issue is that if the code you give Open3
or system
is a single item, they’ll need to invoke a shell to interpret it, thus requiring the escaping (because otherwise how would it know where you meant to split things). But if it’s more than one item, they can invoke the utility directly.
The solution, then, is to never invoke system
and friends with a single argument. --
usually does the trick, as in most tools it means “stop interpreting command flags starting here”.
But thank you again for the PR and bringing this to my attention!
Fixes #127