env(1) should print program it attempts to exec on error, not argv
cmd - userland programs
If env is passed a command (utility in the manpage) which it is unable to execute, it currently prints unhelpful and misleading error messages like "/usr/bin/env: No such file or directory" for ENOENT. It should be including the pathname that failed.
- Assignee set to Robert Mustacchi
Thanks for volunteering. :)
$ /usr/bin/env foobar
/usr/bin/env: No such file or directory
$ ./usr/bin/env foobar
./usr/bin/env: foobar: No such file or directory
- Status changed from New to Resolved
- % Done changed from 0 to 100
- Tags deleted (
Resolved in 13707:3f41b24ce657.
Also available in: Atom