I wasn’t sure what was happening when I noticed this over a year ago. I placed the same script in two different folders. It worked OK from the first and returned an error msg from the second, which you can see below.
The only difference between the two folder paths is that the first didn’t contain any empty spaces (/Users/USER/compile), whereas the second did (/Users/USER/My Folder/compile).
I tried:
escaping using a backlash (/Users/USER/My\ Folder/compile);
placing it between single ('/Users/USER/My Folder/compile');
placing it between double quotes ("/Users/USER/My Folder/compile")
But I still got either the former error or a new one.
Perhaps someone could confirm the error or enlighten me?
Using macOS 13.3.1 (a) and Scrivener 3.3.1 (15588).
I’m having no difficulties escaping the space, which would be the expected way to call upon an executable on the command-line. This is using macOS 13.3.1 as well. It makes all kinds of sense that it wouldn’t work at all without handling the space though, because you are sending this to the system: /Users/USER/My and everything after that is considered arguments.
I would double-check that the path you have given actually works in the shell. Maybe the script doesn’t have the executable flag on it or something.
I have not seen any reports of that, or seen it myself (though I rarely expand/collapse things in the binder). You could try a reinstall if you haven’t already, to flush out any UI file issues that may be causing it.
Otherwise it could be icon related, given it looks like you use custom ones extensively.
