mysterious bash problem
Thu Jan 15 07:26:00 GMT 1998
On 13-Jan-1998, Earnie Boyd <email@example.com> wrote:
> Ulrich Lauther <firstname.lastname@example.org> writes:
> >Let foo be a valid shell script (starting with a ":" in the first line,
> To execute a script the first non-blank line must begin with
> #! /bin/sh
> where /bin/sh is the path and shell you want to execute.
I think you're missing some history. Using `:' in the first line to
identify a Bourne shell script (as opposed to `#', for a C-shell script)
actually predates the `#!' convention.
If gnu-win32 doesn't support execution of shell scripts starting with
`:', then this is a bug in gnu-win32. It works fine with other Unix
systems, including Linux.
In any case, the form of the error message
> >bash.exe: ./foo: (null)
is clearly a bug.
Fergus Henderson <email@example.com> | "I have always known that the pursuit
WWW: < http://www.cs.mu.oz.au/~fjh > | of excellence is a lethal habit"
PGP: finger firstname.lastname@example.org | -- the last words of T. S. Garp.
For help on using this list (especially unsubscribing), send a message to
"email@example.com" with one line of text: "help".
More information about the Cygwin