News for hackers. Stuff that matters.
Re:Shell Style Guide by jolmg on Tuesday May 15, 2018 @03:36PM (#17077087)
Do you know why they stopped?
Re:Shell Style Guide by JdeBP on Tuesday May 15, 2018 @04:17PM (#17077510)
Re:Shell Style Guide by jolmg on Tuesday May 15, 2018 @04:58PM (#17077809)
So they did it for compatibility. In the end, it seems better to take everything as 1 argument instead of simply splitting on spaces, without having support for quoting and escaping. That way you can have arbitrary code with spaces in the shebang if that's ever a good idea.
Re:Shell Style Guide by jessaustin on Tuesday May 15, 2018 @07:13PM (#17078719)
It is probably silly to dream that kernels will change their behavior, if FreeBSD had to revert such an improvement. However as you describe env is actually downstream of the kernel, so if it were improved we could envision shebangs like the following:

  #!/usr/bin/env --new-env-behavior-parse-all-args=bash -e
Some people might prefer a less verbose flag, but perhaps making it extra-yucky would improve adoption?