From:	ian AT cygnus DOT com (Ian Lance Taylor)
Subject:	Re: cygwinb19.1.dll sh.exe still won't run shell scripts from path + workaround
7 Apr 1998 18:35:15 -0700 :
Message-ID:	<199804080106.VAA22920.cygnus.cygwin32.developers@subrogation.cygnus.com>
References:	<199804080049 DOT RAA28358 AT skaro DOT cygnus DOT com>
To:	noer AT cygnus DOT com
Cc:	jeffdb AT netzone DOT com, cygwin32-developers AT cygnus DOT com

   From: Geoffrey Noer <noer AT cygnus DOT com>
   Date: Tue, 7 Apr 1998 17:49:34 -0700 (PDT)

   I committed the following patch of yours.  Here's the ChangeLog entry
   I added for it.  Please send me any corrections if it's inaccurate:

   Tue Apr  7 17:18:05 1998  Geoffrey Noer  <noer AT cygnus DOT com>

	   patch from Mikey (jeffdb AT netzone DOT com):
	   * fhandler.cc (fhandler_disk_file::open): under Win95, set
	   S_IXOTH|S_IXGRP|S_IXGRP if the first two bytes of a file contain
	   a '#!'.
	   (fhandler_disk_file::check_execable_p): consider shell scripts
	   execable

   > @@ -1255,9 +1274,9 @@
   >  
   >    if (strcasecmp (".bat", ch) == 0
   >        || strcasecmp (".exe", ch) == 0
   > -      || strcasecmp (".com", ch) == 0)
   > +      || strcasecmp (".com", ch) == 0
   > +      || strcasecmp (".shc", ch) == 0) /* file associate sh -c == ShellScript */
   >      return 1;
   > -
   >    return 0;
   >  }

The `.shc' extension is not very Unix-like.  On Unix, when shell
scripts have an extension, is almost always `.sh'.  I've never seen
`.shc' myself.

Ian

- Raw text -