Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sources DOT redhat DOT com Delivered-To: mailing list cygwin AT sources DOT redhat DOT com Message-ID: <2C08D4EECBDED41184BB00D0B747334202FB437F@exchanger.cacheflow.com> From: "Karr, David" To: "'Cygwin Users'" Subject: RE: Status on issue with PATH ignoring scripts with same name as exesin 1.3.1? Date: Tue, 8 May 2001 09:19:19 -0700 MIME-Version: 1.0 X-Mailer: Internet Mail Service (5.5.2653.19) Content-Type: text/plain; charset="iso-8859-1" I've verified that the latest Bash version (2.05.0(5)-release (i686-pc-cygwin)) with the 1.3.1 cygwin1.dll gives me back the old working behavior. -----Original Message----- From: Karr, David [mailto:david DOT karr AT cacheflow DOT com] Sent: Tuesday, May 08, 2001 8:11 AM To: 'Cygwin Users' Subject: RE: Status on issue with PATH ignoring scripts with same name as exesin 1.3.1? Why would anyone depend on this working? Well, maybe because it seems logical, and the way it's working now isn't logical, and it was working before. In another note, you suggest a workaround of renaming my script to add a period to the end. The "mv" command doesn't let me do this, so I can't even test whether that would work. I still think it is more logical to have it work the way it used to work. Is it known whether Corinna's last fix to Bash will resolve this, and if I rerun "setup" now, will I get that fix? Your comment indicating this is "not a SBCIH" is unclear to me. -----Original Message----- From: Earnie Boyd [mailto:earnie_boyd AT yahoo DOT com] Sent: Tuesday, May 08, 2001 5:50 AM To: Karr, David Cc: 'cygwin AT cygwin DOT com' Subject: Re: Status on issue with PATH ignoring scripts with same name as exesin 1.3.1? "Karr, David" wrote: > > I haven't reexamined this issue in several days. I have "wrapper" scripts > with the same name as exes later in the path. This worked fine in 1.1.8, > but now that I'm trying to use 1.3.1, it doesn't work anymore. When the > shell does a PATH search, it ignores the script and just uses the exe. I'm > just looking for some information on this. I can downgrade my cygwin1.dll > to 1.1.8 for now. > Why would anyone depend on this working? It is simply an implementation specific issue. I suggest instead of downgrading that you rename your scripts. The simple reason is that Cygwin stat's foo for foo.exe and if foo.exe is what is being executed by the shell then IMNSHO it's correct the way it is now and broken before. Earnie. _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple -- Want to unsubscribe from this list? Check out: http://cygwin.com/ml/#unsubscribe-simple