Date:	Thu, 16 Nov 2000 11:51:07 +0200 (IST)
From:	Eli Zaretskii <eliz AT is DOT elta DOT co DOT il>
X-Sender:	eliz AT is
To:	Todd Beckering <ToddBeckering AT worldnet DOT att DOT net>
cc:	djgpp AT delorie DOT com
Subject:	Re: bash command file and windows pifs
In-Reply-To:	<ZTAQ5.894$BL.53846@bgtnsc05-news.ops.worldnet.att.net>
Message-ID:	<Pine.SUN.3.91.1001116115050.5962A-100000@is>
MIME-Version:	1.0
Reply-To:	djgpp AT delorie DOT com
Errors-To:	nobody AT delorie DOT com
X-Mailing-List:	djgpp AT delorie DOT com
X-Unsubscribes-To:	listserv AT delorie DOT com

On Wed, 15 Nov 2000, Todd Beckering wrote:

> I'm trying to associate a bash command file with a windows file type, and am
> having a problem.  I set up the associating pif command line:
> bash_path my_command_file_path %1
> but when I double click on a file, bash executes the file I click on (%1),
> instead of my command file.  It looks like windows is executing:
> bash_path %1

Does it help to change the properties to invoke Bash like this:

     bash_path -c 'my_command_file_path %1'

- Raw text -