Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <37E0CCF2.2566@bigfoot.com>
Date: Thu, 16 Sep 1999 11:56:50 +0100
From: Keith Starsmeare <kxs@bigfoot.com>
MIME-Version: 1.0
To: cygwin@sourceware.cygnus.com
Subject: Scripts starting with colon
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Why do scripts have to start with #! to be recognised as executable?
Scripts can start with just : to mean that it's either a bourne shell
script or a bash script depending on what shell you execute the script
from.

Was this an intentional ommission?

There are scripts in the cygwin installation that start with a colon,
for example gzexe, but the next line is #!/bin/sh and these files are
recognised as being executable.

It seems to be the case with cygwin that a file (with UNIX style end of
line characters) that starts with

:
#!

is the equivalent of a file that starts

#!/bin/sh

how confusing.

Could this matter be fixed (or added to a list of bugs - possibly
mentioned in the FAQ), or is it not considered a bug?

Keith

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com