Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin AT sources DOT redhat DOT com
Message-ID: <E1B42CFD544FD31193EE0000E87C5CE799B4A4@mailserver2.mqsoftware.com>
From: Glen Coakley <gcoakley AT mqsoftware DOT com>
To: cygwin AT cygwin DOT com
Subject: RE: Batch files
Date: Fri, 30 Mar 2001 17:14:54 -0600
MIME-Version: 1.0
X-Mailer: Internet Mail Service (5.5.2653.19)
Content-Type: text/plain;
	charset="iso-8859-1"


You'll have to educate me on PATHEXT.

The windows command 'start' will invoke the proper program based upon a
files extension. Unfortunately, start doesn't work under cygwin. 

The magic I was referring to doing was in a normal Unix environment (of
which cygwin would qualify).

________________________________
Glen Coakley, Sr. Software Engineer
MQSoftware Inc., (763) 543-4845
Have you ever wonder what happens when you run "rm -rf / " but been afraid
to try it?


> -----Original Message-----
> From: Mark Paulus [mailto:commpg AT yahoo DOT com]
> Sent: Friday, March 30, 2001 4:44 PM
> To: cygwin AT cygwin DOT com
> Subject: RE: Batch files
> 
> 
> start already does the invoking of the proper program based upon
> it's windows file association (do a 'start "window title" file.ext).
> Also, doesn't WinNT provide support for defining executable 
> extensions via the PATHEXT environment variable??  Can't that
> be built upon?
> 
> 
> On Fri, 30 Mar 2001 15:44:25 -0600, Glen Coakley wrote:
> 
> >
> >cmd will grok it because it will look for a command called 
> #!, which step
> >one instructs you to create. A note on step #2. You will 
> want #!.exe in the
> >path that is set in Windows and in cgywin's bash but, it 
> only has to be in
> >the path once. So, if you have added cygwin/bin to your 
> normal windows path,
> >you shouldn't need to put it in windows/system32.
> >
> >While we are on the topic of paths, you would really only 
> need to add 
> >	#! cmd /c
> >as the first line of the batch file, since windows/system32 
> is always in the
> >windows path and cygwin builds it path on that.
> >
> >I think I speak for many though, when I say that it would be 
> nice to have
> >more intuitive support, such as it just working. I have many 
> batch files
> >that I would rather not convert. Perhaps cygwin could 
> recognize a first line
> >of "@echo off" as a DOS batch file and run the interpreter. 
> Even better, and
> >I have wondered for a long time why I haven't seen this yet, 
> programs could
> >be invoked on any file based on the results of that file's 
> magic (see: man
> >file). 
> >
> >________________________________
> >Glen Coakley, Sr. Software Engineer
> >MQSoftware Inc., (763) 543-4845
> >Have you ever wonder what happens when you run "rm -rf / " 
> but been afraid
> >to try it?

--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple