On Dec 17 19:41, Andy Koppe wrote:
> 2010/12/17 Vincent Côté-Roy:
> > I'm sorry, I wasn't very clear: xyz.bat or xyz.cmd do indeed execute
> > as before. My problem is that when I type xyz (i.e. without the
> > extension) it won't find xyz.bat or xyz.cmd, as it did before
> > upgrading.
>
> It di
2010/12/17 Vincent Côté-Roy:
> I'm sorry, I wasn't very clear: xyz.bat or xyz.cmd do indeed execute
> as before. My problem is that when I type xyz (i.e. without the
> extension) it won't find xyz.bat or xyz.cmd, as it did before
> upgrading.
It did not do that. Not on the Cygwin 1.5.25 install h
Hi Larry,
I'm sorry, I wasn't very clear: xyz.bat or xyz.cmd do indeed execute
as before. My problem is that when I type xyz (i.e. without the
extension) it won't find xyz.bat or xyz.cmd, as it did before
upgrading.
2010/12/17 Larry Hall (Cygwin) :
> On 12/17/2010 12:54 PM, Vincent Côté-Roy
On 12/17/2010 12:54 PM, Vincent Côté-Roy wrote:
Hi,
I've just upgraded to 1.7 (from 1.5) and ever since I did, .bat and
.cmd files are no longer automagically executed when I invoke them
without their extension: i.e., it used to be that invoking xyz in bash
would execute xyz.bat or xyz.cmd if it
Hi,
I've just upgraded to 1.7 (from 1.5) and ever since I did, .bat and
.cmd files are no longer automagically executed when I invoke them
without their extension: i.e., it used to be that invoking xyz in bash
would execute xyz.bat or xyz.cmd if it happened to be in my path.
Is this a new feature
5 matches
Mail list logo