Is this not what you are looking for? From the man page of env(1)
> The -S option allows specifing [sic] multiple parameters in a script.
> [...]
> Without the '-S' parameter the script will likely fail with:
> . . . /usr/bin/env: 'perl -w -T': No such file or directory
I actually ran into this problem last week and just used the absolute path with an argument (/usr/bin/python3 -u) instead of passing an argument to env, and I added a TODO comment to figure out how to do this better. Now you made me find the right way :)
It was funny to notice my mental knee-jerk reaction of "ought to be enough for anyone" (referring to 640K RAM). I've never used args with env until last week in the first place and even then it was a (mental) debate of solving it in code (wrapping print() in a function that also flushes stdout) or adding the argument instead, so I guess that's why that was my initial thought. But of course that doesn't mean there can't be legitimate uses of long argument lists. Java code comes to mind (although I do question the sanity of many things Java).
> The -S option allows specifing [sic] multiple parameters in a script.
> [...]
> Without the '-S' parameter the script will likely fail with:
> . . . /usr/bin/env: 'perl -w -T': No such file or directory
I actually ran into this problem last week and just used the absolute path with an argument (/usr/bin/python3 -u) instead of passing an argument to env, and I added a TODO comment to figure out how to do this better. Now you made me find the right way :)