DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:reply-to:message-id:to:subject
	:in-reply-to:references:mime-version:content-type
	:content-transfer-encoding; q=dns; s=default; b=YhdiyVyeIwEVN+6S
	TO5PDxnI6vuURCgMSqpBiDzp8HyIKS7ucrV2bLhPEaqNNXUm8pRFS+STBxO6e2CX
	fRfqu70YPUKD54Z1Xp2/usj61pYums+c9gOYRwxL4nSofHAfn2Mstu61cZRQBK9C
	D0J9ggLHI0tMBPElUlN9leiL2Ho=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Thu, 6 Feb 2014 02:07:38 +0400
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: Andrey Repin <cygwin@cygwin.com>
Message-ID: <709102296.20140206020738@mtu-net.ru>
To: Warren Young <warren@etr-usa.com>, cygwin@cygwin.com
Subject: Re: Newbie Questions
In-Reply-To: <52F2AD84.1050008@etr-usa.com>
References: <1898639722.6893470.1391541591920.JavaMail.root@ptd.net> <52F153AE.5080704@gmail.com> <52F28215.5030801@ptd.net> <52F28330.6060101@cygwin.com> <52F2AA5D.4000000@etr-usa.com> <52F2AD84.1050008@etr-usa.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Warren Young!

> On 2/5/2014 14:17, Warren Young wrote:
>>
>> I'd bet there are more Bourne shell scripts in the world with no
>> extension at all than .sh.

> ....That said, if you're wanting to be able to double-click on a shell 
> script icon in Windows and associate that with Cygwin's bash.exe, you 
> *will* need to pick a file name extension, since that's how Windows 
> determines what's in a file.

Not necessarily. Especially not, when using ShellExecute(Ex)?...

> .sh is indeed the standard choice when you must use a file extension for 
> a Bourne shell script, for whatever reason.

> These two features can interact in odd ways.

> Say you have a Perl script, which you have misleadingly named foo.sh. 
>  From a bash shell, you type:

>         $ ./foo.sh

> The Perl script will run as intended, despite the name.

> But if you associate .sh with bash.exe, then double-click that script 
> from Windows Explorer, it won't work right, since bash.exe will try to 
> run it as a shell script.

Have you actually tried that?
Try it, you'll be surprised.

> Perl isn't close enough in syntax to Bourne shell for this to work for
> anything but trivial (or very tricky!) scripts. 

> What you've done here is substitute Windows Explorer for exec(), so you
> don't get the shebang handling built into exec().

Try it yourself... you'll be surprised.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 06.02.2014, <02:02>

Sorry for my terrible english...


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple