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=D2lFUudVkg6iOmDM
	GOAW9uLptFx7A7vwLChUqB4Gkm1sSo7DoZqFGzLEQMbEuG3Do/42BeDPDuzuxJNE
	oYzd6vHxf23ykeeSNRjRdN+QYGddP/e3K8/SWyMlUuSSrD/JiqVPSQHR4lwfIIEg
	rsLUG752iLxheIgAEuA7t/aDD8Q=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Tue, 11 Nov 2014 22:55:47 +0300
From: Andrey Repin <anrdaemon@yandex.ru>
Reply-To: cygwin@cygwin.com
Message-ID: <65830765.20141111225547@yandex.ru>
To: "Nellis, Kenneth" <Kenneth.Nellis@xerox.com>, cygwin@cygwin.com
Subject: Re: how to embed shell script within a .BAT file
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A702E839DB4@USA7109MB022.na.xerox.net>
References: <87bnoforlc.fsf@Rainer.invalid> <0D835E9B9CD07F40A48423F80D3B5A702E839DB4@USA7109MB022.na.xerox.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Greetings, Nellis, Kenneth!

>> From: Achim Gratz
>> 
>> Nellis, Kenneth writes:
>> > Jeremy's solution is closest to what I was looking for; however I need
>> > it to work from a networked, non-drive-mapped folder.
>> > (CMD.EXE doesn't like UNC paths.) I hadn't realized that I could pipe
>> > a script into bash.
>> 
>> The solution to the UNC path problem is to put something
>> 
>> PUSHD %~dp0
>> 
>> near the beginning of the script.  That is if you really want to have .bat
>> files and click on them in Explorer.  Associating the shell scripts
>> properly so that Explorer will hand them to Cygwin sounds like a better
>> solution to me.

> BTW, works great! Here's the completed .BAT file preface with added error
> handling so the CMD window doesn't auto-close if the bash code exits with
> an error.

> @echo off
> set PATH=C:\cygwin64\bin;%PATH%
> PUSHD %~dp0

PUSHD "%~dp0"

But be aware, that you will lose the ability to run such script from different
CWD.

> type %0 | sed "0,/^---BASH SCRIPT FOLLOWS---/ d; s/\r*$//" | bash

sed "0,/^---BASH SCRIPT FOLLOWS---/ d; s/\r*$//" < "%~f0" | bash

> if errorlevel 1 pause
> exit

That's nice for desktop application.
But

EXIT %ERRORLEVEL%

would be more useful in general.

And keep in mind: not everything can be run that way, unfortunately.
Only interpreters accepting command stream from STDIN (such as bash).
And you will lose the ability to pipe data to such script yourself.

> ---BASH SCRIPT FOLLOWS---
> ...

> I'll pursue associating a shell script with a file type
> when I have more time.

On a slightly unrelated note, please avoid naming your scripts ".bat", when
you are using extended CMD features. Not every .bat file interpreter supports
a full range of bugs in CMD.


--
WBR,
Andrey Repin (anrdaemon@yandex.ru) 11.11.2014, <22:35>

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