Date: Wed, 21 Feb 2001 12:18:22 +0200 (IST)
From: Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender: eliz AT is
To: Esa A E Peuha <peuha AT cc DOT helsinki DOT fi>
cc: djgpp AT delorie DOT com
Subject: Re: [malfer AT teleline DOT es: Announce GRX 2.3.4]
In-Reply-To: <86p7l2kpl5g.fsf@sirppi.helsinki.fi>
Message-ID: <Pine.SUN.3.91.1010221121655.18287U-100000@is>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: djgpp AT delorie DOT com
Errors-To: nobody AT delorie DOT com
X-Mailing-List: djgpp AT delorie DOT com
X-Unsubscribes-To: listserv AT delorie DOT com
Precedence: bulk


On 21 Feb 2001, Esa A E Peuha wrote:

> "Eli Zaretskii" <eliz AT is DOT elta DOT co DOT il> writes:
> 
> > This particular problem is hard to fix because it is not in Bash.  On
> > Unix, the first line of a script is examined by the system's kernel,
> > which decides what program should be invoked to run the script.  The
> > confusing error message comes from the kernel which doesn't consider
> > \r a delimiter.
> 
> That is true, but only if you run the script like "./sundry_script".
> The more primitive way, "bash sundry_script", doesn't involve the
> kernel, so it will work as long as Bash can parse the script.

Yes.  But the usual rebuttal you will hear from Bash maintainers is that 
since the simpler and more widely-used case is not up to Bash, it isn't 
worth to fix the other one, either.