Timeline for Why is it better to use "#!/usr/bin/env NAME" instead of "#!/path/to/NAME" as my shebang?
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 26, 2023 at 12:01 | comment | added | Anders | Many development environments install interpreters of different versions in the users HOME. And one choose which to use by prepending the PATH with the selected version. Look at python and ocaml for examples of this, there are other examples. | |
| Jul 29, 2020 at 11:10 | comment | added | DrHyde | Yeah, it also won't work if perl isn't in the path, or on an Amiga, or ... If you're using something weird like that then you're going to have to do some work yourself. | |
| Jul 28, 2020 at 16:17 | comment | added | LLlAMnYP | What if sh is not in /bin? True story for google distroless containers. | |
| Feb 24, 2020 at 21:59 | comment | added | DrHyde | It is, but it's a bletcherous kludge that works. It's a blethcherous kludge that exists because less kludgey solutions don't work. | |
| Feb 23, 2020 at 4:07 | comment | added | vonbrand | @AmokHuginnsson it is a bletcherous kludge. | |
| S Aug 11, 2018 at 16:44 | history | suggested | Maximilian Heinzler | CC BY-SA 4.0 | Quote the script name in case it includes spaces |
| Aug 11, 2018 at 15:47 | review | Suggested edits | |||
| S Aug 11, 2018 at 16:44 | |||||
| May 25, 2015 at 21:23 | comment | added | AmokHuginnsson | Exactly the anser I was looking for: how to write porable "shebang" for perl script that will allow additional aruments passed to perl (last line in your example accepts additional aruments). | |
| May 2, 2013 at 15:38 | history | edited | Anthon | CC BY-SA 3.0 | code formatting of env call |
| May 2, 2013 at 15:37 | review | First posts | |||
| May 2, 2013 at 15:38 | |||||
| May 2, 2013 at 15:19 | history | answered | DrHyde | CC BY-SA 3.0 |