Path: csiph.com!goblin2!goblin1!goblin.stu.neva.ru!usenet.stanford.edu!not-for-mail
From: Stephane Chazelas <stephane.chazelas@gmail.com>
Newsgroups: gnu.bash.bug
Subject: Re: [PATCH] docs: More hints on #! parsing
Date: Wed, 25 Sep 2019 22:36:41 +0100
Lines: 21
Approved: bug-bash@gnu.org
Message-ID: <mailman.1109.1569447471.2190.bug-bash@gnu.org>
References: <20190925203324.16276-1-eblake@redhat.com> <20190925213641.2al2rhiuh2plrffh@chaz.gmail.com>
NNTP-Posting-Host: lists.gnu.org
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: bug-bash@gnu.org
To: Eric Blake <eblake@redhat.com>
Envelope-to: bug-bash@gnu.org
Content-Disposition: inline
In-Reply-To: <20190925203324.16276-1-eblake@redhat.com>
User-Agent: NeoMutt/20171215
Precedence: list
Xref: csiph.com gnu.bash.bug:15432

2019-09-25 15:33:24 -0500, Eric Blake:
[...]
>  Bash scripts often begin with @code{#! /bin/bash} (assuming that
>  Bash has been installed in @file{/bin}), since this ensures that
>  Bash will be used to interpret the script, even if it is executed
> -under another shell.
> +under another shell.  Another common practice is the use of
> +@code{#!/bin/env bash} to find the first instance of bash on @env{PATH}.
[...]

env is more commonly found in /usr/bin. There's no env in /bin
on Ubuntu or FreeBSD for instance.

Using "#! /bin/bash -" is also good practice (so your script
still works when its path starts with - or +, see also
https://unix.stackexchange.com/questions/351729/why-the-in-the-bin-sh-shebang
for more historical context).

-- 
Stephane