3 ms·
Probably the natural consequence of shebang limitations and the "chicken and egg problem" of env(1) that isn't always in /usr/bin. If only we could write #!sh
by BoingBoomTschak 2y ago
Probably the natural consequence of shebang limitations and the "chicken and egg problem" of env(1) that isn't always in /usr/bin.
If only we could write #!sh to do a PATH lookup...
Thanks for finding the exact POSIX section describing its own failings!
On Gentoo (with the recent merged-usr profile), getconf PATH returns "/bin:/usr/bin", heh.