How to make --with-shell= work if it runs an executable whose path may contain spaces?

[mooreye]

Scenario: Bash script that runs fzf is in an arbitrary directory and I want that fzf process to use a separate script for its --with-shell= flag that is also in that directory, so that I can just use --preview={} so it runs that script with current selection as argument. However, --with-shell= treats space as argument separator and there seems no way to include a literal space, that may be part of that directory's path (including all other funny characters). The fzf process runs in an arbitrary working directory (from where the user invoked the main script) so using ./preview-script.sh also won't work.

Similar problems would be present if I use --preview=/absolute/path/to/preview-script.sh because --preview= expands different things like {} which may also be part of full path since it's arbitrary.

How do I deal with this?

[junegunn]

However, --with-shell= treats space as argument separator

You can quote it. i.e. --with-shell="/path with spaces/bash"

[junegunn]

Fixed in b59f27e. Thanks for the report!

[mooreye]

So from within Bash, it will be safe to pass executable path with ${path@Q} to fzf?

[junegunn]

Not completely sure what you mean. Could you test it and let me know the results?

[mooreye]

Manual says that --with-shell= is Shell command and flags to start child processes with. and gives $SHELL -c as an example. So space is still a flag separator, but where? As an example, which of the following --with-shell= values are correct? (as literal strings passed to --with-shell=):

bash -c
bash -euo pipefail -c
/opt/foo bar/bash -c
'/opt/foo bar/bash' -c
'/opt/foo bar/bash' -euo pipefail -c
"/opt/foo bar/bash" -c
"/opt/foo bar/bash" -euo pipefail -c
'/path/with/qu"ote/and/sin'\''gle-quote/bash' -c

[junegunn]

Should be quoted or escaped. Take a look at the commit message: b59f27e