- you still get the python3 in PATH, not a specific one (sbang aims to use a specific interpreter)
- The -S argument to env is not POSIX: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/e...
- you still get the python3 in PATH, not a specific one (sbang aims to use a specific interpreter)
- The -S argument to env is not POSIX: https://pubs.opengroup.org/onlinepubs/9699919799/utilities/e...
env lets you solve that one too. You can control PATH. From the FreeBSD manpages:
#!/usr/bin/env -S -P/usr/local/bin:/usr/bin perl
And if you lack the -P flag... env controls the environment variables... So, you could extend (or replace) it like so: #!/usr/bin/env PATH=/home/my/loc:${PATH} perl
> The -S argument to env is not POSIXYou're right. POSIX only guarantees the -i flag, and the ability to set variables. It hasn't been modified in the standard since 1991, despite other updates to the standard.
OpenBSD and Busybox only supports the crippled POSIX version. It isn't completely portable.
Versions with -S and are available on Linux, FreeBSD (also has -P), macOS (also has -P).
This is probably obvious but bears repeating since we're on this tangent -- even -S and -P do not prevent the OS from truncating the shebang if it's too long. So env is great for passing multiple args, but it still doesn't let you use really long shebangs (the original point of the thread :)