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 X-Apparently-From: Message-ID: <3AF7EB79.1A180273@yahoo.com> Date: Tue, 08 May 2001 08:50:01 -0400 From: Earnie Boyd Reply-To: Cygwin Users X-Mailer: Mozilla 4.76 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 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? References: <2C08D4EECBDED41184BB00D0B747334202FB437B AT exchanger DOT cacheflow DOT com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit "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