From: jeffers AT redrose DOT net (David Jeffers) Subject: Re: what did I miss? #!.... doesn't work in bash 31 Oct 1996 17:43:34 -0800 Sender: daemon AT cygnus DOT com Approved: cygnus DOT gnu-win32 AT cygnus DOT com Distribution: cygnus Message-ID: <199610311912.LAA04347.cygnus.gnu-win32@cygnus.com> References: Original-To: "Bret A. Schuhmacher" Original-Cc: gnu-win32 AT cygnus DOT com In-Reply-To: Original-Sender: owner-gnu-win32 AT cygnus DOT com >>>>> "Bret" == Bret A Schuhmacher writes: The bang "#!/usr/sh" line isn't really necessary for shell scripts using Cygnus bash. I remember reading about a "magic cookie" but all my scripts work with it or without it on Win 95. NT Perl uses a BAT file to build an executable so again it isn't necessary. For instance: #!/bin/sh <---not necessary? awk ' { print $1 } ' works fine since awk is in my PATH. I think the "#!/bin/sh" line in Cygnus simply means "this is an executable" since I don't even have to chmod +x after I write the scripts like I do in Linux... Bret> OK, what part of the manual did I miss? I can't get scripts Bret> with #!/bin/tclsh or #!/bin/perl or whatever to work. Is Bret> this a configuration thing? Is this a path thing (/bin is Bret> in the path, as is .). Bret> I downloaded the bash source code and found some code in Bret> execute_cmd.c that would do the trick... but I can't find Bret> the bash code that was ported to Win/NT. I can't get my Bret> compiled bash to tell me what version it is, so I can't tell Bret> if the source version I found (1.14.6) is newer or older. Bret> Not looking for a handout, just a pointer :-). How have you Bret> handled this in the past (besides executing /bin/tclsh Bret>