To: djgpp AT delorie DOT com
Subject: Re: [malfer AT teleline DOT es: Announce GRX 2.3.4]
References: <Pine DOT SUN DOT 3 DOT 91 DOT 1010215161508 DOT 29378B-100000 AT is> <96gvlr$2h9$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <96j0vj$dfb$1 AT nets3 DOT rz DOT RWTH-Aachen DOT DE> <fqcr8t4qnpvvtrf0ul9v3bvjuhil0i3pui AT 4ax DOT com> <1438-Sat17Feb2001103307+0200-eliz AT is DOT elta DOT co DOT il>
From: Esa A E Peuha <peuha AT cc DOT helsinki DOT fi>
Date: 21 Feb 2001 09:09:31 +0200
In-Reply-To: "Eli Zaretskii"'s message of "Sat, 17 Feb 2001 10:33:07 +0200"
Message-ID: <86p7l2kpl5g.fsf@sirppi.helsinki.fi>
Lines: 16
X-Mailer: Gnus v5.6.43/Emacs 19.34
Reply-To: djgpp AT delorie DOT com

"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.

-- 
Esa Peuha
student of mathematics at the University of Helsinki
http://www.helsinki.fi/~peuha/