Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com From: JROZYCKI AT ebmail DOT gdeb DOT com X-Lotus-FromDomain: GDYN To: Troy Noble cc: cygwin AT cygwin DOT com Message-ID: <85256B05.006C4612.00@groton5.notes.gdeb.com> Date: Thu, 15 Nov 2001 14:44:52 -0500 Subject: RE: script-name won't execute but script-name.py will Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline Troy, The interpreter line is already specfied on the first line of all my scripts. So something else must be the culprit. Thanks, Jeff Troy Noble on 11/15/2001 02:35:01 PM To: Jeff Rozycki/EB/GDYN AT GDYN, cygwin AT cygwin DOT com cc: Subject: RE: script-name won't execute but script-name.py will Try adding #!/usr/bin/python as the first line of your scripts (substitute the appropriate path/filename depending on whether it's python, perl, bash, etc. and where the filename lives /usr/bin, /usr/local/bin, etc.) Or if you're sure it's always going to be on your PATH you can use #!env python Then the filename extension doesn't matter. I've even had luck invoking native win32 script interpreters, such as ActiveState Perl this way such as: #!/cygdrive/c/Perl/bin/perl Hey, this stuff really does work like Unix! Troy -----Original Message----- From: JROZYCKI AT ebmail DOT gdeb DOT com [mailto:JROZYCKI AT ebmail DOT gdeb DOT com] Sent: Thursday, November 15, 2001 12:13 PM To: cygwin AT cygwin DOT com Subject: script-name won't execute but script-name.py will -snip ... you're welcome Earnie -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Bug reporting: http://cygwin.com/bugs.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/