Jeff King <p...@peff.net> writes: > This is about finding "/usr/bin/foo", realizing it cannot be exec'd > because it lacks a shebang line, and then pretending that it did have > "#!/bin/sh". IOW, maintaining compatibility with execvp(). > > So the command itself isn't a shell command, but it may execute a shell > script. If that makes sense.
Ah, OK. Thanks.
