On 17-01-29 21:04:40, Cameron Simpson wrote: > On 29Jan2017 09:30, J <[email protected]> wrote: > > > and i am still using the env variable because it is AFAIK the new > > standard way > > No, it is not "the new standard way", it is just the standard hack for when > you don't know the exact (fixed) path to an executable. For example, bash > might be in /bin or /usr/local/bin or somewhere else (or, my typical > concern, not present). > > Whereas /bin/sh is _always_ in exactly that place. It is even a POSIX > requirement. So you can always go: > > #!/bin/sh > > because it never moves. > > The "env variable" isn't really any better - it totally relies on the "env" > command being exactly where you say. With /bin/sh you never need that hack. Thanks for clearing that up for me
_______________________________________________ OfflineIMAP-project mailing list: [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/offlineimap-project OfflineIMAP homepages: - https://github.com/OfflineIMAP - http://offlineimap.org
