Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: kulack AT us DOT ibm DOT com
X-Lotus-FromDomain: IBMUS
To: cygwin AT sourceware DOT cygnus DOT com
Message-ID: <8525689C.006BCCE9.00@D51MTA08.pok.ibm.com>
Date: Wed, 8 Mar 2000 13:37:21 -0600
Subject: Re: Executing .bat files from bash
Mime-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Disposition: inline

On 03/07/2000 at 01:09:57 PM, Bob McGowan <rmcgowan AT veritas DOT com> wrote:
I'll even patch bash if I have to.

The alias model works well, but if you have more dynamic batch files,
create a shell script of the name <file> for batch file <file>.bat.
The shell script does <file>.bat.
Done.

You can easily create a tool to automate this too. (left to the reader).
- For each component of the path variable.
- look for files named *.bat in that directory.
- Create a file of the same name without the extension in that directory.
- chmod to make it executable.




--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com